English Français العربية

Parsley - Buyer Intent Signals

Official registry Archived Marketing and sales

Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.

Source code Documentation

What can you do with Parsley - Buyer Intent Signals?

  • "Which leads went hot this week?"
  • "Show me the MEDDIC gaps for recent conversations"
  • "Any high-intent visitors that nobody's followed up on?"
  • "What are people asking that my chatbot can't answer?"

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http parsley-buyer-intent-signals 'https://www.parsley.id/api/mcp' --header 'X-API-Key: <Your Parsley API key (starts with pk_live_). Generate one at parsley.id/hub/api-keys>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "parsley-buyer-intent-signals": {
            "type": "http",
            "url": "https://www.parsley.id/api/mcp",
            "headers": {
                "X-API-Key": "<Your Parsley API key (starts with pk_live_). Generate one at parsley.id/hub/api-keys>"
            }
        }
    }
}
NPM package @tryparsley/mcp-server
Claude Code 
claude mcp add parsley-buyer-intent-signals -e 'PARSLEY_API_KEY=<your parsley_api_key>' -- npx -y @tryparsley/mcp-server@0.1.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "parsley-buyer-intent-signals": {
            "command": "npx",
            "args": [
                "-y",
                "@tryparsley/mcp-server@0.1.2"
            ],
            "env": {
                "PARSLEY_API_KEY": "<your parsley_api_key>"
            }
        }
    }
}

Environment variables

  • PARSLEY_API_KEY required secret Your Parsley API key (starts with pk_live_). Generate one at parsley.id/hub/api-keys

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Parsley MCP Server
  2. What it does
  3. Setup
  4. Tools (8)
  5. Prompts (5)
  6. Access
  7. Agencies
  8. Development
  9. License

Parsley MCP Server

A Model Context Protocol server that exposes buyer intent signals, MEDDIC qualification data, and lead intelligence from your Parsley account to AI assistants like Claude Desktop and Cursor.

What it does

Ask your AI assistant natural questions about your leads:

  • "Which leads went hot this week?"
  • "Show me the MEDDIC gaps for recent conversations"
  • "Any high-intent visitors that nobody's followed up on?"
  • "What are people asking that my chatbot can't answer?"

If you also have a CRM MCP connected (Attio, HubSpot, Salesforce, etc.), Claude can cross-reference automatically - finding hot leads with no CRM follow-up, prepping you for calls with full context from both systems.

Setup

1. Get your API key

Generate an API key at parsley.id/hub/api-keys. You need a Parsley account with the chatbot enabled.

2. Configure Claude Desktop

Add to your Claude Desktop config file:

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

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

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "parsley": {
      "command": "npx",
      "args": ["-y", "@tryparsley/mcp-server"],
      "env": {
        "PARSLEY_API_KEY": "pk_live_your_key_here"
      }
    }
  }
}
Environment variables
VariableRequiredDescription
PARSLEY_API_KEYYesYour Parsley API key (pk_live_...)
PARSLEY_BASE_URLNoAPI base URL (defaults to https://www.parsley.id)

Tools (8)

Every account
ToolDescription
get_analytics_summaryDashboard overview - profile views, conversations, lead quality breakdown, top topics, conversion rate
With conversation balance
ToolDescription
get_conversationsList recent conversations with filtering by lead quality, intent signal, date range
get_conversation_detailFull conversation detail - MEDDIC signals with evidence quotes, engagement, enrichment, discovery field values
get_hot_leadsHot and warm leads with MEDDIC evidence - the morning briefing tool
search_by_intentFind conversations by MEDDIC signals, intent score, or topic
get_knowledge_gapsUnanswered chatbot questions grouped by topic and frequency
get_lead_enrichmentExtracted company, role, timeline, and budget context from conversations
get_meddic_summaryAggregate MEDDIC signal distribution - per-signal counts, top combinations

Prompts (5)

Predefined workflow templates that appear in Claude's prompt picker.

PromptCross-MCPDescription
morning_briefingYesHot leads summary with follow-up priorities. Cross-references CRM if connected.
stale_leads_checkYesQualified leads with no recent CRM activity. Requires a CRM MCP.
coaching_gapsNoMEDDIC gaps with suggested follow-up questions for each lead.
content_opportunitiesNoKnowledge gaps turned into blog post, chatbot doc, and FAQ suggestions.
deal_prepOptionalPre-call briefing on a company/person. Pulls CRM context if available.
Cross-MCP workflows

Prompts marked "Cross-MCP" work with any CRM that has an MCP server. Connect both Parsley and your CRM's MCP to Claude, and the prompts will orchestrate across both automatically. No extra configuration needed.

Tested with: Attio, HubSpot, Salesforce, Copper, Pipedrive.

Access

  • get_analytics_summary runs on every account
  • The other 7 tools and all 5 prompts require conversation balance - every new account gets 10 free conversations, then it is 25¢ each

See parsley.id/pricing.

Agencies

Every tool accepts an optional client parameter: pass a managed client's org id to query that client's data instead of your own. The API key owner must hold an admin-equivalent membership in the client org - validated server-side, so a key can never reach data its owner couldn't see in the dashboard.

Development

git clone https://github.com/peterjduffy/parsley-mcp.git
cd parsley-mcp
npm install
npm run build
PARSLEY_API_KEY=pk_live_xxx node dist/index.js

License

MIT

Frequently asked questions

What is Parsley - Buyer Intent Signals?

Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.

How do I install Parsley - Buyer Intent Signals?

It runs as a remote server. In Claude Code: claude mcp add --transport http parsley-buyer-intent-signals 'https://www.parsley.id/api/mcp' --header 'X-API-Key: <Your Parsley API key (starts with pk_live_). Generate one at parsley.id/hub/api-keys>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Parsley - Buyer Intent Signals need an API key?

Yes. It expects PARSLEY_API_KEY, X-API-Key, which you set in its configuration.

Is Parsley - Buyer Intent Signals open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Parsley - Buyer Intent Signals?

It is published by peterjduffy. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.