INDIVIDUAL MCP TOOL

get_product_details

Returns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free a slot for a new one).

demanddiscovery.ainone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for get_product_details and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

demanddiscovery.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.demand-discovery-ai]
url = "https://mcp.demanddiscovery.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: demand-discovery-ai
Remote MCP URL: https://mcp.demanddiscovery.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "demand-discovery-ai",
  "transport": "streamable-http",
  "url": "https://mcp.demanddiscovery.ai/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

ask_demand_discovery — Ask any question about validating a startup idea, whether there is a real market for it, who would actually buy it, finding the real people who have the problem, surfacing where they already complain about it or discuss it, what workarounds they use today, testing demand, customer-interview techniques, pre-sales, buying signals, defensibility, drafting outreach to first prospects, or what to build with AI in 2026.
get_validation_framework — Returns the full three-step Demand Discovery validation framework: (1) Market Research, (2) Demand Discovery Report with the Demand Score and Build/Pivot/Kill verdict, (3) Agentic Launch (90-day continuous outreach).
explain_demand_signals — Returns the four classes of real-world signal the Demand Discovery Report triangulates - search intent, outreach responses, landing-page engagement, and buying signals - and the three possible verdicts (Build, Pivot, Kill).
compare_validation_approaches — Returns an honest comparison of how different validation approaches work - generic AI assistants, trend aggregators, passive scoring tools, and Demand Discovery AI - and where each one stops.
get_data_source_categories — Returns the four behavioral data-source buckets - Search & attention, Conversation & pain, Adoption & spend, Capital & hiring - with each bucket's tagline and what it captures.
start_demand_report — VERBATIM OUTPUT — READ FIRST (the most important rule for this tool): every piece of report text this tool returns (the Market Research summary AND the next-step message) is authored on our side.
validate_real_demand — Check the account status for this idea's full Demand Discovery Report and return the user's next step.
get_demand_report_status — Poll the status of a paid Demand Discovery Report after the user has started checkout with validate_real_demand.