Skip to main content
Use TRIGGERcmd through Corsair: one client, typed API calls. Copy the token from the Instructions page at https://www.triggercmd.com/user/computer/create, which is also where a computer is registered. The plugin sends it as a Bearer token. Things to know:
  • Commands live on your computers. The cloud only stores their names and settings, so commands.list reports what each agent synced. Adding or editing a command happens in the agent’s commands.json, not through this API.
  • A trigger is not a completion. commands.run acknowledges that the request was dispatched. Use commands.history to see whether it actually ran.
  • Parameters need Allow Params. A command runs without parameters unless the agent’s Allow Params flag is on, and an empty params string is rejected here because it would pass an empty argument rather than omitting it.
  • Panel buttons belong to the dashboard. Each button is configured with the command it runs. panels.trigger needs the panel and button names; params is optional and only matters for a button that takes them.
  • A 404 means the route is wrong. A real route with a bad token answers 401 with Invalid Token!, so a 404 is a path error rather than an auth one.
  • No webhooks. The provider posts no events for command completion, so poll commands.history.
What you get:
  • 6 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

List your registered computers
Run notepad on the laptop, with a parameter
See the full list on the API page.

What’s next

API reference

Every triggercmd.api.* operation with input and output types.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.