Skip to main content
Connect Claude Code to Agent Vault so it can check out and sign in for you, using only mock tokens. It takes about 2 minutes: one command adds the server, and you sign in once with /mcp.

Copy the line for Claude Code from your dashboard, then add the server and sign in.

Before you start

  • An Agent Vault account, with a card if your agent will check out. New here? The Quickstart sets one up in about 5 minutes.
  • Claude Code, installed and signed in.

Connect Claude Code

1

Paste this into Claude Code

Claude Code reads the connect skill and runs the command that adds the server.
2

Sign in

Run /mcp in Claude Code, choose agent-vault and sign in on the Agent Vault sign-in page that opens, with your Agent Vault account.

Choose what it may use

A new connection starts with nothing granted, so your agent can’t use a card or a login yet. Until you choose, its first tool call answers:
The connection itself appears in the dashboard only once your agent makes its first tool call, so make that call first.
1

Make a first call

Ask your agent to call get_token_catalog. It answers with the message above, and the call creates the connection.
2

Open Connected apps

In the dashboard sidebar, under Vault, click Connected apps. The new connection’s row shows Choose what it may use.
3

Pick its cards and logins

Click Choose access. Under Cards and Logins, pick All, or keep Only selected and tick the ones this agent may use.
4

Check the choices, then click Save access

Your first connection’s dialog opens with nothing ticked. After that, a new connection’s dialog opens with the choices of the connection you used most recently, so saving it unchanged grants the same cards and logins, and the same three switches: Let this app create and change its own logins, Ask me before every purchase from this app and Fill a test card instead of my card. Check all of them for this agent before you click Save access.
You can change or revoke the connection on the same page at any time. See Connected apps.

Let the tools run without asking

Claude Code asks before each MCP tool call unless a rule allows it, and in auto mode it can refuse a call outright, mid-checkout. Add this rule to the permissions in ~/.claude/settings.json, keeping any rules already there:
~/.claude/settings.json
mcp__agent-vault matches every tool the agent-vault server exposes and nothing else, so it loosens nothing for other servers or shell commands. Restart Claude Code after adding it.

Check it works

Ask Claude Code to call the Agent Vault tool get_token_catalog. It answers with the mock tokens for the cards and logins you allowed, such as av_card_1_number_u7x2k. Your real card number never reaches Claude Code.

Troubleshooting

The login needs a real terminal to read the pasted address. Run it yourself in your own terminal, not through an agent’s shell tool. Over SSH, use ssh -t.
The add command saves it for one project. Run it again with --scope user to add it for every project.
The connection has nothing granted yet. Follow Choose what it may use, then ask again.
For Claude Code, the dashboard recommends an API key over signing in: in testing, sign-in was slower or failed more often. Its Claude Code setup leads with one command that runs the local server with your key. On Overview, open Connect another agent and pick Claude Code, or see MCP setup.

Next

Your first checkout

Have Claude Code buy something, start to finish.

Tool reference

Every tool your agent now has.