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.

Claude Code + Gork Mail

Give Claude Code its own inbox

Gork Mail is the best way to give Claude Code its own inbox. Send email, receive replies, and manage full conversation threads from a dedicated inbox each bot owns.

Start for free Docs

Install

One command

Add the Gork MCP server with the command or config below, then restart Claude Code. 13 email tools appear, each call scoped to the inbox you connect. The same MCP server serves CLI agents, editors, and the Gork API.

1Run the claude mcp add command in your terminal.

2Provide your secret Gork API key when prompted.

3Start a Claude Code session with claude.

4Prompt Claude: "Read recent inbound emails from billing@yourcompany.com and summarize any failed payment notifications."

Run directly in your terminal to install the MCP tool.

claude mcp add gork -- npx -y -p @gork/sdk gork-mcp --api-key=$GORK_API_KEY

Try it

One prompt away

Run Claude Code in your terminal with this direct instruction. Copy it, paste it into Claude Code — it calls the tools itself.

Claude Code

Check my Gork Mail inboxes for unread messages. If any email contains an authentication code or password reset link, extract the link and display it.

Paste into Claude Code — no code, no config

Why email

Why your Claude Code agent needs its own inbox

One address per bot

Not one connection shared across the fleet. The native Gmail plugin gives every bot on your account the same credential. Gork Mail gives each bot a real address it owns.

Real inbound

The Gmail plugin lets your bot read your inbox. Gork Mail lets people, or systems, email the bot directly, with full thread history and reply_to_message.

Scoped blast radius

One flagged send scopes to one bot's address, not your entire Gmail reputation.

Code

Working code

Automate email reading and parsing directly from your shell:

# Run Claude Code in your workspace
claude "Read the latest verification email sent to test-runner@yourcompany.com, extract the 6-digit OTP code, and run 'pnpm test:auth --code <OTP>'"

# Claude Code automatically:
# 1. Invokes gork_read_emails({ inbox: "test-runner@yourcompany.com" })
# 2. Extracts regex match for r"\b\d{6}\b"
# 3. Executes the test script with the parsed code

Templates

Live Claude Code bots, each running on its own Gork Mail inbox. Open one to add it to your account and email it.

Sales

Lead

Qualifies inbound demo email. Replies with times or a self-serve link.

Prompt Trigger

“Monitor incoming sales inquiries on partnerships@yourcompany.com. If an enterprise lead emails, evaluate company size and reply with demo calendar links.”

Gork Mail

Support

Desk

Tier-one support inbox. Answers from your FAQ, escalates the rest.

Prompt Trigger

“Check support@yourcompany.com for unread tickets. Draft answers using our knowledge base and tag human engineers on billing disputes.”

Gork Mail

Engineering

Crash Triage

Ingests CI/CD crash dumps and error emails, locates the failing code, and opens a pull request.

Prompt Trigger

“Read incoming error emails from Sentry on alerts@yourcompany.com, parse the stack trace, locate the bug in our codebase, and reply with the commit fix.”

Gork Mail

Operations