← All integrations

TRIGGERcmd MCP server

6 operations0 webhooks

List registered computers and their commands, run a command remotely, read run history, and press panel buttons.

Try TRIGGERcmd with your agent

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

Runs once, when you ask

TRIGGERcmd tools and triggers

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

Commands

  • HistoryRead-only

    Read the run history of one command, newest first

    commands.history

  • ListRead-only

    List the commands configured on every computer, with the computer each belongs to

    commands.list

  • RunDestructive

    Run a configured command on one of the account's computers, with optional parameters

    commands.run

Panels

  • ListRead-only

    List the dashboard panel buttons and the parameters each carries

    panels.list

  • TriggerDestructive

    Press a panel button, which runs the command it is configured for

    panels.trigger

Computers

  • ListRead-only

    List the computers the agent has registered

    computers.list

Connect TRIGGERcmd to Claude, ChatGPT or Cursor

  1. 1

    Connect TRIGGERcmd in Corsair

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

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

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

Teams use Corsair for list registered computers and their commands, run a command remotely, read run history, and press panel buttons. Common builds include sync jobs, admin tooling, and agents that call TRIGGERcmd 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 TRIGGERcmd 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/triggercmd in the open repo. When TRIGGERcmd 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 TRIGGERcmd data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TRIGGERcmd 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 TRIGGERcmd 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 2 destructive TRIGGERcmd operations. You can change a link's mode at hub.corsair.dev/me.