← All integrations

Fireberry MCP server

24 operations0 webhooks

Operate Fireberry CRM records, metadata, custom fields and objects, attachments, queries, and batch actions through typed Corsair endpoints.

Use Fireberry in Claude, ChatGPT, Cursor or another MCP client

Connect Fireberry once in Corsair, then add one MCP address to your agent.

Connect Fireberry
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Fireberry with your agent

Connect Fireberry, 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 Fireberry on my account, then run one read-only example and show me the result.

Runs once, when you ask

Fireberry tools and triggers

Tools are what your agent can do in Fireberry through Corsair's MCP server. Triggers are the Fireberry events a routine can start from.

Records

  • CreateWrite

    Create a Fireberry record

    records.create

  • DeleteDestructive

    Permanently delete a Fireberry record

    records.delete

  • GetRead-only

    Retrieve a Fireberry record by ID

    records.get

  • ItemsRead-only

    Retrieve line items associated with a Fireberry order, invoice, or receipt

    records.items

  • Legacy QueryRead-only

    Search and paginate Fireberry records using the legacy query API

    records.legacyQuery

  • ListRead-only

    List records for a documented Fireberry object

    records.list

  • QueryRead-only

    Filter, sort, group, and paginate Fireberry records

    records.query

  • RelatedRead-only

    List records related to a Fireberry record

    records.related

  • UpdateWrite

    Update a Fireberry record

    records.update

Batch

  • CreateWrite

    Create multiple Fireberry records in one request

    batch.create

  • DeleteDestructive

    Delete up to 20 Fireberry records in one request

    batch.delete

  • UpdateWrite

    Update multiple Fireberry records in one request

    batch.update

Connect Fireberry to Claude, ChatGPT or Cursor

  1. 1

    Connect Fireberry in Corsair

    Add your Fireberry API key once in Corsair. Corsair stores the credential encrypted and makes the Fireberry API calls for your agent, so it never goes into a prompt or a config file. Connect Fireberry

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Fireberry. On a ChatGPT personal plan, connect Fireberry here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, 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. 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, Fireberry's read and write operations run right away and its 4 destructive operations wait 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/fireberry, add the Fireberry plugin, and connect with an API key. Then call methods like corsair.fireberry.api.batch.create() from your app. Corsair keeps each tenant isolated.

Yes. Fireberry requires an API key from your Fireberry 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 Fireberry, GitHub, Notion, Stripe, and the rest. Trigger Fireberry from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for operate Fireberry CRM records, metadata, custom fields and objects, attachments, queries, and batch actions through typed Corsair endpoints. Common builds include sync jobs, admin tooling, and agents that call Fireberry 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 Fireberry 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/fireberry in the open repo. When Fireberry 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 Fireberry data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Fireberry 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 Fireberry 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 4 destructive Fireberry operations. You can change a link's mode at hub.corsair.dev/me.