plan_next_data_ask — discovery MCP Tool
plan_next_data_ask
(plan next data ask) is one of 17 tools on the
discovery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_next_data_ask from your client
- Claude Code discovery plan_next_data_ask run in your project directory
- Claude Desktop discovery plan_next_data_ask ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor discovery plan_next_data_ask ~/.cursor/mcp.json
- VS Code discovery plan_next_data_ask .vscode/mcp.json
- Zed discovery plan_next_data_ask ~/.config/zed/settings.json
- Windsurf discovery plan_next_data_ask ~/.codeium/windsurf/mcp_config.json
- Cline discovery plan_next_data_ask ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI discovery plan_next_data_ask ~/.gemini/settings.json
- Grok discovery plan_next_data_ask .mcp.json (in your project root)
- ChatGPT discovery plan_next_data_ask Settings → Connectors → Advanced → Developer mode
- Claude.ai discovery plan_next_data_ask Settings → Connectors → Add custom connector
- LangChain discovery plan_next_data_ask pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http discovery https://peopleanalyst.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.