audit-deliverability — MailX Email Deliverability MCP Prompt
audit-deliverability
is one of 2 prompts on the
MailX Email Deliverability
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke audit-deliverability from your client
- Claude Code MailX Email Deliverability Prompt/audit-deliverability run in your project directory
- Claude Desktop MailX Email Deliverability Prompt/audit-deliverability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MailX Email Deliverability Prompt/audit-deliverability ~/.cursor/mcp.json
- VS Code MailX Email Deliverability Prompt/audit-deliverability .vscode/mcp.json
- Zed MailX Email Deliverability Prompt/audit-deliverability ~/.config/zed/settings.json
- Windsurf MailX Email Deliverability Prompt/audit-deliverability ~/.codeium/windsurf/mcp_config.json
- Cline MailX Email Deliverability Prompt/audit-deliverability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MailX Email Deliverability Prompt/audit-deliverability ~/.gemini/settings.json
- Grok MailX Email Deliverability Prompt/audit-deliverability .mcp.json (in your project root)
- ChatGPT MailX Email Deliverability Prompt/audit-deliverability Settings → Connectors → Advanced → Developer mode
- Claude.ai MailX Email Deliverability Prompt/audit-deliverability Settings → Connectors → Add custom connector
- LangChain MailX Email Deliverability Prompt/audit-deliverability pip install langchain-mcp-adapters
Other prompts on this server
MailX Email Deliverability also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.