Parsley - Buyer Intent Signals

io.github.peterjduffyPublished by GitHub account peterjduffyv0.1.2Updated Oct 25, 2026

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

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Parsley MCP exposes buyer intent signals, MEDDIC qualification data and lead intelligence from a Parsley account to an AI assistant.

What you can do
Review account analytics: profile views, conversations, lead quality, top topics and conversion rate. List and read conversations with MEDDIC signals, evidence quotes, engagement and enrichment. Surface hot and warm leads and search conversations by intent signal, score or topic. Report knowledge gaps in unanswered chatbot questions and aggregate MEDDIC signal distribution. Run prompt templates for morning briefings, stale-lead checks, coaching gaps, content ideas and deal prep, optionally cross-referencing a connected CRM.
When to use it
Useful for sales and revenue teams that already run a Parsley chatbot and want to ask natural-language questions about lead intent, qualification gaps and follow-up priorities, especially alongside a CRM MCP server.
Requirements
A Parsley account with the chatbot enabled and an API key, supplied as the PARSLEY_API_KEY environment variable or the X-API-Key header. Runs as a remote endpoint or locally via the npm package with Node.js. Conversation tools and prompts require conversation balance.
Before you install
The API key is a live credential and should be kept out of shared configs. Conversation tools and prompts consume paid conversation balance after 10 free conversations, at 25 cents each. The optional client parameter lets an admin-equivalent key query managed client organizations' data.

Installation

In SourceWeft

  1. Open Parsley - Buyer Intent Signals in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.peterjduffy%2Fparsley-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "parsley-buyer-intent-signals": {
      "type": "http",
      "url": "https://www.parsley.id/api/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

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

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):

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

bash
git clone https://github.com/peterjduffy/parsley-mcp.gitcd parsley-mcpnpm installnpm run buildPARSLEY_API_KEY=pk_live_xxx node dist/index.js

License

MIT

Source: README.md at commit 026e8db

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Signals integrations