Read survey responses and manage contacts, webhooks, teams and organisation users. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"formbricks": {
"url": "https://formbricks.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"formbricks": {
"type": "http",
"url": "https://formbricks.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Formbricks API key.
Create one in Formbricks → Settings → API Keys. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Formbricks API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Formbricks connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
formbricks_health | read | Check API health Check that the Formbricks API is reachable. Formbricks v2: GET /health. |
formbricks_whoami | read | Identify the configured key Return the project and environment the configured x-api-key belongs to — the fastest way to find the workspace and environment ids the other tools need. Formbricks v2: GET /me. |
formbricks_list_responses | read | List survey responses List survey responses, optionally narrowed to one survey, one contact or a date window. This is the main read: the answers people gave. Formbricks v2: GET /management/responses. |
formbricks_get_response | read | Get one response Fetch a single survey response with its answers, metadata and completion state. Formbricks v2: GET /management/responses/{id}. |
formbricks_list_webhooks | read | List webhooks List the webhooks configured to fire on survey events, optionally filtered to specific surveys. Formbricks v2: GET /management/webhooks. |
formbricks_get_webhook | read | Get one webhook Fetch a single webhook with its URL, triggers and bound surveys. Formbricks v2: GET /management/webhooks/{id}. |
formbricks_list_contact_attribute_keys | read | List contact attribute keys List the contact attribute keys defined in an environment — the schema of what you know about a contact. Formbricks v2: GET /management/contact-attribute-keys. |
formbricks_get_contact_attribute_key | read | Get one contact attribute key Fetch a single contact attribute key. Formbricks v2: GET /management/contact-attribute-keys/{id}. |
formbricks_get_survey_contact_link | read | Get a personal survey link for a contact Get the personalised survey URL for one contact — the link you send so their response is attributed to them. Formbricks v2: GET /management/surveys/{surveyId}/contact-links/contacts/{contactId}/. |
formbricks_get_survey_segment_links | read | Get personal survey links for a segment Get personalised survey URLs for every contact in a segment — how you run a targeted send. Formbricks v2: GET /management/surveys/{surveyId}/contact-links/segments/{segmentId}. |
formbricks_list_teams | read | List teams List the teams in an organisation. Formbricks v2: GET /organizations/{organizationId}/teams. |
formbricks_list_organization_users | read | List organisation users List the users in an organisation, optionally looked up by id or email. Formbricks v2: GET /organizations/{organizationId}/users. |
formbricks_list_roles | read | List roles List the roles that can be assigned to organisation users. Formbricks v2: GET /roles. |
formbricks_create_webhook | write | Create a webhook Register a webhook that fires on survey events. Formbricks v2: POST /management/webhooks. |
formbricks_delete_webhook | write | Delete a webhook Remove a webhook. Formbricks v2: DELETE /management/webhooks/{id}. |
formbricks_create_contact | write | Create a contact Create a contact in a workspace from a set of attributes, e.g. email and userId. Formbricks v2: POST /management/contacts. |
formbricks_delete_response | write | Delete a response Delete one survey response. Irreversible — use it to honour a data-deletion request. Formbricks v2: DELETE /management/responses/{id}. |
formbricks_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
formbricks_request_feature | Request a missing feature Tell usefulapi that the user needs something the Formbricks tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
formbricks_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Formbricks tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
formbricks_cancel_subscription | Cancel the Pro subscription Cancel the caller's Formbricks Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run formbricks_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Formbricks server only. Subscribe with formbricks_upgrade (it returns a Stripe Checkout link). Cancel any time with formbricks_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running formbricks_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Formbricks. The server calls the Formbricks API with your own Formbricks access, so it sees only the data that your account can see.
The login page asks for your Formbricks API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Formbricks API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Formbricks API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Formbricks.
Yes, if you approve it. 4 of the 17 Formbricks tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Formbricks server only. Run formbricks_usage_status to see how many calls you used.
Ask the AI to run formbricks_upgrade: it returns a Stripe Checkout link. To cancel, run formbricks_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with formbricks_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.