Connects Claude to Cantrip's GTM platform through 17 tools that manage go-to-market workflows for technical founders. You get commands to initialize projects, define ICPs and buyer pains, research competitors, and run gap analysis that generates concrete next actions. The server translates MCP calls into JSON envelopes POSTed to Cantrip's API, maintaining project context through a local .cantrip.json file. Includes a review workflow for accepting or rejecting AI-inferred entities like value props and contacts, plus generic CRUD operations across seven entity types. Requires a Cantrip API key and uses stdio transport via npx. Best for solo founders who want structured customer discovery and positioning research without leaving their editor.
Cantrip helps technical founders find their first customers with structured GTM workflows.
Works with Claude Code / Claude Desktop / Cursor — any MCP-compatible agent.
claude mcp add cantrip -e CANTRIP_API_KEY=your-api-key -- npx -y mcp-server-cantrip
"Initialize a Cantrip project for my product: [describe yours in one sentence]"
The Quick start command above covers Claude Code. Verify it worked with claude mcp list or the /mcp command inside a session.
All MCP clients use the same JSON block. Add it to the appropriate config file:
| Client | Config file |
|---|---|
| Claude Code (manual) | ~/.claude.json |
| Claude Code (project-scoped) | .mcp.json in project root |
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
| Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) |
{
"mcpServers": {
"cantrip": {
"command": "npx",
"args": ["-y", "mcp-server-cantrip"],
"env": {
"CANTRIP_API_KEY": "your-api-key"
}
}
}
}
Note: The
-yflag is required — without it,npxprompts 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.
.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.
After connecting Cantrip, try these prompts in order:
Server not found / no tools appear:
claude mcp list (Claude Code) or /mcp inside a session to check connection status.~/.claude.json or .mcp.json, not ~/.claude/mcp.json.Server hangs on startup:
-y in the npx args. Without it, npx waits for interactive confirmation that can never arrive over stdio."Cannot reach Cantrip API" errors:
CANTRIP_API_KEY is set in the env block of your MCP config.https://api.cantrip.ai is reachable from your network.Windows "Connection closed" errors:
"command": "cmd" with "args": ["/c", "npx", "-y", "mcp-server-cantrip"].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.
| Tool | Description |
|---|---|
cantrip_connect | Connect workspace to a project (reads/writes .cantrip.json) |
cantrip_status | Check if the daemon is running |
cantrip_init | Create a new project and auto-connect |
| Tool | Description |
|---|---|
cantrip_snapshot | Project overview, drill into entity types |
cantrip_next | List gap-analysis opportunities |
cantrip_next_prompt | Generate a context-rich LLM prompt for an opportunity |
cantrip_next_run | Spawn a background agent for an opportunity |
cantrip_history | Query the audit trail |
| Tool | Description |
|---|---|
cantrip_review | List items pending review |
cantrip_review_accept | Accept an inferred entity |
cantrip_review_reject | Reject an inferred entity |
cantrip_review_resolve | Resolve an escalation |
cantrip_review_dismiss | Dismiss an escalation |
| Tool | Description |
|---|---|
cantrip_entity_list | List entities of a type |
cantrip_entity_show | Show entity detail |
cantrip_entity_add | Create a new entity |
cantrip_entity_edit | Edit an existing entity |
Supported entity types: icp, pain_point, value_prop, experiment, channel, competitor, contact
MIT
CANTRIP_API_KEY*secretYour Cantrip API key
explorium-ai/vibeprospecting-mcp
io.github.compuute/lead-enrichment
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper
io.github.br0ski777/company-enrichment
com.mcparmory/apollo
mambalabsdev/mcp-gtm-tech-stack-signal-scraper