← All integrations

Coassemble MCP server

4 operations0 webhooks

Course and training platform. List clients, courses and users, and read learners' progress through a course.

Connect Coassemble to Claude, ChatGPT or Cursor

  1. 1

    Connect Coassemble in Corsair

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

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

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp

    Claude

    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    ChatGPT

    Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.

    Cursor

    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" }
      }
    }

    Claude Code

    Run this, then run /mcp in Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcp

    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. Every Coassemble operation only reads data, so it runs right away in every mode.

Coassemble operations available through MCP

  • GetRead-only

    Get a paginated list of Coassemble clients

FAQ

Install corsair and @corsair-dev/coassemble, add the Coassemble plugin, and connect with an API key. Then call methods like corsair.coassemble.api.clients.get() from your app. Corsair syncs data per tenant.

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

Teams use Corsair for course and training platform. list clients, courses and users, and read learners' progress through a course. Common builds include sync jobs, admin tooling, and agents that call Coassemble APIs from your backend. Local DB entities let you query synced Coassemble records without hitting the API on every read.

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 Coassemble 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/coassemble in the open repo. When Coassemble 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 Coassemble data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Coassemble 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 Coassemble on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every Coassemble operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.