MCP Server Setup - Docs

Connect Parsley to Claude Desktop, Cursor, or any MCP-compatible AI assistant. Query your buyer intent signals, MEDDIC data, and lead scores through conversation.

Connect Parsley to your AI assistant via the Model Context Protocol (MCP). Ask about hot leads, MEDDIC signals, knowledge gaps, and lead scores using natural language - no dashboards required.

Quick Setup

Generate an API key in Hub > API Keys
Add the config snippet to your Claude Desktop or Cursor config file
Set your API key as an environment variable
Restart your AI assistant
Start asking about your leads

Setup takes under 2 minutes.

Prerequisites

A Parsley account with the chatbot enabled and at least one conversation
An API key from Hub > API Keys
Claude Desktop or Cursor (or any MCP-compatible client)
Node.js 18+ installed (for the npx command)

Free plan users get the get_analytics_summary tool. Business plan users get all 8 tools and 5 workflow prompts.

Step 1: Generate an API Key

From your Parsley dashboard:

Go to Hub in the left sidebar
Click API Keys
Click Create API Key
Name it MCP (or any name that helps you identify its purpose)
Copy the key immediately - it is only shown once

Store your API key securely. If you lose it, revoke it and create a new one.

Step 2: Configure Claude Desktop

Open your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the Parsley MCP server to the mcpServers object:

{
  "mcpServers": {
    "parsley": {
      "command": "npx",
      "args": ["-y", "@parsley/mcp-server"],
      "env": {
        "PARSLEY_API_KEY": "pk_live_your_key_here"
      }
    }
  }
}

Replace pk_live_your_key_here with your actual API key from Step 1.

If you already have other MCP servers configured, add the "parsley" entry alongside them inside the existing mcpServers object.

Step 2 (Alternative): Configure Cursor

Add to your Cursor MCP settings file (.cursor/mcp.json in your project root):

{
  "mcpServers": {
    "parsley": {
      "command": "npx",
      "args": ["-y", "@parsley/mcp-server"],
      "env": {
        "PARSLEY_API_KEY": "pk_live_your_key_here"
      }
    }
  }
}

Step 3: Restart and Test

Restart Claude Desktop (or Cursor) completely. Then try asking:

"Which leads went hot this week?"
"Show me my analytics summary"
"What are visitors asking that my chatbot can't answer?"

If everything is configured correctly, Claude will call the Parsley MCP tools and return your data.

Available Tools

Free Plan

Tool	Description
`get_analytics_summary`	Dashboard overview - views, conversations, lead counts, conversion rate

Business Plan

Tool	Description
`get_hot_leads`	Hot and warm leads with MEDDIC evidence
`get_conversations`	List conversations filtered by quality, intent, or date
`get_conversation_detail`	Full conversation with visitor info, MEDDIC signals, topics
`search_by_intent`	Find conversations by MEDDIC signals, intent score, or topic
`get_knowledge_gaps`	Unanswered questions by topic
`get_lead_enrichment`	Extracted company, role, timeline, and budget context
`get_meddic_summary`	Aggregate MEDDIC signal distribution across conversations

All tools accept a days parameter to control the lookback period (default varies by tool).

Workflow Prompts

Business plan users also get 5 pre-built workflow prompts that appear in Claude's prompt picker:

Prompt	What it does	Cross-MCP
Morning Briefing	Hot leads, intent signals, follow-up priorities	Yes
Stale Leads Check	Hot leads with no CRM follow-up	Yes (requires CRM MCP)
Coaching Gaps	Leads with missing MEDDIC signals + suggested questions	No
Content Opportunities	Unanswered questions grouped by topic with content suggestions	No
Deal Prep	Full brief before a call - what they asked, signals, objections	Optional

Cross-MCP with Your CRM

If you also connect your CRM's MCP server to Claude (Attio, HubSpot, Salesforce, Copper, Pipedrive, etc.), the AI cross-references both data sources automatically.

Example queries that work with both MCPs connected:

"Find hot Parsley leads that don't have a next activity in my CRM"
"Prep me for my call with Sarah at Acme - what did she ask about, and what's in the CRM?"
"Which leads went warm this week but haven't been contacted yet?"

No extra configuration needed. Connect both MCPs and Claude does the rest.

Troubleshooting

"Server not found" or tools not appearing

Make sure Node.js 18+ is installed: run node --version in your terminal
Check your config file is valid JSON (no trailing commas, correct brackets)
Restart Claude Desktop completely (quit and reopen, not just close the window)
Check Claude Desktop's MCP server logs for errors

"Authentication failed" or "Invalid API key"

Verify your API key starts with pk_live_
Make sure you copied the full key without extra spaces
Check the key hasn't been revoked in Hub > API Keys
Generate a new key if unsure

"Tier restriction" errors on certain tools

Free plan users only have access to get_analytics_summary
Upgrade to Business for all 8 tools and 5 prompts

No conversation data returned

Make sure your chatbot has had at least one conversation
Check the days parameter - the default lookback varies by tool
Verify the API key belongs to the correct Parsley account

Security

The MCP server runs locally on your machine as a subprocess of Claude Desktop
Your API key is passed as a local environment variable - never sent to a third party
All communication is between your machine and Parsley's API over HTTPS
The server is read-only - no write operations, no modifications to your data
You can revoke your API key anytime from Hub > API Keys

Uninstalling

To remove the Parsley MCP server:

Delete the "parsley" entry from your Claude Desktop config file
Restart Claude Desktop
Optionally, revoke the API key in Hub > API Keys