An MCP server that exposes Parsley buyer intent signals, MEDDIC qualification data, lead intelligence, and chatbot knowledge gaps to AI assistants. It can also work with a connected CRM MCP to cross-reference leads and surface follow-up priorities.
From the registry: Query buyer intent signals, MEDDIC qualifications, and lead scores from Parsley.
Please install the `parsley-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js and npm** — Node.js is required to run the server via npx.
- **Create a Parsley API key** — Generate an API key from the Parsley dashboard. A Parsley account with the chatbot enabled is required. (https://www.parsley.id/hub/api-keys)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@tryparsley/mcp-server"]
- required environment variables:
- `PARSLEY_API_KEY`: Your Parsley API key. (example: `<your-parsley-api-key>`)
- optional environment variables:
- `PARSLEY_BASE_URL`: Optional API base URL override. (example: `<your-parsley-base-url>`)
Note: Preferred install path is the published npx package. The README also shows a local development run path, but that is not the recommended end-user configuration.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.PARSLEY_API_KEYrequiredYour Parsley API key used to authenticate requestsPARSLEY_BASE_URLOptional API base URL, defaults to https://www.parsley.idMCP server for Omie — ERP, customers, products, orders, invoices, financials