ByteForms MCP server
5 operations0 webhooks
Form builder platform. Create, list, read, and delete forms and read the responses submitted to them.
Try ByteForms with your agent
Connect ByteForms, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in ByteForms on my account, then run one read-only example and show me the result.
ByteForms tools and triggers
Tools are what your agent can do in ByteForms through Corsair's MCP server. Triggers are the ByteForms events a routine can start from.
Forms
- CreateWrite
Create a new ByteForms form with custom fields and options
forms.create
- DeleteDestructive
Delete a ByteForms form by its numeric or public ID
forms.delete
- GetRead-only
Retrieve a single ByteForms form definition by ID
forms.get
- ListRead-only
List all ByteForms forms created by the authenticated user
forms.list
- ResponsesRead-only
Retrieve paginated responses submitted to a ByteForms form
forms.responses
Connect ByteForms to Claude, ChatGPT or Cursor
- 1
Connect ByteForms in Corsair
Add your ByteForms API key once in Corsair. Corsair stores the credential encrypted and makes the ByteForms API calls for your agent, so it never goes into a prompt or a config file. Connect ByteForms
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs ByteForms. On a ChatGPT personal plan, connect ByteForms here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, ByteForms's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/byteforms, add the ByteForms plugin, and connect with an API key. Then call methods like corsair.byteforms.api.forms.create() from your app. Corsair keeps each tenant isolated.
Yes. ByteForms requires an API key from your ByteForms account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit ByteForms, GitHub, Notion, Stripe, and the rest. Trigger ByteForms from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for form builder platform. create, list, read, and delete forms and read the responses submitted to them. Common builds include sync jobs, admin tooling, and agents that call ByteForms APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per ByteForms API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/byteforms in the open repo. When ByteForms ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your ByteForms data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ByteForms data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put ByteForms on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive ByteForms operation. You can change a link's mode at hub.corsair.dev/me.