MCP connector

Formbear runs an MCP server (Model Context Protocol) so an AI agent can work with your workspace: list your forms, read their questions, pull or summarize responses, and, on Pro, build and publish forms. Everything goes through the same encrypted, workspace-scoped paths the app uses, on our own EU infrastructure, so no new company touches your data.

Create a token

1. 1

   Open Settings → API

   Any workspace owner or admin can manage tokens. Each token grants access to the whole workspace, so treat it like a password.
2. 2

   Create a token and copy it

   Name it for where you’ll use it. The secret is shown once: copy it then, because you can’t view it again, only revoke it and make a new one.
3. 3

   Point your MCP client at the endpoint

   The endpoint is https://formbear.app/api/mcp. Send the token as a bearer credential, as shown for each client below.

Connect your client

Formbear speaks standard Streamable HTTP MCP, so any client that supports remote MCP servers with a bearer token works. The most common ones:

Claude Code

claude mcp add formbear --transport http https://formbear.app/api/mcp \
  --header "Authorization: Bearer fbk_your_token_here"

Claude.ai and Claude Desktop

Go to Settings → Connectors → Add custom connector, paste https://formbear.app/api/mcp as the URL, and enter your token when asked to authenticate. Custom connectors are available on paid Claude plans.

Cursor and other MCP clients

{
  "mcpServers": {
    "formbear": {
      "url": "https://formbear.app/api/mcp",
      "headers": {
        "Authorization": "Bearer fbk_your_token_here"
      }
    }
  }
}

ChatGPT

In ChatGPT, enable Developer mode under Settings → Connectors, then add a connector with the same URL and your token. Developer mode is available on ChatGPT Plus, Pro, Business, and Enterprise.

Reading (every plan)

• list_forms: every form in the workspace, with its status and response count.
• get_form: one form’s questions and structure, by its public id.
• list_responses: a form’s responses, each answer keyed by its question, decrypted server-side. Pages with limit and offset (up to 200 per call).
• summarize_responses: per-question aggregates, a cheap overview without pulling every raw response.

Building forms (Pro)

• create_form: create a new draft form from a title and a set of blocks. Returns the new public id.
• update_form: change a draft’s title, or replace its blocks.
• publish_form: publish the draft, making it live.

Things to try

• “Which of my forms got the most responses this month?”
• “Summarize the feedback from my onboarding survey and pull out the three most common complaints.”
• “Show me the last 20 responses to the contact form and flag any that mention billing.”
• “Build me an event RSVP form with name, email, dietary requirements, and a plus-one question, then publish it.” (Pro)

What the agent can see, and what we keep

A token acts as your workspace, with the access of the person who created it. The read tools return your own forms and response answers, decrypted on our server only for that request; we never hand the raw answer set to a model ourselves, and nothing is sent to a third party to power the connector. Each token records only when it was last used. Every call runs on our EU infrastructure, under the same encryption at rest and privacy policy as the rest of Formbear.

Revoking access

Revoke a token anytime from Settings → API and it stops working immediately. A token also stops the moment the person who created it leaves the workspace, so access always follows current membership. See responses for the data these tools read.