Skip to content

Connect Claude Code to Carver (MCP)

Sign in to Carver from Claude Code with your browser — no API key, no config file, nothing copied onto your machine.

Overview

Carver's MCP server lets an AI assistant such as Claude Code read and act on your compliance estate directly: list your AI agents, see which acts reach them, work through outstanding obligations, publish a trust page. The server is an OAuth 2.1 resource server, so Claude Code handles sign-in for you — it opens a browser tab, you sign in and choose a workspace, and the token is stored in your OS keychain and refreshed silently.

You do not need an existing Carver account to start. If you're new, you can sign up in the same tab and work in a private workspace of your own while any request to join your company's workspace waits for an administrator.

Availability

This flow is live on https://staging.carveragents.ai. The examples below use that host. Production (app.carveragents.ai) is not yet enabled — contact us before pointing Claude Code at it.

Getting Started

Run this from a machine with a browser — the sign-in step opens a browser tab.

1. Add the server

claude mcp add --transport http carver https://staging.carveragents.ai/api/v1/mcp

No flags, no client ID, no key. Claude Code discovers what it needs from the server's own metadata and registers itself.

2. Sign in

claude mcp login carver

A Carver tab opens in your browser:

  1. Sign in or sign up — Google, Microsoft, or email and password. Use the same account you use for the Carver dashboard: the workspaces you're offered belong to that account, not to your email address.
  2. Choose the workspace this connection should read:
  3. Your organization — the shared workspace, with every AI agent your organization has registered. Choose this to work on your team's estate.
  4. Just me — a private workspace created for you on confirm. Empty to start with, and nobody else can see it.
  5. Press Connect. The tab confirms the connection and hands back to your terminal.

If you're brand new and not yet approved for your company's workspace, Just me is always available and is approved instantly.

3. Check it worked

In Claude Code:

/mcp

carver should be listed as connected. Then just ask in plain language:

  • "list my AI agents"
  • "what's outstanding on the vendor support agent"
  • "which acts reach our customer chatbot?"

Claude Code announces which workspace the session is reading when it connects — if you're ever unsure what a session can see, that line is the answer.

What Claude Code Can Do

Once connected, these tools are available to the assistant, all scoped to the workspace you chose:

Area What you can ask for
AI agents List agents, get one agent, compliance overview, draft and save an agent profile
Obligations Acts reaching an agent, obligations under one act, outstanding gaps, decision history
Answering Answer a single obligation, answer a whole act, assign a gap to an owner
Trust Read your trust page state, publish the trust page
Account Plan and quota

Configuration

Switching workspace

The workspace is fixed at sign-in and cannot be changed in place — a connection can never reach a workspace it wasn't granted. To swap:

claude mcp logout carver
claude mcp login carver     # pick the other workspace

Sessions and expiry

Access is valid for one hour and refreshes silently in the background. The underlying session lasts 30 days, so you shouldn't have to sign in again inside a month.

Disconnecting

claude mcp logout carver      # end this connection
claude mcp remove carver      # also forget the server

Logging out revokes the session server-side, not just locally.

Troubleshooting

What you see What it means
"This request has expired" on the sign-in page A sign-in request is valid for 10 minutes. Re-run claude mcp login carver.
The picker shows no organizations Your membership is still pending an administrator's approval. Take Just me and carry on — you can switch once you're approved.
Tools stop working with a 403 mid-session Your membership for that workspace was revoked or set back to pending. This takes effect immediately. Log out and back in, choosing another workspace.
Everything returns 401 right after claude mcp add Expected once — that 401 is what starts the sign-in flow. If claude mcp login doesn't follow, check that https://staging.carveragents.ai/.well-known/oauth-protected-resource returns JSON.
Your private workspace looks empty It is, by design. Just me starts with no agents; register one, or reconnect against your organization's workspace.

See Also