Jotform MCP server
Jotform in any MCP client, through Memtro: Jotform does not publish this server. Memtro's Jotform connector reads Jotform through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Jotform: the account's forms with their status and submission counts, and the submissions made to a form or across the account, each with its answers. When asked, can clone or delete a form, edit, flag, mark read or delete a submission, and create, rename, fill or delete a label to organise forms. Never submits to a form.
Reads
jotform_list_formsJotform forms in the account: title, status, how many submissions and how many unread, when created and last changed, and the form's link.jotform_list_submissionsJotform submissions with each answer against its question.jotform_get_submissionOne Jotform submission in full: when it was made, its status, and every answer against its question.
Acts, when you ask
These change something in Jotform. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
jotform_clone_formCopy a Jotform form into a new form in the same account.jotform_update_submissionEdit a Jotform submission's answers, or mark it read, unread or flagged.jotform_delete_submissionPermanently delete one Jotform submission and its answers.jotform_update_labelRename or recolour a Jotform label.jotform_add_forms_to_labelFile Jotform forms under a label (a form can carry several labels).jotform_delete_formDelete a Jotform form.jotform_delete_labelDelete a Jotform label and every label inside it.jotform_create_labelCreate a new label in Jotform, for organising forms, optionally with a colour and inside a parent label.
Connect it
First connect Jotform on Dashboard → Connections, then add Memtro to your client once. The Jotform tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Jotform connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What came in through the event registration form this week?
- › How many unread submissions does the contact form have?
- › Show me the latest submissions across all our forms
- › Which of our forms have had no submissions at all?
- › Flag the submission from Dan Fletcher on the workshop form
Questions
- Is this an official Jotform MCP server?
- No. It is Memtro's MCP server with Memtro's Jotform connector behind it: the connector reads Jotform through its API with the credentials you connect on Dashboard → Connections, and Jotform publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Jotform?
- Only when you ask, and only what it has been granted: create a label to organise forms in the account, optionally inside another label; clone a form; edit a submission's answers, or mark it read, unread or flagged; delete a submission permanently; rename or recolour a label; file forms under a label; delete a form permanently, with its submissions; delete a label and its sublabels (the forms in it stay). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.