InboxGuard agent auth — email deliverability MCP Resource

InboxGuard agent auth is one of 4 resources on the email deliverability MCP server. Connect the server and your client can attach it as context.

by client

How to attach InboxGuard agent auth from your client

• Claude Code email deliverability Resource/InboxGuard agent auth run in your project directory
• Claude Desktop email deliverability Resource/InboxGuard agent auth ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor email deliverability Resource/InboxGuard agent auth ~/.cursor/mcp.json
• VS Code email deliverability Resource/InboxGuard agent auth .vscode/mcp.json
• Zed email deliverability Resource/InboxGuard agent auth ~/.config/zed/settings.json
• Windsurf email deliverability Resource/InboxGuard agent auth ~/.codeium/windsurf/mcp_config.json
• Cline email deliverability Resource/InboxGuard agent auth ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI email deliverability Resource/InboxGuard agent auth ~/.gemini/settings.json
• Grok email deliverability Resource/InboxGuard agent auth .mcp.json (in your project root)
• ChatGPT email deliverability Resource/InboxGuard agent auth Settings → Connectors → Advanced → Developer mode
• Claude.ai email deliverability Resource/InboxGuard agent auth Settings → Connectors → Add custom connector
• LangChain email deliverability Resource/InboxGuard agent auth pip install langchain-mcp-adapters

Other resources on this server

• Scan result card
• InboxGuard full reference
• InboxGuard OpenAPI

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.