# Parsley - Buyer Intent Signals

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/peterjduffy/parsley-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 171  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/parsley-buyer-intent-signals

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

## Tools
Capabilities this server exposes over MCP:

- **get_analytics_summary** — Dashboard overview - profile views, conversations, lead quality breakdown, top topics, conversion rate
- **get_conversations** — List recent conversations with filtering by lead quality, intent signal, date range
- **get_conversation_detail** — Full conversation detail - MEDDIC signals with evidence quotes, engagement, enrichment, discovery field values
- **get_hot_leads** — Hot and warm leads with MEDDIC evidence - the morning briefing tool
- **search_by_intent** — Find conversations by MEDDIC signals, intent score, or topic
- **get_knowledge_gaps** — Unanswered chatbot questions grouped by topic and frequency
- **get_lead_enrichment** — Extracted company, role, timeline, and budget context from conversations
- **get_meddic_summary** — Aggregate MEDDIC signal distribution - per-signal counts, top combinations

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "parsley-buyer-intent-signals": {
    "command": "npx",
    "args": ["-y","@tryparsley/mcp-server"],
    "env": {
      "PARSLEY_API_KEY": "",
      "PARSLEY_BASE_URL": ""
    }
  }
}
```

**Requires environment variables:** `PARSLEY_API_KEY`, `PARSLEY_BASE_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Parsley - Buyer Intent Signals does

Parsley - Buyer Intent Signals MCP server connects an MCP-compatible assistant to data in a Parsley account. It provides access to buyer intent signals, MEDDIC qualification information, lead scores, conversation records, extracted lead context, and chatbot knowledge gaps.

The server includes eight tools. Analytics provides account-level figures such as profile views, conversation volume, lead-quality distribution, popular topics, and conversion rate. Conversation tools list records with filters, retrieve detailed records with evidence quotes and engagement data, and identify hot or warm leads. Other tools search by MEDDIC signal, intent score, or topic; group unanswered questions; return company, role, timeline, and budget context; and summarize MEDDIC signal counts and combinations.

Five predefined prompts support recurring workflows. These include a morning briefing, stale-lead review, coaching-gap analysis, content-opportunity discovery, and deal preparation. Some prompts can use a separately connected CRM MCP to compare Parsley activity with CRM activity.

## How it works

The server runs as a standard MCP process and authenticates requests with a Parsley API key. An assistant can then call the available tools using natural-language requests about leads, conversations, qualification signals, or chatbot questions.

One analytics tool is available on every account. The remaining seven tools and all five prompts require conversation balance.

Cross-MCP prompts can work with CRM MCP servers for Attio, HubSpot, Salesforce, Copper, and Pipedrive. For example, a connected CRM can provide context when checking for qualified leads without recent CRM activity or preparing for a call. Each tool also accepts an optional client organization identifier for agency use; server-side membership checks limit access to data the API-key owner is authorized to view.

## Setup and configuration

Create a Parsley API key at the Parsley API-key page and use an account with the chatbot enabled. The documented installation runs the published package through `npx` with `@tryparsley/mcp-server`.

Set `PARSLEY_API_KEY` to the account key. `PARSLEY_BASE_URL` is optional and defaults to `https://www.parsley.id`; it can be used when a different API base URL is required. Claude Desktop and Cursor examples in the README use a stdio configuration with the package command and these environment variables.

For local development, clone the repository, install npm dependencies, build the project, and start `dist/index.js` with `PARSLEY_API_KEY` set.

## Tools and capabilities

Parsley - Buyer Intent Signals supports these tool categories:

- Account analytics and conversion reporting
- Conversation listing, filtering, and detailed inspection
- Hot and warm lead identification with MEDDIC evidence
- Intent, topic, and MEDDIC-signal searches
- Unanswered-question analysis by topic and frequency
- Lead enrichment for company, role, timeline, and budget
- Aggregate MEDDIC signal reporting

The prompts add reusable briefing, qualification, coaching, content, and deal-preparation workflows. The `stale_leads_check` prompt requires a CRM MCP, while `morning_briefing` and other cross-MCP workflows can use CRM context when available.

## Limitations and notes

Conversation-dependent tools and prompts are not available without conversation balance. CRM comparisons also require a separately configured CRM MCP. API-key access remains subject to the owner’s Parsley permissions and client-organization membership.

_Full upstream README: https://allmcps.com/mcp/parsley-buyer-intent-signals/readme_