Autopilot status — MisarReach MCP Server MCP Resource

Autopilot status is one of 4 resources on the MisarReach MCP Server MCP server. Connect the server and your client can attach it as context.

by client

How to attach Autopilot status from your client

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

Other resources on this server

• Connected channels
• Lead lists
• Deal pipeline

MisarReach MCP Server also offers 5 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.