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.
Skills that pair with SubmitraX
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Use when starting any conversation. Establishes how to find and use skills and requires Skill tool invocation before any response, including clarifying questions.
Ask which skill or flow fits a situation. It routes among the user-invoked skills in this repository.
Searches, creates, and manages notes in an Obsidian vault with wikilinks and index notes. Use it when the user wants to find, create, or organize notes in Obsidian.
No skills found
Try a different search term or clear the filters.
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.
- Install the Node connector
Download the MCP connector from SubmitraX and install its dependencies.
- Add the account API token
Create the token in SubmitraX and put it in the connector's configuration.
- 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.
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.
Before you connect
- 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.
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.
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/