Local MCP server/Productivity

SubmitraX MCP server

Local MCP server

SubmitraX collects form responses and notifies you, aimed at designers and small teams who do not want to manage a server. Its MCP path is a connector that runs locally: the provider documents installing the Node connector, adding an account API token, starting it with node index.js and registering that command with your client. A self-hosted remote connector is also documented. The public mcp.submitrax.com endpoint from the earlier listing does not resolve, so this page now describes the local setup only.

API token for the local connector Local install path Reviewed 2026-11-16
About

Where it fits

Designers and small teams who collect form responses and want an assistant to read or manage them locally.

  • Review recent form submissions.
  • Export responses.
  • Generate a form from a description.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Run the SubmitraX MCP connector locally

The provider documents a local connector that runs on your own computer with an account API token, plus a self-hosted remote option. The mcp.submitrax.com host in the earlier listing does not resolve.

  1. Install the Node connector

    Download the MCP connector from SubmitraX and install its dependencies.

  2. Add the account API token

    Create the token in SubmitraX and put it in the connector's configuration.

  3. Start it and register the command

    Run node index.js and add that command as a local stdio MCP server in your client.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

SubmitraX documentationhttps://submitrax.com/documentation/