# Groundmail [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/Groundmail/groundmail-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 3984  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/groundmail

## Description
Send transactional email and manage domains, templates, webhooks and suppressions with Groundmail.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `GROUNDMAIL_API_KEY`, `GROUNDMAIL_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Groundmail does

The Groundmail MCP server exposes Groundmail’s transactional email features to MCP-compatible clients. An agent can send messages, inspect recent email activity, and look up delivery results such as bounces. It can also work with sending domains, templates, webhooks, suppressions, address validation, deliverability reporting, and DMARC monitoring.

Domain operations include adding and verifying domains. DNS records can be applied through Cloudflare, Vercel, or GoDaddy. The server also supports importing data from other providers and managing customer tenants. A tenant represents a customer an account sends mail for and can be created, updated, paused, resumed, and reviewed for statistics. Sends, domains, and suppressions can be associated with a tenant.

The Groundmail MCP server fits the Communication category for workflows that need an AI client to operate transactional email systems rather than compose or send ordinary personal mail.

## How it works

Groundmail provides a hosted MCP endpoint at `https://mcp.groundmail.dev/mcp`. Clients connect over HTTP and authenticate through a browser-based OAuth flow, or send an API key as a bearer token. Access can be scoped as Full, Send only, or Read only, and access can later be revoked from Groundmail settings.

The package also supports local execution. A stdio process runs with `npx -y groundmail-mcp`, while local HTTP mode runs with `npx -y groundmail-mcp --http --port 3000`. Local HTTP clients connect to `http://127.0.0.1:3000/mcp` and provide the bearer token on requests. The local service exposes `GET /health`; the hosted service has a corresponding health endpoint.

Tools include read-only and destructive annotations plus output schemas, allowing clients to distinguish operation types and interpret structured results.

## Setup and configuration

For the hosted option, add the MCP URL to the client and complete authentication. Claude Code, Cursor, Claude.ai, and ChatGPT each have documented connection paths in the project README. Cursor can also run the package through stdio or connect to a local HTTP process.

Stdio and local HTTP use `GROUNDMAIL_API_KEY`. Set `GROUNDMAIL_API_URL` only when the MCP process should target a different API endpoint, such as a local API. Hosted HTTP can use OAuth or a bearer token instead of a locally configured key.

## Tools and capabilities

The Groundmail MCP server covers:

- Sending, listing, and looking up emails
- Adding, verifying, and configuring sending domains
- Applying DNS records through Cloudflare, Vercel, or GoDaddy
- Managing templates, webhooks, and suppressions
- Validating addresses and reviewing deliverability
- Monitoring DMARC status
- Importing from other providers
- Creating and managing tenants, including tenant statistics

## Limitations and notes

The platform is described as transactional email only, not newsletters or cold outreach. OAuth is available for the hosted endpoint, while local modes require API-key authentication. The exact complete tool list is maintained in Groundmail’s MCP documentation.

_Full upstream README: https://allmcps.com/mcp/groundmail/readme_