How to Use the Customer Discovery Prover MCP in Cursor

Q: Can Customer Discovery Prover stop my Cursor agent from writing unvalidated features?

Yes, by calling validatecustomerdiscovery in Agent mode, the editor checks your local discovery files to ensure the feature solves a documented, verified pain point.

Write code for real problems. Force Cursor to validate your customer discovery evidence with this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Customer Discovery Prover MCP to Cursor

Create your Vinkius account to connect Customer Discovery Prover to Cursor — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Customer Discovery Prover with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Validate Market Pain Points While Writing Code in Cursor

The `validate_customer_discovery` tool connects directly to your Cursor workspace, allowing your coding agent to check if a feature request matches documented user pain before you build it. It reads your local markdown files to ensure you are not writing speculative code. By analyzing your local interview files, this MCP Server keeps your development focused on real problems. It ensures you only write code that addresses verified workflow bottlenecks instead of speculative ideas.

Enforce The Mom Test in Your Cursor Agent Workflows

The `validate_customer_discovery` tool scans your project's discovery data inside Cursor to find hard evidence of user commitment before you build out a new system. It ensures your code editor is aligned with actual willingness-to-pay rather than verbal promises. If your agent tries to generate code based on a customer saying they "would pay" for a feature, the tool flags it. It demands proof of real commitment, such as signed letters of intent or pilot dates, saving you weeks of wasted engineering hours.

Keep Your Target Segments Clean in Your Dev Environment

This MCP Server uses the `validate_customer_discovery` tool to help you isolate specific buyer groups inside Cursor, ensuring your feature implementation aligns with the correct target audience. It prevents you from writing complex enterprise code for early-stage startup targets. When you run this validation, your agent checks if your current coding task matches the specific pain points of your target segment. It stops you from building features for groups who have entirely different budgets and buying processes.

Setup guide

Set up Customer Discovery Prover MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Customer Discovery Prover MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Customer Discovery Prover transactions." If the MCP tools are loaded correctly, Cursor will call the Customer Discovery Prover tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "customer-discovery-prover-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Customer Discovery Prover. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Customer Discovery Prover now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Customer Discovery Prover MCP in Cursor

You just add the server configuration to your project's local MCP configuration file. Once configured, your Cursor agent can run validation checks directly on your interview markdown files.

Yes, by calling `validate_customer_discovery` in Agent mode, the editor checks your local discovery files to ensure the feature solves a documented, verified pain point.

The tool analyzes your customer interview logs for actual commitment signals like deposits or scheduled pilots. It flags simple verbal interest as insufficient, keeping your roadmap grounded in reality.

Plain text or markdown files with raw interview notes work best. The tool parses these files to extract names, roles, specific quotes, and actual behaviors.

Your customer interview logs stay completely within your local workspace or secure sandbox. The server processes the data ephemerally, ensuring no sensitive customer details are stored or leaked.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript