Connect Claude Code and other MCP clients
Header-auth setup for clients that use an API token instead of browser sign-in.
Claude's apps sign in through the browser with no token to copy (see the standard setup). Clients that authenticate with a request header instead - Claude Code in the terminal, and most other MCP clients - use an API token.
1. Create a token
Settings, then AI Connector - create a token and copy it. Treat it like a password: it acts as your AMZ Vault user, with your permissions, and every action it takes is audited under your name.
2. Add the connector
Claude Code (terminal):
claude mcp add --transport http amz-vault https://www.amz-vault.com/mcp --header "Authorization: Bearer <your token>"
Clients that read an mcp.json (Cursor, VS Code, and others):
{
"mcpServers": {
"amz-vault": {
"url": "https://www.amz-vault.com/mcp",
"headers": { "Authorization": "Bearer <your token>" }
}
}
}
Notes
- Revoke any time from the same Settings page - revocation is immediate.
- One token per client is good hygiene; names on the tokens page tell them apart.
- Team members connect with their own AMZ Vault login's token and get their own granted permissions - read-only roles cannot stage changes through any client.
- Currently the workforce runs on Claude and ChatGPT; other clients can use the full read and staging toolset today.