Connect your AI agent with MCP
Formbear now speaks the Model Context Protocol. Add our MCP endpoint to Claude, ChatGPT, Claude Code, or Cursor, sign in to Formbear when it connects, and let your agent work with your forms and responses, all through the same encrypted, EU-hosted paths the app uses.
- Sign in, pick a workspace, done. Formbear is its own OAuth 2.1 authorization server for the connector, built on the account you already use. You approve the app, choose the workspace it may use, and it acts with your access there, stopping the moment you leave. Connected apps are listed under Settings → API, where you can disconnect one or pick a different workspace for it.
- Read your data from an agent. On every plan: list your forms, read a form's questions, pull its responses (each answer keyed by its question, decrypted server-side), and get per-question summaries.
- Build and manage forms from an agent (Pro). Have your agent create a form, add, edit, reorder, or remove questions, change its settings and design, and publish it. Every question keeps a stable id, so an agent can edit a form that already has responses without breaking them; it asks before a change that would discard answers. Duplicate, delete, or restore an earlier version too.
- Analytics and insights for the agent. Ask where a form's visitors came from and how many finished, get an AI digest of the responses, or have the agent look something up in these docs.
- API tokens for tools and scripts. Where pasting a credential once is easier, create and revoke workspace tokens under Settings → API. The secret is shown once, and a token stops the moment its creator leaves. See the MCP connector docs.
- No new company in the loop. The MCP server runs on our own EU infrastructure: your data never leaves it to make this work.