Pipedrive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIPEDRIVE_API_KEY | Yes | Your Pipedrive API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dealsC | Get all deals with optional filters |
| get_deal_detailsB | Get detailed information about a specific deal, including person and organization info |
| get_activitiesC | Get activities with optional filters |
| get_leadsC | Get leads with optional filters |
| get_pipelinesC | Get all pipelines |
| get_stagesC | Get all stages for a pipeline |
| get_usersB | Get all users in the company |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct Pipedrive entity (pipelines, stages, users, deals, activities, leads). The only mild overlap is get_deals versus get_deal_details, but the descriptions clearly differentiate a filtered list from a detailed single-deal lookup.
All tools follow a consistent get_<noun> snake_case pattern, which is predictable and readable. Minor deviation: get_deals is plural while get_deal_details is singular, but the convention is still clear.
Seven tools is well-scoped and each earns its place for a read-oriented Pipedrive surface. It is slightly lean, with no redundancy or bloat.
The surface is entirely read-only, with no create, update, or delete operations for deals, activities, or leads, which are core CRM workflows. Agents can retrieve data but cannot act on it, creating significant dead ends.