← All integrations

Supportbee MCP server

50 operations0 webhooks

Help desk for reading, replying to and routing support tickets, with users, teams, labels, snippets and reports.

Try Supportbee with your agent

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

Runs once, when you ask

Supportbee tools and triggers

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

Tickets

  • Add LabelWrite

    Add a label to a ticket. The label has to exist on the company first

    tickets.addLabel

  • ArchiveWrite

    Archive a ticket, which takes it out of the default list. The ticket stays readable

    tickets.archive

  • Assign TeamWrite

    Assign a ticket to a team. Reassigning to another team clears the user assignee

    tickets.assignTeam

  • Assign UserWrite

    Assign a ticket to a user. If the ticket is already assigned to a team, the user must be a member of it

    tickets.assignUser

  • AuditRead-only

    Read the audit trail of one ticket, oldest action first

    tickets.audit

  • CreateDestructive

    Open a ticket for a requester, which emails them when notify_requester is set. This plugin always sends the API token

    tickets.create

  • DeleteDestructive

    Delete a trashed ticket for good. Only an admin can delete, and only a ticket already in the trash

    tickets.delete

  • GetRead-only

    Read one ticket with its requester, content and assignment

    tickets.get

  • ListRead-only

    List unarchived tickets in last-activity order, filtered by assignee, team, label, requester or date

    tickets.list

  • Mark AnsweredWrite

    Mark a ticket answered without sending a reply, which is how an off-system answer is recorded

    tickets.markAnswered

  • Mark SpamWrite

    Mark a ticket as spam

    tickets.markSpam

  • Mark UnansweredWrite

    Mark a ticket unanswered so it returns to the open queue

    tickets.markUnanswered

Connect Supportbee to Claude, ChatGPT or Cursor

  1. 1

    Connect Supportbee in Corsair

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

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Supportbee. On a ChatGPT personal plan, connect Supportbee 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, Supportbee's read and write operations run right away and its 6 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/supportbee, add the Supportbee plugin, and connect with an API key. Then call methods like corsair.supportbee.api.attachments.create() from your app. Corsair keeps each tenant isolated.

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

Teams use Corsair for help desk for reading, replying to and routing support tickets, with users, teams, labels, snippets and reports. Common builds include sync jobs, admin tooling, and agents that call Supportbee 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 Supportbee 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/supportbee in the open repo. When Supportbee 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 Supportbee data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Supportbee 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 Supportbee 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 6 destructive Supportbee operations. You can change a link's mode at hub.corsair.dev/me.