planned_vs_executed — insidergraph MCP Tool
planned_vs_executed
(planned vs executed) is one of 11 tools on the
insidergraph
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call planned_vs_executed from your client
- Claude Code insidergraph planned_vs_executed run in your project directory
- Claude Desktop insidergraph planned_vs_executed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor insidergraph planned_vs_executed ~/.cursor/mcp.json
- VS Code insidergraph planned_vs_executed .vscode/mcp.json
- Zed insidergraph planned_vs_executed ~/.config/zed/settings.json
- Windsurf insidergraph planned_vs_executed ~/.codeium/windsurf/mcp_config.json
- Cline insidergraph planned_vs_executed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI insidergraph planned_vs_executed ~/.gemini/settings.json
- Grok insidergraph planned_vs_executed .mcp.json (in your project root)
- ChatGPT insidergraph planned_vs_executed Settings → Connectors → Advanced → Developer mode
- Claude.ai insidergraph planned_vs_executed Settings → Connectors → Add custom connector
- LangChain insidergraph planned_vs_executed pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http insidergraph https://api.insidergraph.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.