Integrations & AI Connectors
Connect Orbiform to Claude with MCP
Orbiform runs a remote MCP (Model Context Protocol) server, so Claude — or any other MCP-compatible AI client — can list your forms, read and manage responses, check analytics, and configure webhooks directly from a conversation, scoped to a single Orbiform workspace at a time.
1. What is MCP?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. Instead of copy-pasting data between Orbiform and a chat window, you add Orbiform as a connector once, and Claude can call its tools directly — reading your form data live and, if you allow it, creating or updating forms and webhooks on your behalf.
2. Connecting from Claude.ai (recommended)
On an individual Pro or Max plan, go to Settings → Connectors in Claude, click + Add custom connector, and enter:
https://orbiform.cc/api/mcp
Claude will redirect you to sign in to Orbiform (if you aren't already) and ask which workspace to connect — this uses OAuth, so Claude never sees your Orbiform password, only the specific workspace you approve. On Team or Enterprise plans, an organization Owner adds the connector under Organization settings → Connectors first, and members connect individually after.
3. Connecting with a static API key (other MCP clients)
For MCP clients that don't support OAuth, generate a static API key instead: go to Settings → Integrations in Orbiform, find Static API keys, and click Create key. Copy it immediately — it's shown only once. Configure your MCP client with the same server URL and an Authorization: Bearer <key> header.
4. What Claude can do once connected
- list_forms / get_form — see every form in the workspace and its full detail.
- create_form / update_form / delete_form — build or edit a form's title, fields, and settings.
- list_responses / get_response / delete_response — read or remove submissions.
- get_analytics — funnel and per-question breakdowns, the same data as the dashboard's Analytics tab.
- list_webhooks / create_webhook / update_webhook / delete_webhook / test_webhook — manage a form's integrations.
5. Example prompts once connected
- "List every form in my Orbiform workspace and how many responses each has."
- "Summarize the last 20 responses to my customer feedback form."
- "Create a 5-question onboarding survey and publish it."
- "Add a webhook on my signup form pointing to this URL, then send a test payload."
6. Security and what's scoped to what
Every connection — OAuth or static key — is bound to exactly one Orbiform workspace, chosen at connect time; Claude can never read or write another workspace's data through the same connection. Only workspace owners and admins can create API keys, approve OAuth connections, or revoke either one, and both can be disconnected anytime from Settings → Integrations in Orbiform.
7. Disconnecting
In Orbiform, go to Settings → Integrations, and under Connected apps, click Disconnect next to the app, or revoke a static API key under Static API keys. You can also remove the connector from Claude's own Settings → Connectors page.
Related articles
