deleteEndpoint — email MCP Tool
deleteEndpoint
(delete endpoint) 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 deleteEndpoint from your client
- Claude Code email deleteEndpoint run in your project directory
- Claude Desktop email deleteEndpoint ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor email deleteEndpoint ~/.cursor/mcp.json
- VS Code email deleteEndpoint .vscode/mcp.json
- Zed email deleteEndpoint ~/.config/zed/settings.json
- Windsurf email deleteEndpoint ~/.codeium/windsurf/mcp_config.json
- Cline email deleteEndpoint ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI email deleteEndpoint ~/.gemini/settings.json
- Grok email deleteEndpoint .mcp.json (in your project root)
- ChatGPT email deleteEndpoint Settings → Connectors → Advanced → Developer mode
- Claude.ai email deleteEndpoint Settings → Connectors → Add custom connector
- LangChain email deleteEndpoint pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email https://www.primitive.dev/mcp
Other tools on this server
- listDomains
- addDomain
- verifyDomain
- downloadDomainZoneFile
- getAccount
- getInboxStatus
- getOutboundStatus
- listEmails
- searchEmails
- getEmail
- replyToEmail
- sendEmail
- sendEmailDemo
- listSentEmails
- getSentEmail
- cancelScheduledSend
- awaitReply
- getConversation
- getThread
- downloadEmailAttachments
- listEndpoints
- createEndpoint
- 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.