replyToEmail — email MCP Tool
replyToEmail
(reply to email) is one of 30 tools on the
email
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call replyToEmail from your client
- Claude Code email replyToEmail run in your project directory
- Claude Desktop email replyToEmail ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor email replyToEmail ~/.cursor/mcp.json
- VS Code email replyToEmail .vscode/mcp.json
- Zed email replyToEmail ~/.config/zed/settings.json
- Windsurf email replyToEmail ~/.codeium/windsurf/mcp_config.json
- Cline email replyToEmail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI email replyToEmail ~/.gemini/settings.json
- Grok email replyToEmail .mcp.json (in your project root)
- ChatGPT email replyToEmail Settings → Connectors → Advanced → Developer mode
- Claude.ai email replyToEmail Settings → Connectors → Add custom connector
- LangChain email replyToEmail pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email https://www.primitive.dev/mcpOther tools on this server
- listDomains
- addDomain
- verifyDomain
- downloadDomainZoneFile
- getAccount
- getInboxStatus
- getOutboundStatus
- listEmails
- searchEmails
- getEmail
- sendEmail
- sendEmailDemo
- listSentEmails
- getSentEmail
- cancelScheduledSend
- awaitReply
- getConversation
- getThread
- downloadEmailAttachments
- listEndpoints
- createEndpoint
- deleteEndpoint
- testEndpoint
- listFilters
- createFilter
- deleteFilter
- listWebhookDeliveries
- replayWebhookDelivery
- createEmailAddress
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.