pipedrive-mcp
by mmedum
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: `debug` / `info` / `warn` / `error`. | info |
| LOG_FORMAT | No | Log format: `text` / `json`. | text |
| PIPEDRIVE_DRY_RUN | No | Server-wide dry-run floor: every write becomes a rehearsal. A per-call `dry_run` can only turn one on, never off. | false |
| PIPEDRIVE_API_TOKEN | No | CI/automation fallback. Prefer `pipedrive-mcp login` for interactive use. | |
| PIPEDRIVE_HTTP_TIMEOUT | No | Per-request outbound HTTP timeout. | 30s |
| PIPEDRIVE_COMPANY_DOMAIN | No | Subdomain (e.g. `acme` for `acme.pipedrive.com`). After `pipedrive-mcp login`, recorded in user config and no longer required in env. |
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
ActivityMaintained
ResponsivenessNo issues