Devin MCP

Install corsair and @corsair-dev/devinmcp, add the Devin MCP plugin, and connect with an API key. Then call methods like corsair.devinmcp.api.session.create() from your app. Corsair keeps each tenant isolated.

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

Teams use Corsair for mcp integration for devin ai software engineering agent capabilities and tooling. Common builds include sync jobs, admin tooling, and agents that call Devin MCP 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 Devin MCP 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/devinmcp in the open repo. When Devin MCP 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 Devin MCP data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Devin MCP data on your behalf.