Demand Discovery AI MCP MCP server

This MCP server enables AI agents to validate startup ideas by connecting with real people who are actively seeking solutions. It allows agents to gather qualitative feedback and quotes linked to their sources, helping founders move beyond opinion-based assumptions to behavior-driven validation.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Demand Discovery AI

MCP endpoint (Streamable HTTP)

https://mcp.demanddiscovery.ai/api/mcp

Vendor documentation

What you can do with it

Validate startup ideas with real user feedback
Gather quotes linked to specific sources
Analyze user behavior over opinions

Tools advertised by the last live check:

ask_demand_discovery
get_validation_framework
get_product_details
explain_demand_signals
compare_validation_approaches
get_data_source_categories
start_demand_report
validate_real_demand
get_demand_report_status
start_agentic_launch

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http demand-discovery-ai-mcp https://mcp.demanddiscovery.ai/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add demand-discovery-ai-mcp --url https://mcp.demanddiscovery.ai/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable demand-discovery-ai-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "demand-discovery-ai-mcp": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "demand-discovery-ai-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.demanddiscovery.ai/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start demand-discovery-ai-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "demand-discovery-ai-mcp": {
      "type": "http",
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http demand-discovery-ai-mcp https://mcp.demanddiscovery.ai/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "demand-discovery-ai-mcp": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "demand-discovery-ai-mcp": {
      "serverUrl": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}

See all 1,583

Do you run Demand Discovery AI MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing