email-deliverability-skill — MailX Email Deliverability MCP Resource
email-deliverability-skill
is one of 2 resources on the
MailX Email Deliverability
MCP server. Connect the server and your client can attach it as context.
by client
How to attach email-deliverability-skill from your client
- Claude Code MailX Email Deliverability Resource/email-deliverability-skill run in your project directory
- Claude Desktop MailX Email Deliverability Resource/email-deliverability-skill ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MailX Email Deliverability Resource/email-deliverability-skill ~/.cursor/mcp.json
- VS Code MailX Email Deliverability Resource/email-deliverability-skill .vscode/mcp.json
- Zed MailX Email Deliverability Resource/email-deliverability-skill ~/.config/zed/settings.json
- Windsurf MailX Email Deliverability Resource/email-deliverability-skill ~/.codeium/windsurf/mcp_config.json
- Cline MailX Email Deliverability Resource/email-deliverability-skill ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MailX Email Deliverability Resource/email-deliverability-skill ~/.gemini/settings.json
- Grok MailX Email Deliverability Resource/email-deliverability-skill .mcp.json (in your project root)
- ChatGPT MailX Email Deliverability Resource/email-deliverability-skill Settings → Connectors → Advanced → Developer mode
- Claude.ai MailX Email Deliverability Resource/email-deliverability-skill Settings → Connectors → Add custom connector
- LangChain MailX Email Deliverability Resource/email-deliverability-skill pip install langchain-mcp-adapters
Other resources on this server
MailX Email Deliverability also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.