kpi-dealflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KPIDEALFLOW_API_KEY | Yes | Your API key from kpidealflow.com/settings | |
| KPIDEALFLOW_BASE_URL | No | Override for self-hosted or staging | https://kpidealflow.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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_leadA | Add a new lead to the KPI DealFlow pipeline. Use this when someone calls in, texts, emails, or is otherwise identified as a prospect. |
| list_leadsB | List leads from the KPI DealFlow pipeline. Filter by stage, status, or inbound/outbound. |
| get_leadA | Get full details for a specific lead by ID. |
| update_leadB | Update a lead — move them through the pipeline, change their status, or add notes. |
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 targets a distinct operation on leads: creation, listing, retrieval, and update. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tools follow a consistent verb_noun pattern with snake_case (e.g., add_lead, list_leads, get_lead, update_lead). The minor pluralization in list_leads does not detract from clarity.
Four tools is well-scoped for a lead pipeline server. Each tool serves a necessary function without redundancy, and the count falls comfortably within the 3-15 ideal range.
The tools cover the core lead lifecycle: add, list, get, and update. A delete tool is missing, but for many pipelines this may be intentional. Overall, the surface is adequately complete for common agent tasks.