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