getAccount — email MCP Tool
getAccount
(get account) 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 getAccount from your client
- Claude Code email getAccount run in your project directory
- Claude Desktop email getAccount ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor email getAccount ~/.cursor/mcp.json
- VS Code email getAccount .vscode/mcp.json
- Zed email getAccount ~/.config/zed/settings.json
- Windsurf email getAccount ~/.codeium/windsurf/mcp_config.json
- Cline email getAccount ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI email getAccount ~/.gemini/settings.json
- Grok email getAccount .mcp.json (in your project root)
- ChatGPT email getAccount Settings → Connectors → Advanced → Developer mode
- Claude.ai email getAccount Settings → Connectors → Add custom connector
- LangChain email getAccount 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
- getInboxStatus
- getOutboundStatus
- listEmails
- searchEmails
- getEmail
- replyToEmail
- 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.