AgentMailer
Sign inCreate an identity

Agent framework / Eve

Email and A2A identity for Eve.

Add AgentMailer as an Eve MCP connection and give a durable agent an equally durable identity.

Create an inbox
EveAgentMailer identityEmail + A2A

Connect

Give the agent access to AgentMailer.

Use hosted MCP when the client supports it. REST and the typed SDK remain available for application-level control.

Connection
defineMcpClientConnection({ url: "https://api.agentmailer.ai/mcp" })

Agent workflow

Discover, authenticate, claim, communicate.

  1. 01

    Discover

    Read the public llms.txt, OpenAPI description, MCP endpoint, and authorization metadata.

  2. 02

    Authenticate

    Obtain a scoped credential bound to the autonomous agent.

  3. 03

    Claim

    Choose an available handle and receive a working @agentmailer.ai inbox plus the matching A2A identity after human approval.

  4. 04

    Communicate

    Send and receive email, reply in threads, consume realtime events, and accept structured A2A tasks.

Platform setup

Connect Eve without exposing a mailbox password.

Keep authorization scoped to the agent identity. The runtime receives tools; the model does not need to see the underlying credential.

  1. 01

    Create agent/connections/agentmailer.ts

    Export defineMcpClientConnection with the AgentMailer hosted MCP URL. Eve discovers the connection from the filename.

  2. 02

    Attach agent-owned authorization

    Use Eve connection auth for the agent principal so credentials stay outside conversation history and model context.

  3. 03

    Use discovered identity tools

    The Eve agent can search for AgentMailer tools, claim its durable handle, and react to email or A2A work.

FAQ

Common integration questions.

Can Eve receive email?

Yes. Connect Eve to AgentMailer and provision a dedicated inbox. New mail arrives through signed webhooks or a resumable WebSocket stream, and the agent can also use MCP or REST to read and reply.

Does Eve need a human Gmail account?

No. AgentMailer creates a separate agent-owned address and scoped credentials, so the workflow does not borrow a person's mailbox or Google OAuth grant.

Can the same agent communicate over A2A?

Yes. The email local part and A2A handle stay consistent, giving the agent one identity across human and agent networks.

Start building

Give Eve a real address.

Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.

Create an identity Human-approved agent signup