kothar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_for_projectA | Given a project description, recommend the top MCP servers to install and explain why each one fits. Example: "Python FastAPI backend with PostgreSQL and JWT auth" |
| recommend_nextA | Mid-project advisor: given your current MCP stack (list of server names) and a new development context, recommend what to add next and why. Example: current_stack=["github", "filesystem"], new_context="adding Stripe payments and PDF invoices" session_file: optional path to a session notes file whose content is appended to new_context. |
| explain_whyB | Explain why a specific MCP server is a good fit for a given project. Example: server_name="github", project_description="open source Python library with CI/CD" |
| recommend_for_goalA | Decompose a multi-part goal into sub-queries and recommend MCP servers for each part. Splits on hard boundaries: '. ', '; ', ' then ', ', then ', ' and then ' (not bare ' and '). project: optional project context prepended to each sub-query for richer semantic matching. Example: goal="integrate GitHub. add Stripe payments", project="Python FastAPI backend" |
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: explaining a specific server, recommending for a multi-part goal, for a full project, or for next steps. No overlap.
All names follow verb_noun pattern (explain_why, recommend_for_goal, etc.), but 'explain_why' uses 'why' as a noun, slightly deviating from standard action-object convention.
Four tools cover the essential recommendation scenarios without redundancy. The count is well-scoped for the server's purpose.
The set covers main use cases: explaining, recommending for goals, projects, and next steps. Missing features like comparing or updating recommendations, but not critical.