Error Tracking — AgentDeals MCP Resource
Error Tracking
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 Error Tracking from your client
- Claude Code AgentDeals Resource/Error Tracking run in your project directory
- Claude Desktop AgentDeals Resource/Error Tracking ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentDeals Resource/Error Tracking ~/.cursor/mcp.json
- VS Code AgentDeals Resource/Error Tracking .vscode/mcp.json
- Zed AgentDeals Resource/Error Tracking ~/.config/zed/settings.json
- Windsurf AgentDeals Resource/Error Tracking ~/.codeium/windsurf/mcp_config.json
- Cline AgentDeals Resource/Error Tracking ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentDeals Resource/Error Tracking ~/.gemini/settings.json
- Grok AgentDeals Resource/Error Tracking .mcp.json (in your project root)
- ChatGPT AgentDeals Resource/Error Tracking Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentDeals Resource/Error Tracking Settings → Connectors → Add custom connector
- LangChain AgentDeals Resource/Error Tracking 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
- Consumer Email
- Container Registry
- Databases
- Design
- Design & Creative
- Dev Utilities
- Diagramming
- DNS & Domain Management
- Documentation
- Education
- 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.