Miinta Pipedrive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | HTTP Server Port (only used if TRANSPORT_MODE is http or sse) | 3000 |
| MCP_AUTH_TOKEN | No | MCP Authentication Token (required if not localhost) | |
| TRANSPORT_MODE | No | Transport mode - stdio, http, or sse | stdio |
| DEFAULT_TIMEZONE | No | Default timezone | Europe/Madrid |
| CACHE_TTL_SECONDS | No | Cache TTL in seconds | 3600 |
| PIPEDRIVE_API_BASE | No | Pipedrive API Base URL | https://api.pipedrive.com/v2 |
| PIPEDRIVE_API_TOKEN | Yes | Pipedrive API Token (Bearer token) | |
| MAX_ITEMS_PER_SECTION | No | Maximum items per section | 50 |
| PIPEDRIVE_COMPANY_DOMAIN | No | Pipedrive Company Domain for deal URLs | app.pipedrive.com |
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 |
|---|---|
| miinta.filters.listA | List all available Pipedrive saved filters. Useful for discovering filter IDs and names before calling miinta.sales_queue.get. Optionally filter by type. |
| miinta.filters.createA | Create a new Pipedrive saved filter. Useful for creating custom activity or deal filters that can then be used with miinta.sales_queue.get. Returns the created filter with its ID. |
| miinta.filters.deleteA | Delete a Pipedrive saved filter by its ID. Use miinta.filters.list to find filter IDs. |
| miinta.sales_queue.getA | Return a structured "morning queue" payload using three Pipedrive filters (by ID or name), plus enrichment (deal title, stage name, org/person names, URLs). Use miinta.filters.list to discover available filter names. |
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 4 tools
Each tool has a distinct purpose: list, create, delete filters, and get the sales queue. The sales queue tool depends on filters but does not overlap with filter CRUD operations. No ambiguity between tools.
All tools follow a consistent `miinta.<resource>.<action>` pattern: `miinta.filters.list`, `miinta.filters.delete`, `miinta.filters.create`, and `miinta.sales_queue.get`. The convention is uniform and predictable.
With four tools, the set is concise and well-scoped for managing filters and retrieving a sales queue. It fits within the ideal 3-15 range and each tool is necessary for the intended workflow.
Filter CRUD is partially covered: create, list, delete, but no update or get-by-id. The sales queue tool is the core feature and works via filters. Minor gaps exist but can be worked around by deleting/recreating filters.