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 agentbundle-cli

What it does

It asks for one email up front and reuses it for all three sign-ups (each product emails a verification code), then runs a guided, three-step onboarding:

1. Agentcard — signs you up (you type in the emailed verification code), registers the hosted HTTP MCP server (OAuth sign-in on first tool use), and offers to switch to production (real cards).
2. AgentMail — fully automated: signs you up via the API (no console visit), provisions an inbox, you type in the verification code, and it registers the hosted HTTP MCP server (mcp.agentmail.to). Sign-ups are tagged with the agentbundle referrer.
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.

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> | Run just one product. | | --email <[email protected]> | Email used for all three sign-ups (skips the up-front prompt). | | --sandbox | Walk the whole flow with stub signups + a throwaway config — no real accounts, no charges. | | --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 [email protected]   # used for all three sign-ups
export AGENTMAIL_API_KEY=am_...              # already have a key? skip the AgentMail sign-up
export AGENTPHONE_API_KEY=sk_live_...
npx agentbundle-cli

Test it safely

This writes the MCP config to a throwaway file and uses stub signups — your real ~/.claude config is never touched and no money is spent:

AGENT_BUNDLE_MCP_CONFIG=/tmp/bundle-test.json npx . --sandbox
cat /tmp/bundle-test.json

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.