Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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.
Ask your AI assistant natural questions about your leads:
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.
Generate an API key at parsley.id/hub/api-keys. You need a Parsley account with the chatbot enabled.
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Add to your Cursor MCP settings (.cursor/mcp.json):
| Variable | Required | Description |
|---|---|---|
PARSLEY_API_KEY | Yes | Your Parsley API key (pk_live_...) |
PARSLEY_BASE_URL | No | API base URL (defaults to https://www.parsley.id) |
| Tool | Description |
|---|---|
get_analytics_summary | Dashboard overview - profile views, conversations, lead quality breakdown, top topics, conversion rate |
| Tool | Description |
|---|---|
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 |
Predefined workflow templates that appear in Claude's prompt picker.
| Prompt | Cross-MCP | Description |
|---|---|---|
morning_briefing | Yes | Hot leads summary with follow-up priorities. Cross-references CRM if connected. |
stale_leads_check | Yes | Qualified leads with no recent CRM activity. Requires a CRM MCP. |
coaching_gaps | No | MEDDIC gaps with suggested follow-up questions for each lead. |
content_opportunities | No | Knowledge gaps turned into blog post, chatbot doc, and FAQ suggestions. |
deal_prep | Optional | Pre-call briefing on a company/person. Pulls CRM context if available. |
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.
get_analytics_summary runs on every accountSee parsley.id/pricing.
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.
MIT
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/parsley-buyer-intent-signals)<a href="https://allmcps.com/mcp/parsley-buyer-intent-signals"><img src="https://allmcps.com/api/badge/parsley-buyer-intent-signals?style=directory" alt="Parsley Buyer Intent Signals on AllMCPs" /></a>