Pipedrive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for SSE transport (default: 3000, only used when MCP_TRANSPORT=sse) | 3000 |
| MCP_ENDPOINT | No | Message endpoint path for SSE (default: /message, only used when MCP_TRANSPORT=sse) | /message |
| MCP_JWT_TOKEN | No | JWT token for authentication (optional) | |
| MCP_TRANSPORT | No | Transport type: stdio (default, for local use) or sse (for Docker/HTTP access) | stdio |
| MCP_JWT_ISSUER | No | JWT issuer (optional) | |
| MCP_JWT_SECRET | No | JWT secret for authentication (optional) | |
| MCP_JWT_AUDIENCE | No | JWT audience (optional) | |
| PIPEDRIVE_DOMAIN | Yes | Your Pipedrive domain (e.g., your-company.pipedrive.com) | |
| MCP_JWT_ALGORITHM | No | JWT algorithm (default: HS256) | HS256 |
| PIPEDRIVE_API_TOKEN | Yes | Your Pipedrive API token | |
| PIPEDRIVE_RATE_LIMIT_MIN_TIME_MS | No | Minimum time between requests in milliseconds (default: 250) | 250 |
| PIPEDRIVE_RATE_LIMIT_MAX_CONCURRENT | No | Maximum concurrent requests (default: 2) | 2 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues