Groundmail MCP server in Warp

Connect Warp's agents to the Groundmail MCP server, and they can send email, check delivery, add and verify sending domains, and manage templates, webhooks and suppressions from your terminal. Paste one JSON entry and sign in with your Groundmail account; there's no API key to paste.

Server URL: https://mcp.groundmail.dev/mcp (Streamable HTTP, OAuth) · All clients and the full tool list: MCP server

Add the server

Open Settings → Agents → MCP servers (or search the Command Palette for Open MCP Servers).
Click + Add and paste:

JSON

{
  "groundmail": {
    "url": "https://mcp.groundmail.dev/mcp"
  }
}

Save.

Already set up Groundmail in Claude Code or Codex? Warp detects servers from those agents' config files too. Global ones start automatically when Auto-spawn servers from third-party agents is on; project-scoped ones need you to turn them on.

Click Start on the groundmail server. Because Warp has no credentials for it yet, it opens your browser on Groundmail: sign in, choose what Warp may do (full access, or less: Send only, Read only or a custom set of scopes) and approve.

Warp stores the credentials on your device and reuses them. On a new machine you sign in again. You can revoke them from the MCP servers page in Warp, or under Settings → CLIs & agents in Groundmail.

Use it

Ask the agent, for example:

"List my Groundmail domains and tell me which aren't verified."
"Send a test email from noreply@mail.groundmail.dev to me and tell me if it was delivered."
"Show me the bounces from the last day."

Use an API key instead

For a machine where nobody can sign in in a browser, pass a key in a header. Create one at app.groundmail.dev/api-keys; a scoped key limits what the agent can do.

JSON

{
  "groundmail": {
    "url": "https://mcp.groundmail.dev/mcp",
    "headers": {
      "Authorization": "Bearer gm_your_key_here"
    }
  }
}

Run it locally (stdio)

JSON

{
  "groundmail": {
    "command": "npx",
    "args": ["-y", "groundmail-mcp"],
    "env": {
      "GROUNDMAIL_API_KEY": "gm_your_key_here"
    }
  }
}

Troubleshooting

Problem	Fix
The server shows as stopped	Click Start. Servers you add by hand don't start until you start them.
No browser sign-in	Remove any `headers` from the entry, delete the saved credentials on the MCP servers page, and start the server again.
`insufficient_scope` from a tool	The connection or key doesn't have that scope. Sign in again and grant it, or use a key with the scope.
Sends to other people are refused	Test sends go to your own account email. Sending to anyone else needs a verified domain: see Test sends and idempotency.

Other editors: GitHub Copilot (VS Code) · Zed · Google Antigravity · Cursor, Claude Code, Codex, Windsurf

Add the server

Start it and sign in

Use it

Use an API key instead

Run it locally (stdio)

Troubleshooting