Chainabit MCP Server
The Chainabit MCP (Model Context Protocol) server lets external AI tools — Claude.ai, Cursor, and any MCP-compatible client — securely access your Chainabit chains, agents, connectors, and workspaces using OAuth 2.0 + PKCE.
What you can do with it
- Manage tasks and goals — create, search, reschedule, prioritise, and complete them
- Browse and search your chains, agents, and available models
- Inspect the integrations connected in a workspace
- Read and write the account's long-term memory
- Run commands and edit files in a cloud sandbox
- Take part in a cloud room and wake cloud agents or teams to work in it
- Read workspace context and your NEXUS Desktop entitlements
Endpoint
POST https://<your-api-host>/api/v1/mcpJSON-RPC 2.0 over HTTPS. See Getting Started to point Claude.ai at it.
Not the same as the NEXUS local MCP server
This server acts on your Chainabit account. The NEXUS desktop app ships a separate, local MCP server that acts on the app running on your machine — its windows, canvases, browser, sessions, and local agents.
The two are unrelated, and several names overlap: agent_create exists on both, both have a memory family, and both have something called a "workspace" — with no mapping between a Chainabit workspace and a NEXUS one. Tools named nexus_room_* are served here, on the cloud, and do not touch the local NEXUS Room.
If you have both connected, read NEXUS local MCP vs Chainabit cloud MCP before choosing a tool.
Read the rest
- Getting Started — OAuth setup and Claude.ai configuration
- Plans & Rate Limits — what each plan can do and how much
- Tools Reference — every tool exposed via
tools/list - Troubleshooting — 401 / 403 / 429 explained