Superforms MCP server

• Registry nameco.superforms/superformsverified in the MCP registry

The registry name sits under superforms.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools11
• Server calls itselfsuperforms
• Server version0.2.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 121 ms.

• Its tools do ask a client which design direction they prefer; share a form link and watch answers arrive, but not embed a form on a website page.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it2 of 3 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer139 ms
• Space in an agent's context≈ 2,653 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 77 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 10 of 11
• Not saying whether it only reads or can destroy: 5 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• create_form

  Publish a voice-first form link immediately after creator confirmation, collect human answers, and pipe responses back to the agent.

• create_feedback_form

  Publish a voice-first feedback, cancellation, feature request, survey, or research form immediately after creator confirmation, with optional smart follow-ups.

• create_ask

  Create a voice-first Superforms answer link for human input. Backward-compatible alias for create_form.

• join_creation_session

  Join a Superforms homepage creation handoff session before creating the real form. Pass agentName with the client name, such as Codex, Claude Code, Claude, ChatGPT, or Cursor.

• update_creation_session

  Update a homepage creation handoff draft with the current form title, questions, and settings before the user clicks Set live.

• get_responses

  Fetch persisted raw responses for a Superforms ask. This is the MCP equivalent of the HTTP bridge answers endpoint.

• list_asks

  List recent asks for a provided private agent token.

• watch_ask

  Wait up to two minutes and return as soon as an individual answer is saved, including answers received while an agent was reconnecting and while the form remains in progress. The wait ends when this call returns; nothing keeps watching…

• list_my_forms

  List forms owned by the connected Superforms account, including response counts and latest response timestamps.

• get_my_form_responses

  Read persisted raw responses for a form owned by the connected Superforms account. No per-form agent token is required.

• watch_my_form_responses

  Return any existing individual answers immediately, or wait briefly until the respondent saves their next answer, even while the form remains in progress.