StackAI MCP server
6 operations0 webhooks
Inspect project input and output schemas and manage asynchronous StackAI runs.
Try StackAI with your agent
Connect StackAI, 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 StackAI on my account, then run one read-only example and show me the result.
StackAI tools and triggers
Tools are what your agent can do in StackAI through Corsair's MCP server. Triggers are the StackAI events a routine can start from.
Runs
- CancelDestructive
Request cancellation of an owned run. It cannot be undone.
runs.cancel
- GetRead-only
Get a run and its current state.
runs.get
- ListRead-only
List runs using cursor pagination and filters.
runs.list
- ResumeDestructive
Resume an ask-human paused run. The run continues executing and bills model usage.
runs.resume
- StartDestructive
Start an asynchronous project run. Each run executes the workflow and bills model usage.
runs.start
Projects
- Io SchemaRead-only
Inspect a project version input and output schema.
projects.ioSchema
Connect StackAI to Claude, ChatGPT or Cursor
- 1
Connect StackAI in Corsair
Add your StackAI API key once in Corsair. Corsair stores the credential encrypted and makes the StackAI API calls for your agent, so it never goes into a prompt or a config file. Connect StackAI
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs StackAI. On a ChatGPT personal plan, connect StackAI here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.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" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, 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
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, StackAI's read and write operations run right away and its 3 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/stackai, add the StackAI plugin, and connect with an API key. Then call methods like corsair.stackai.api.projects.ioSchema() from your app. Corsair keeps each tenant isolated.
Yes. StackAI requires an API key from your StackAI 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 StackAI, GitHub, Notion, Stripe, and the rest. Trigger StackAI from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for inspect project input and output schemas and manage asynchronous StackAI runs. Common builds include sync jobs, admin tooling, and agents that call StackAI 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 StackAI 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/stackai in the open repo. When StackAI 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 StackAI data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store StackAI 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 StackAI 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 3 destructive StackAI operations. You can change a link's mode at hub.corsair.dev/me.