Consumer Email — AgentDeals MCP Resource
Consumer Email
is one of 500 resources on the
AgentDeals
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Consumer Email from your client
- Claude Code AgentDeals Resource/Consumer Email run in your project directory
- Claude Desktop AgentDeals Resource/Consumer Email ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentDeals Resource/Consumer Email ~/.cursor/mcp.json
- VS Code AgentDeals Resource/Consumer Email .vscode/mcp.json
- Zed AgentDeals Resource/Consumer Email ~/.config/zed/settings.json
- Windsurf AgentDeals Resource/Consumer Email ~/.codeium/windsurf/mcp_config.json
- Cline AgentDeals Resource/Consumer Email ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentDeals Resource/Consumer Email ~/.gemini/settings.json
- Grok AgentDeals Resource/Consumer Email .mcp.json (in your project root)
- ChatGPT AgentDeals Resource/Consumer Email Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentDeals Resource/Consumer Email Settings → Connectors → Add custom connector
- LangChain AgentDeals Resource/Consumer Email pip install langchain-mcp-adapters
Other resources on this server
- categories
- vendors
- changes
- changes-latest
- guides
- Search Deals View
- Plan Stack View
- Compare Vendors View
- Track Changes View
- AI / ML
- AI Coding
- Analytics
- API Development
- API Gateway
- Auth
- Background Jobs
- Browser Automation
- CDN
- CI/CD
- Cloud Hosting
- Cloud IaaS
- Cloud Storage
- Code Quality
- Communication
- Communication & Messaging
- Container Registry
- Databases
- Design
- Design & Creative
- Dev Utilities
- Diagramming
- DNS & Domain Management
- Documentation
- Education
- Error Tracking
- Feature Flags
- Forms
- Headless CMS
- IDE & Code Editors
AgentDeals also offers 6 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.