doc:/operate/troubleshooting — Amomic-AI Docs MCP Resource
doc:/operate/troubleshooting
is one of 99 resources on the
Amomic-AI Docs
MCP server. Connect the server and your client can attach it as context.
by client
How to attach doc:/operate/troubleshooting from your client
- Claude Code Amomic-AI Docs Resource/doc:/operate/troubleshooting run in your project directory
- Claude Desktop Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/.cursor/mcp.json
- VS Code Amomic-AI Docs Resource/doc:/operate/troubleshooting .vscode/mcp.json
- Zed Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/.config/zed/settings.json
- Windsurf Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/.codeium/windsurf/mcp_config.json
- Cline Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Amomic-AI Docs Resource/doc:/operate/troubleshooting ~/.gemini/settings.json
- Grok Amomic-AI Docs Resource/doc:/operate/troubleshooting .mcp.json (in your project root)
- ChatGPT Amomic-AI Docs Resource/doc:/operate/troubleshooting Settings → Connectors → Advanced → Developer mode
- Claude.ai Amomic-AI Docs Resource/doc:/operate/troubleshooting Settings → Connectors → Add custom connector
- LangChain Amomic-AI Docs Resource/doc:/operate/troubleshooting pip install langchain-mcp-adapters
Other resources on this server
- documentation-index
- doc:/agents-setup
- doc:/api/apps-duesly
- doc:/api/authentication
- doc:/api/call-outcomes
- doc:/api/calls
- doc:/api/campaigns
- doc:/api/contacts
- doc:/api/conversations
- doc:/api/discovery
- doc:/api/errors
- doc:/api/idempotency
- doc:/api/messages
- doc:/api/overview
- doc:/api/pagination
- doc:/api/rate-limits
- doc:/api/scopes
- doc:/api/tickets
- doc:/apps/duesly
- doc:/apps/overview
- doc:/build/agents
- doc:/build/deployments
- doc:/build/knowledge
- doc:/build/knowledge-retrieval
- doc:/build/testing
- doc:/build/tools
- doc:/build/versions
- doc:/campaigns/audiences
- doc:/campaigns/call-scripts
- doc:/campaigns/create
- doc:/campaigns/failure-reasons
- doc:/campaigns/outcomes
- doc:/campaigns/overview
- doc:/campaigns/results
- doc:/campaigns/scheduling
- doc:/campaigns/sending-rules
- doc:/campaigns/troubleshooting
- doc:/channels/email
- doc:/channels/outbound-calls
- doc:/channels/overview
Read from the server itself, by connecting to it and calling resources/list on 11 November 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.