MCP connector: use immut as a tool, not an API

immut runs a hosted MCP server. Point your agent host at it and immut becomes a set of tools your model can call. No code, no SDK.

URL: https://backend.immut.io/mcp

This is the fastest way in if your host speaks MCP. If it does not, use the REST API instead. Both do the same work.

How do I connect it?

One command sets it up in Claude Code.

claude mcp add --transport http immut https://backend.immut.io/mcp \
  --header "Authorization: Bearer imut_live_your_key"

Other hosts take a config file. Cursor is one.

{
  "mcpServers": {
    "immut": {
      "url": "https://backend.immut.io/mcp",
      "headers": { "Authorization": "Bearer imut_live_your_key" }
    }
  }
}

Create the key in the immut app under Organization Settings, then AI Agents. Per-host setup steps are on the Connect page.

What are the transport rules?

Streamable HTTP, and stateless. POST only. GET and DELETE return 405.

Authenticate with Authorization: Bearer imut_live_.... This endpoint also accepts x-api-key, because some hosts allow no other header. That is true here and nowhere else. The /api/v1 routes require Bearer.

What tools does it expose?

23 of them.

They cover workspaces, folders, and protecting files and versions. They also cover documents, proofs, certificates and public verification. The rest handle run reporting, agent status and instructions, the review queue, and usage.

The full list with arguments is in llms-full.txt and in the bootstrap document at https://backend.immut.io/api/v1/docs.

Does the connector change what my key can do?

No. It forwards your key to the same v1 API.

Scopes apply exactly as they do over REST. A tool your key lacks scope for returns a clean tool error. It does not end the session. So the connector is a different door, not a wider one.

Can it read files off my computer?

No. The hosted server has no filesystem access.

It protects bytes you pass it. If you want something that reads your disk and decides what matters, that is the agent skill, which runs on your own machine. The two are complements. Many teams run both.

Local file reading exists in the code for people self-hosting the server beside themselves. It is ignored in production, whatever the environment says. A public deployment must never read arbitrary host paths.

Which should I use, the connector or the skill?

Pick by what you need it to do.

What happens when a tool call fails?

You get a tool error with the same codes the REST API uses.

Read the code, not the message. The list, and which errors are worth retrying, is on the Errors page.