Keshro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KESHRO_API_TOKEN | Yes | Your Keshro API token, get one from keshro.com/account |
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
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 25 tools
Tools are mostly distinct, with clear verbs like add, block, complete, start, unblock. However, 'create_plan' and 'generate_plan' may cause confusion, as well as 'plan_status' vs 'get_plan', though context may differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_task, get_plan, list_projects). No mixing of conventions.
25 tools is on the high side, exceeding the typical well-scoped range of 3-15. While the domain is broad, the count feels slightly heavy and may include some redundancy.
The tool set covers task, plan, and project lifecycles well, but lacks delete operations for any resource, which is a notable gap. Update is present only for plans, not projects.