MCP is on for Bellows Cloud. On a self-hosted install it is switched on by the administrator; if the endpoint answers
404, it is off there.Endpoint
On Bellows Cloud the endpoint is:/api/mcp.
It uses Streamable HTTP and needs https. Older HTTP+SSE clients (protocol 2024-11-05) are refused.
Sign in
You do not create or paste a token. The first time a client connects, it opens a Bellows consent screen in your browser.1
Sign in to Bellows
If you are not signed in, Bellows asks you to sign in first.
2
Review the request
The consent screen shows the app, the access it asks for, and the organization it gets access to. Pick the organization if you belong to more than one.
3
Allow or Deny
Click Allow. The client now holds a token that works only on
/api/mcp.Connect
- Claude Code
- Claude.ai
- Other clients
/mcp, choose bellows, then Authenticate. Approve the request in the browser. Check it with a prompt like “call whoami on the bellows server”.What the session can do
The client acts as you, in the organization you chose. It sees your tasks and your personal executors and connections, plus your organization’s. It cannot touch credentials, secrets, connection setup or membership; those are refused whatever you granted. Tools only call the same Bellows routes the web app uses, so repository policy and your role still apply. See MCP tools for the full list.Limits
- A tool call ends after 55 seconds. For long runs, use
wait_taskrepeatedly. - A client can run up to 8 tool calls at once.
- No file bytes pass through MCP. To attach a file, the client gets an upload link. See Attachments.