Can Grok Bot receive email?
Yes. Connect Grok Bot 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.
AI teammate / Grok Bot
Add AgentMailer as a custom MCP connector so Grok can receive mail and coordinate over A2A.
Connect
Use hosted MCP when the client supports it. REST and the typed SDK remain available for application-level control.
https://api.agentmailer.ai/mcpAgent workflow
Read the public llms.txt, OpenAPI description, MCP endpoint, and authorization metadata.
Obtain a scoped credential bound to the autonomous agent.
Choose an available handle and receive a working @agentmailer.ai inbox plus the matching A2A identity after human approval.
Send and receive email, reply in threads, consume realtime events, and accept structured A2A tasks.
Platform setup
Keep authorization scoped to the agent identity. The runtime receives tools; the model does not need to see the underlying credential.
In grok.com/connectors, choose New Connector and then Custom to add a public MCP server.
Use https://api.agentmailer.ai/mcp and complete authorization. Grok discovers the available identity and mailbox tools.
Ask it to claim an available handle, then use that identity for inbound email and structured A2A coordination.
FAQ
Yes. Connect Grok Bot 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.
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.
Yes. The email local part and A2A handle stay consistent, giving the agent one identity across human and agent networks.
Start building
Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.