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.

Devin + Gork Mail

Give Devin its own inbox

Gork Mail is the best way to give Devin 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 Devin. 13 email tools appear, each call scoped to the inbox you connect. The same MCP server serves CLI agents, editors, and the Gork API.

1Add GORK_API_KEY to Devin project environment secrets.

2Configure the Devin playbook with the Gork Mail SDK or MCP integration.

3Prompt Devin to handle email-gated workflows without human intervention.

Run directly in your terminal to install the MCP tool.

# Add to Devin playbook / machine secrets
export GORK_API_KEY="gork_live_YOUR_KEY"
npx -y -p @gork/sdk gork-mcp

Try it

One prompt away

Add to Devin issue description or repository playbook. Copy it, paste it into Devin — it calls the tools itself.

Devin

Run end-to-end user signup tests. Use Gork Mail MCP to create a fresh inbox test-user@yourcompany.com, trigger registration, read the confirmation code, and finish signup.

Paste into Devin — no code, no config

Why email

Why your Devin 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

Devin executing email verification in Python:

from gork import Gork
import re, os

client = Gork(api_key=os.environ["GORK_API_KEY"])
inbox = client.inboxes.create(username="devin-runner", domain="yourcompany.com")

# Wait for confirmation code
messages = client.messages.search("verification", inbox_id=inbox.id)
code = re.search(r"\b\d{6}\b", messages[0].text_body).group(0)
print(f"Devin retrieved code: {code}")

Templates

Live Devin 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