MinuteMail MCP Server
MinuteMail as MCP (Model Context Protocol) tools: let AI agents and MCP clients operate ephemeral mailboxes, emails, attachments, custom domains, teams, and mock OAuth identities for testing email and auth flows.
接入你的智能体
發布者自己的 URL。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
https://mcp.minutemail.co/mcp上方的 Claude 按鈕會開啟 Claude,並填好名稱和 URL。你仍需在那裡確認。
claude mcp add --transport http io.github.minutemailco-mcp-server https://mcp.minutemail.co/mcpRun in a terminal.
{ "mcpServers": { "io.github.minutemailco-mcp-server": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.minutemail.co/mcp" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
MinuteMail as MCP (Model Context Protocol) tools: let AI agents and MCP clients operate ephemeral mailboxes, emails, attachments, custom domains, teams, and mock OAuth identities for testing email and auth flows.
Ephemeral mailboxes and a mock OAuth IdP for testing email and auth flows — 39 API-driven tools
https://mcp.minutemail.co/mcp (Streamable HTTP, protocol
revision 2025-06-18)Bearer mmak_...). The server is a
stateless proxy — it holds no credentials, sessions, or local storage of
its own; your key is forwarded verbatim to the MinuteMail API, where scopes
and quotas are enforced. All state (mailboxes, mails, identities) lives in
the MinuteMail platform behind it.io.github.minutemailco/mcp-server and on
Smithery.Sign up at minutemail.co (free during early access)
Create an API key in the dashboard
Configure your MCP client to send it as the Authorization header:
Authorization: Bearer mmak_XXXXXXXX
Claude Code / Claude Desktop / Cursor / any Streamable HTTP client:
https://mcp.minutemail.co/mcpAuthorization: Bearer mmak_...Claude Code CLI:
claude mcp add --transport http minutemail https://mcp.minutemail.co/mcp \
--header "Authorization: Bearer mmak_XXXXXXXX"
Claude Desktop / clients with an mcpServers JSON config (e.g.
claude_desktop_config.json / ~/.cursor/mcp.json):
{
"mcpServers": {
"minutemail": {
"type": "http",
"url": "https://mcp.minutemail.co/mcp",
"headers": {
"Authorization": "Bearer mmak_XXXXXXXX"
}
}
}
}
Some clients (older Claude Desktop builds) only support local
stdioservers in their JSON config. If yours rejectstype: "http", use the built-in remote/connectors UI with the URL and header above, or run mcp-remote as a stdio bridge:{ "mcpServers": { "minutemail": { "command": "npx", "args": [ "mcp-remote", "https://mcp.minutemail.co/mcp", "--header", "Authorization: Bearer mmak_XXXXXXXX" ] } } }
For a guided walkthrough, see the docs: docs.minutemail.co/mcp/getting-started.
Raw JSON-RPC (what the clients do under the hood):
curl -s https://mcp.minutemail.co/mcp \
-H 'Authorization: Bearer mmak_XXXXXXXX' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"mailboxes.create","arguments":{"expiresIn":30}}}'
Every tool maps 1:1 to a route of the MinuteMail API. All calls require the
Bearer API key; write operations require the matching scope (mailboxes,
domains, team, identities).
mailboxes scope)mailboxes scope)archived.list, archived.get,
archived.delete, archived.reactivate.
domains scope)domains.list, domains.register, domains.verify, domains.delete.
team scope)team.members.list, team.members.add, team.members.get, team.members.delete,
team.invitations.create, team.invitations.list, team.invitations.delete.
identities scope)identities.list, identities.create, identities.update, identities.get,
identities.delete, oauth.clients.list, oauth.clients.create,
oauth.clients.get, oauth.clients.delete, oauth.clients.rotate_secret.
identities.update patches profile fields, isActive (activate/deactivate),
emailVerified (drives the email_verified claim), and custom claims
merged into issued ID tokens and userinfo responses.
Tool results are returned as MCP text content carrying the API's JSON
response. Non-2xx responses become isError: true results with the HTTP
status and body (401 invalid key, 403 scope/domain, 429 quota with remaining
count, 502 upstream down).
mailboxes.create (expiresIn 30)
↓
your app under test sends a verification email to the mailbox address
↓
mails.list → mails.get (extract the code / link)
↓
assert the flow completed — the mailbox expires on its own
The server is a single static Go binary in a scratch image (~7 MB):
docker run -p 8080:8080 \
-e API_BASE=https://api.minutemail.co \
ghcr.io/minutemailco/mcp-server:latest
# or from Docker Hub:
docker run -p 8080:8080 \
-e API_BASE=https://api.minutemail.co \
chrptvn/minutemail-mcp:latest
Self-hosting still requires MinuteMail API keys — the server is a stateless proxy over the hosted API, not a standalone implementation. It keeps no sessions or local data; every mailbox, mail, and identity is stored by the MinuteMail API it forwards to.
GET /health for liveness; GET /metrics for Prometheus counters.
API-key management is not exposed via MCP — manage keys from the web app.
Go 1.23, stdlib plus prometheus/client_golang.
go test ./... # unit tests
go vet ./...
go run . # local server on :8080
MIT — © MinuteMail.co
Ephemeral mailboxes and a mock OAuth IdP for testing email and auth flows — 39 API-driven tools
{ "mcpServers": { "io.github.minutemailco-mcp-server": { "url": "https://mcp.minutemail.co/mcp", "headers": {} } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 http 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
MinuteMail 透過 HTTP 存取。
上次檢查時間:2026-11-09。 Ephemeral mailboxes and a mock OAuth IdP for testing email and auth flows — 39 API-driven tools