Skip to main content
Corsair MCP lets an AI agent use the apps you’ve connected to Corsair. It can read your inbox, post in Slack, open a GitHub issue, search data Corsair has synced, or set up an automation that runs when something happens in one of your apps. Every client uses the same address:
You add it once, sign in to Corsair, and choose which of your links the client uses.

Before you start

  • A Corsair account. Sign up at hub.corsair.dev with Google, GitHub or an emailed sign-in link.
  • Apps to use. You can connect them in Corsair first, or ask the agent to connect one later. It hands you a sign-in link for that app.

How sign-in works

1

Add the address to your client

2

Sign in to Corsair

The client opens Corsair in your browser.
3

Pick a link

A link is a set of your connected apps plus a mode that decides what the agent may do without asking. Pick an existing link or make a new one for this client. If you have no link yet, Corsair asks you to make one first.
4

Allow

The client gets the apps on that link and your email address. Nothing else on your account is shared.
One connection uses one link. To switch links, remove Corsair from the client, add it again and pick the other link. You can sign a client out of a link at any time from hub.corsair.dev/me.

Add it to your client

  1. In Claude, open Customize → Connectors → Add custom connector.
  2. Name it Corsair, paste https://mcp.corsair.cloud/mcp and add it.
  3. Select Connect and sign in to Corsair.
On a Team or Enterprise plan, an owner adds connectors under Organization settings.
Any other client that supports remote MCP servers with OAuth sign-in works the same way.
Some clients can’t sign in to an MCP server, such as GitHub Copilot’s coding agent. For those, use a link’s own address with an API key. Open the link at hub.corsair.dev/me and follow the steps for your client there.

What the agent can do

Scripts run in a sandbox that can only call your connected apps’ actions. They have no network, filesystem or other system access, and the agent never sees your app credentials. Not every link shows every tool. A link that isn’t allowed to add apps has no add_integrations, and a Read link has no add_triggers or remove_triggers. read_data, search_data and the list_ and get_ tools are marked read-only, so most clients run them without asking. Clients usually ask you before running the others.

Modes and approvals

Each link has a mode. Corsair checks every action against it, whatever the client allows. When an action needs approval, the agent gives you a link. It shows exactly what will run and with which arguments. Approve or deny it there, then tell the agent to carry on. An approval covers that one action once. Change a link’s mode at hub.corsair.dev/me.

Troubleshooting

Ask it to connect the app. It calls add_integrations and gives you a sign-in link. Open it, sign in to the app, then tell the agent you’re done.
The project behind your link has to finish setting the app up first, for example by adding its OAuth credentials. Whoever manages the project does this in Corsair.
The link’s mode doesn’t allow that kind of action. Change the mode at hub.corsair.dev/me, or use a link with a different mode.

Support and privacy

Email primary@corsair.dev. See the privacy policy and terms.