kenda-ingestion-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KENDA_TOKEN | No | Override for the Kenda ingest token. Default is read from ~/.kenda/config.json. | |
| KENDA_ENDPOINT | No | Override for the Kenda API endpoint. Default is read from ~/.kenda/config.json. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kenda_spend_summaryA | Top-line Kenda spend, waste, and health for your org. |
| kenda_waste_by_agentA | Per-agent spend and redundant (wasted) dollars. |
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 2 tools
The two tools have clearly distinct purposes: one provides an org-wide summary of spend/waste/health, the other breaks down waste per agent. No overlap or ambiguity.
Both tool names use the 'kenda_' prefix and are descriptive (spend_summary, waste_by_agent). While not a strict verb_noun pattern, the naming is consistent in style and clearly conveys the tool's function.
With only 2 tools, the server is minimal but appropriately scoped for a focused domain of Kenda spend/waste. The count is slightly low but reasonable for a targeted set.
The server covers top-level summary and per-agent waste, but lacks other potentially useful operations like time trends, department breakdowns, or cost allocation. Notable gaps exist for a more complete spend analysis surface.