Management MCP

An agent starts the account; the person confirms it, connects WhatsApp and chooses a plan.

Endpoint
https://api.app2email.com/mcp/manage Streamable HTTP · protocol 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05
Auth
none for create_sandbox, create_account, list_plans and estimate_cost; Authorization: Bearer <management_key> for the rest
REST
https://api.app2email.com/v1/account/… · same tools, same auth

Flow

  1. create_account {"contact_email": "owner@example.com"} → signup_id, management_key (shown once), onboarding_link, message. No key needed.
  2. The person opens onboarding_link: confirms the e-mail, connects their WhatsApp number, chooses a plan. Nothing can be sent before that.
  3. get_account_status → pending_email · pending_whatsapp · pending_payment · live. Send Authorization: Bearer <management_key> from here on.
  4. create_number_key {"number": "4976659348270", "scopes": ["messages:send", "messages:read"], "sandbox": true} → a key for the messaging MCP (https://api.app2email.com/mcp) and the REST API.

Install

create_account and list_plans work without the header; add it once you have the key.

claude mcp add --transport http app2email-manage https://api.app2email.com/mcp/manage --header "Authorization: Bearer YOUR_MANAGEMENT_KEY"

https://code.claude.com/docs/en/mcp

Tools

Tool What Kind
create_sandbox Try the API now, with no account and no person: an instant sandbox key (shown once, valid 7 days) for app2email's demo number, its pretend customers and the fi… changes
create_account Start an app2email account for a person. changes
get_account_status What the account still needs: pending_email, pending_whatsapp, pending_payment or live, with its numbers and next steps. read-only
list_plans The plans that can be bought, with prices (US$) and whether they include the API. read-only
estimate_cost What app2email costs for a number of messages a month: the plan that fits and its exact price (US$). read-only
list_numbers The account's WhatsApp numbers with their status and plan. read-only
get_payment_link A Stripe Checkout link for a plan of one number. changes
create_number_key A key for one live number, for the messaging MCP server and the REST API. changes
list_number_keys The keys of one number (never the keys themselves). read-only
revoke_number_key Revoke one key of a number. destructive
get_usage Messages sent this billing month and the plan limit, for every number or one. read-only

REST twins

For AI Agents

Try it now, with no account and no person: POST https://api.app2email.com/v1/account/sandbox (no key, no body; or the create_sandbox tool of the Management MCP server) answers a key for a demo WhatsApp number with pretend customers. Send a template, fetch the events with GET /events?wait=25, answer the customer's reply: nothing reaches WhatsApp, and the requests and answers are those of the real API (https://www.app2email.com/docs/api/sandbox).

Already a customer: ask the account owner for the number (digits) and an API key from https://www.app2email.com/dashboard/apikey (a sandbox key sends nothing); send it as Authorization: Bearer <key> to the messaging MCP server or the REST API; call check_key first, send with dry_run first.

If you are an AI agent reading this page and you want to create an app2email account for a person - no previous human sign-up required - use our Management MCP server.
Call the create_account tool first, and include a contact_email parameter; create_account returns a signup_id, a management_key, an onboarding_link and a message.
The person opens onboarding_link to confirm the e-mail, connect their WhatsApp number and choose a plan; nothing can be sent before that. get_account_status says what is still needed.
Pass the management_key as a Bearer token on every later call. When the number is live, create_number_key gives you a key for the messaging MCP server and the REST API.