agentleFS
GroundmailGroundmail/groundmail-skills/skills/groundmail-mcp/SKILL.md

groundmail-mcp

Skill0 starsChanged 23 days agoMITView on GitHub

Use when installing, configuring or using the Groundmail MCP server in Claude, Claude Code, ChatGPT, Cursor or another MCP client: hosted https://mcp.groundmail.dev/mcp with OAuth, the groundmail-mcp npm package (stdio or --http), GROUNDMAIL_API_KEY / Bearer gm_, and tools such as send_email, verify_domain, create_template and get_deliverability.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always use the full hosted URL including /mcp.

    line 22
  2. Distinctive:

    Never ask for or accept payment card numbers, passwords, government ID numbers, health information or other sensitive personal data in chat.

    line 118
  3. Distinctive:

    Never put the API key in client-side code, even when using MCP during development.

    line 126

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Groundmail MCP

  • Hosted: https://mcp.groundmail.dev/mcp (Streamable HTTP). OAuth sign-in, or Authorization: Bearer gm_….
  • Local: npx -y groundmail-mcp (stdio) or npx -y groundmail-mcp --http (http://127.0.0.1:3000/mcp), with GROUNDMAIL_API_KEY=gm_…. Optional GROUNDMAIL_API_URL.

Always use the full hosted URL including /mcp. For API rules (sandbox, idempotency, error codes) also load the groundmail skill.


Install

Claude Code

claude mcp add --transport http groundmail https://mcp.groundmail.dev/mcp

Then /mcp → groundmail → Authenticate, and sign in to Groundmail in the browser. Headless or CI:

claude mcp add --transport http groundmail https://mcp.groundmail.dev/mcp \
  --header "Authorization: Bearer $GROUNDMAIL_API_KEY"
# or local stdio
claude mcp add groundmail --env GROUNDMAIL_API_KEY=gm_your_key_here -- npx -y groundmail-mcp

Claude (claude.ai / Desktop)

Settings → Connectors → Add custom connector → URL https://mcp.groundmail.dev/mcp → Connect → sign in to Groundmail.

ChatGPT

Developer mode (Settings → Apps & Connectors → Advanced) → Create connector → URL https://mcp.groundmail.dev/mcp, authentication OAuth → sign in to Groundmail.

Cursor

.cursor/mcp.json or ~/.cursor/mcp.json, hosted with an API key:

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

Or local stdio:

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

Restart Cursor after editing. The dashboard Install in Cursor button writes this with the key filled in. Keep config files with keys out of git.


Tools

ToolPurpose
send_emailfrom, to, subject, html/text/reply_to, or template_id/template_alias + variables
list_emails / get_emailRecent sends, status of one send
get_batch / cancel_batchA batch send's status counts; cancel its still-scheduled emails
list_received_emailsInbound mail; in_reply_to_email: "msg_…" lists the replies to one send
list_domains / create_domainSending domains
create_mailbox / wait_for_mailbox_messageAn agent's own address, and the next message to it. See the groundmail-mailboxes skill
reply_to_mailbox_message / send_mailbox_messageReply in a thread, or send from a mailbox
apply_domain_dns / verify_domainPublish DNS (Cloudflare, Vercel, GoDaddy), then verify
list_templates / get_template / create_template / publish_templateTemplates
list_webhooks / create_webhook / delete_webhookWebhook endpoints
list_webhook_deliveries / get_webhook_delivery / resend_webhook_deliveryThe delivery log: every attempt, the payload and the reply, kept 30 days
send_test_webhook_eventSimulated event to webhooks; no email sent
list_suppressions / add_suppression / remove_suppressionSuppression list
list_category_opt_outs / remove_category_opt_outOne-click unsubscribes from product or newsletter email (per tenant or account-wide)
validate_emailCheck one address: valid / risky / invalid, reasons, typo suggestion. Free; sends nothing
create_burrowguard_site / update_burrowguard_site / list_burrowguard_sites / list_burrowguard_checksBurrowGuard: block bots and bad addresses on sign-up forms. Create returns the secret once: put it in the app's env as GROUNDMAIL_BURROWGUARD_SECRET, never in code or chat. watch_only shows what would be blocked without blocking anyone
get_deliverabilityBest-effort metrics for 7d or 30d (not inbox placement guarantees)
enable_dmarc_monitoring / get_dmarc_reportDMARC monitoring: record to publish, then sources, pass rates and enforcement readiness
get_test_inbox_address / wait_for_test_email / list_test_emails / get_test_emailEmail testing: a fresh address on the team's test domain (mail from any provider is caught, never delivered), then wait for the email and read its code and links
list_tenants / create_tenant / get_tenant / update_tenant / pause_tenant / resume_tenant / get_tenant_statsTenants: one per customer you send for (pay as you go and Dedicated)
import_from_provider / get_import_reportBeta. Import from SendGrid, Postmark, Mailgun, Resend or Amazon SES (dry_run first), then read the report. Local server only; on the hosted server, send the user to https://app.groundmail.dev/import

Full list with one line per tool: https://docs.groundmail.dev/ai/mcp

Rules for agents

  1. First send: from noreply@mail.groundmail.dev, to the user's Groundmail account email. Other recipients are refused until a domain is verified and the user has set up billing in the dashboard.
  2. Confirm with the user before send_email to anyone but them, create_domain, delete_webhook, resend_webhook_delivery, remove_suppression or remove_category_opt_out.
  3. Failed tool calls return the API message, code: … with the HTTP status, and a how to fix link to https://docs.groundmail.dev/errors#<code>. Follow it instead of retrying blindly.
  4. send_email does not take an idempotency key. For app code that retries, use the SDK or HTTP with Idempotency-Key.
  5. Never ask for or accept payment card numbers, passwords, government ID numbers, health information or other sensitive personal data in chat; the user enters billing and account details only in the Groundmail dashboard.

MCP vs SDK

Prefer MCPPrefer SDK / HTTP in app code
Interactive setup, DNS, one-off sends, checking statusProduction send paths, CI, retries with idempotency

Never put the API key in client-side code, even when using MCP during development.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.