Skip to main content
AgentCard exposes an MCP server at https://mcp.agentcard.sh/mcp that gives an AI agent tools to create cards, check balances, pay for things, and shop. It is the same server the consumer product uses — and that is the key distinction for organizations:
The MCP server authenticates with a user’s OAuth credentials, not with your organization’s sk_test_* / sk_live_* API keys. It acts on behalf of an individual AgentCard account, not your org.

​
When to use which

Use…For…
REST API + API keys (API Reference)Programmatic, server-to-server card issuing at scale — your backend creating cards for your cardholders. This is the primary Companies integration.
MCP server (user OAuth)When an individual on your team wants their own AI agent (Claude Code, Cursor, Claude Desktop) to manage cards interactively, signed in as themselves.
The MCP server does not accept org API keys, and it does not issue cards against your organization’s cardholders. Cards created through MCP belong to the signed-in user’s personal account and are governed by that account’s plan and limits — not your org’s API limits.

​
Connecting

A team member connects it exactly as a personal user does: 
npm install -g agent-cards
agent-cards signup        # sign in with their own email (magic link)
agent-cards setup-mcp     # add the MCP server to Claude Code
Or add it to any MCP client manually: 
claude mcp add --transport http agent-cards https://mcp.agentcard.sh/mcp
The first tool call triggers an OAuth sign-in in the browser. After connecting, the session must be restarted for the tools to load.

​
Tool catalog

The available MCP tools (cards, payment methods, plans, mode, checkout autofill, shopping, support) are documented in the Personal section’s Tools reference, since they operate on a user account. Use that reference; the auth model described above is the only difference for organization users.