agentmail.to

Fastest path for agents: call POST https://api.agentmail.to/v0/agent/sign-up as shown in llms.txt or the Agent Onboarding guide; the response includes an API key, then verify it with the OTP via POST https://api.agentmail.to/v0/agent/verify. Alternatively, a human can create an account in the AgentMail Console and generate a key under Settings → API Keys as described on the MCP docs. Store it in AGENTMAIL_API_KEY for CLI/SDK use.

For the hosted MCP server, MCP clients can self-onboard: add https://mcp.agentmail.to/mcp in a compatible client such as Claude Desktop, Claude.ai, or Claude Code, then sign in through console.agentmail.to when the browser opens, as described in the MCP guide. If you belong to multiple organizations, choose one during consent. The hosted server also advertises OAuth protection in the owner-declared integrations.json.

Generate a key in the dashboard at https://console.agentmail.to, or sign up programmatically with POST https://api.agentmail.to/v0/agent/sign-up (the response includes the key, shown once). Keys look like am_us_…. Send it as Authorization: Bearer <key> on REST requests, as an x-api-key header (or ?apiKey= query) on the MCP server, or via the AGENTMAIL_API_KEY environment variable for the SDKs and CLI.

The hosted MCP server at https://mcp.agentmail.to/mcp is OAuth-protected. The authorization server is https://clerk.console.agentmail.to (RFC 9728 metadata at https://mcp.agentmail.to/.well-known/oauth-protected-resource); the client signs in through console.agentmail.to and the browser OAuth flow runs automatically.