What is Gork mail (also searched as Grokmail or gork.email)?

Gork mail (gork.email, often spelled Grokmail or Grok mail) is programmable email infrastructure designed specifically for AI agents, LLMs, and autonomous workflows. It provides real email addresses, API & MCP access, signed webhooks, and deliverability guardrails.

How does Gork mail work for AI agents?

Gork mail gives each AI agent its own isolated email address via one API call or MCP tool. Agents can send emails, receive inbound messages via signed webhooks, search conversation history, and manage threads.

Can I use Gork mail with Claude Code, Cursor, or LangChain?

Yes. Gork mail ships a native Model Context Protocol (MCP) server. Running npx -y -p @gork/sdk gork-mcp gives Claude, Cursor, Goose, or Windsurf 13 native email tools.

Back to all blueprints

Templates · Multi-Agent Fleet / Multi-Agent Swarm Orchestrator

Multi-Agent Fleet (100 Programmatic Workers)

Provisions 100+ isolated email identities for specialized worker agents without Google Workspace fees.

Create handle All blueprints

Operational Bottleneck

A fleet of agents needs an address each, and admin-per-seat mailboxes are the wrong shape for that: they are priced and administered per person, and expect a human to own the account.

Managing dozens of separate IMAP/SMTP credentials with passwords causes operational chaos, secret leaks, and maintenance failure when passwords expire.

Gork Infrastructure Layer

Structured <90ms Delivery

One API call provisions an inbox under your own domain, with SPF, DKIM, and DMARC records generated and verified over DNS. Manage quota, spend limits, and key scoping from a single dashboard.

Execution Artifacts

System prompt, SDK code & webhooks

Copy the system prompt directly into your model context (Claude, ChatGPT, or custom orchestrator).

system-prompt.txt

1You are the Fleet Communications Dispatcher for an Autonomous Agent Workforce.
2Your role is to route incoming company emails to the correct specialized worker inbox based on sender intent, department, and SLA urgency.
3
4ROUTING MATRIX:
5- Inbound leads & sales -> route to `sales-swarm@agents.yourdomain.com`
6- Invoices & billing issues -> route to `finance-worker@agents.yourdomain.com`
7- Bug reports & API errors -> route to `dev-triage@agents.yourdomain.com`
8- Customer support & how-to -> route to `support-l1@agents.yourdomain.com`
9
10SAFETY RULES:
11- Never cross-contaminate data between tenant organizations.
12- Prevent recursive loops: If an email originates from another internal agent inbox, verify message depth < 3 turns before dispatching.
13
14OUTPUT SCHEMA:
15{
16  "targetInbox": string,
17  "classification": string,
18  "priority": "P0" | "P1" | "P2" | "P3",
19  "dispatchAction": "forward" | "quarantine" | "auto_acknowledge"
20}