Cantrip MCP Server

mcp-server-cantrip

Cantrip helps technical founders find their first customers with structured GTM workflows.

• Nail your ICP — define ideal customer profiles, buyer pains, and value props
• Research competitors — map the landscape and find where you can win
• Get next actions — gap analysis tells you exactly what to work on, then does it for you

Works with Claude Code / Claude Desktop / Cursor — any MCP-compatible agent.

Quick start

1. Get your API key at cantrip.ai (settings)
2. Add the server:

claude mcp add cantrip -e CANTRIP_API_KEY=your-api-key -- npx -y mcp-server-cantrip

1. Try this prompt:

"Initialize a Cantrip project for my product: [describe yours in one sentence]"

Configuration

The Quick start command above covers Claude Code. Verify it worked with claude mcp list or the /mcp command inside a session.

Claude Desktop / Cursor / manual JSON

All MCP clients use the same JSON block. Add it to the appropriate config file:

{
  "mcpServers": {
    "cantrip": {
      "command": "npx",
      "args": ["-y", "mcp-server-cantrip"],
      "env": {
        "CANTRIP_API_KEY": "your-api-key"
      }
    }
  }
}

Note: The -y flag is required — without it, npx prompts for confirmation which hangs over stdio.

Windows (not WSL): Use "command": "cmd" with "args": ["/c", "npx", "-y", "mcp-server-cantrip"].

Project-scoped with teams: Use "${CANTRIP_API_KEY}" in the env value so each developer sets the key in their shell profile.

Project Context (.cantrip.json)

Each project directory contains a .cantrip.json file that tells Cantrip which project to target:

{
  "project": "my-saas"
}

This file is created automatically by cantrip_init (new project) or cantrip_connect (existing project). The agent manages it — you don't need to create it manually.

Multiple projects on the same machine? Each project directory gets its own .cantrip.json. The agent switches context by working in the right directory.

Examples of How to use Cantrip

After connecting Cantrip, try these prompts in order:

1. "Initialize a Cantrip project for my product: [one sentence about what you're building]"
2. "Find my likely ICP and top 3 buyer pains."
3. "Research 5 competitors and tell me where I can win."
4. "Give me a one-week GTM plan."

Troubleshooting

Server not found / no tools appear:

• Run claude mcp list (Claude Code) or /mcp inside a session to check connection status.
• Make sure the config is in the right file — Claude Code uses ~/.claude.json or .mcp.json, not ~/.claude/mcp.json.

Server hangs on startup:

• Ensure you have -y in the npx args. Without it, npx waits for interactive confirmation that can never arrive over stdio.

"Cannot reach Cantrip API" errors:

• Verify CANTRIP_API_KEY is set in the env block of your MCP config.
• Check that https://api.cantrip.ai is reachable from your network.

Windows "Connection closed" errors:

• Use "command": "cmd" with "args": ["/c", "npx", "-y", "mcp-server-cantrip"].

Architecture

Agent (Claude, etc.) ── MCP protocol (stdio) ──> mcp-server-cantrip ── HTTPS POST ──> https://api.cantrip.ai

The MCP server is a thin translation layer. It converts MCP tool calls into {command, args, flags} JSON envelopes and POSTs them to the Cantrip API. Zero business logic — identical contract to the CLI and React UI.

Tools (17)

Setup

Core Commands

Review

Entity CRUD (generic)

Supported entity types: icp, pain_point, value_prop, experiment, channel, competitor, contact

License

MIT