Context7

Install corsair and @corsair-dev/contextsevenmcp, add the Context7 plugin, and connect with an API key. Then call methods like corsair.contextsevenmcp.api.context.get() from your app. Corsair keeps each tenant isolated.

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

Teams use Corsair for documentation context mcp server for injecting up-to-date library docs into ai coding agents. Common builds include sync jobs, admin tooling, and agents that call Context7 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 Context7 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/contextsevenmcp in the open repo. When Context7 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 Context7 data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Context7 data on your behalf.