agent-bundle

One command to give your AI agent the three things it needs to act online — a card (Agentcard), an inbox (AgentMail), and a phone number (AgentPhone). agent-bundle walks you through installing all three, one at a time, and registers each as an MCP server.

npx agent-bundle

What it does

A guided, three-step onboarding:

1. Agentcard — installs the agent-cards CLI, signs you up (one magic-link email click), registers + authenticates the MCP server via agent-cards setup-mcp (hosted HTTP), and offers to switch to production (real cards).
2. AgentMail — takes your API key (or points you to the console to make one) and registers the hosted HTTP MCP server (mcp.agentmail.to).
3. AgentPhone — fully automated: requests a verification code by email, you type it in, it provisions a real US number, and registers the stdio MCP server (npx -y agentphone-mcp). No browser.
4. Agent Bundle — with all three installed, it offers the bundle subscription: $20/mo for Agentcard + AgentMail + AgentPhone together (about half of buying them standalone). It opens a Stripe-hosted checkout on the bundle server (theagentbundle.com), keyed by your email — no charge until you enter a card and confirm on Stripe's page. Re-run with --only bundle anytime.

Every account is created in production — real inboxes, real numbers, and live Agentcard cards. There is no test or sandbox mode.

All MCP servers are registered at user scope (available in every project), via claude mcp add.

It's idempotent — anything already configured is skipped, so it's safe to re-run.

Options

| Flag | Effect | |---|---| | --only <agentcard\|agentmail\|agentphone\|bundle> | Run just one product, or bundle for the $20/mo bundle checkout. | | --dry-run | Print what it would do, change nothing. | | --yes, -y | Accept defaults, skip confirmations. | | --no-color | Plain output. | | --help, -h | Help. |

Skip prompts with env vars

export AGENTMAIL_API_KEY=am_...
export AGENTPHONE_API_KEY=sk_live_...
npx agent-bundle

Preview without changing anything

Use --dry-run to print every step it would take without touching your config or creating accounts:

npx agent-bundle --dry-run

How config is written

By default it uses the claude CLI (claude mcp add --transport http …). If claude isn't on your PATH, or you set AGENT_BUNDLE_MCP_CONFIG, it writes the MCP entries to that JSON file instead. API keys are stored as request headers in the config and never printed to the terminal.

Requirements

Node 18+ (for built-in fetch). Zero runtime dependencies.