Agile Team MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_HOST | No | The host URL for the Ollama server. | http://localhost:11434 |
| GROQ_API_KEY | Yes | API key for Groq models. | |
| DEFAULT_MODEL | No | The default model to use for prompts. | openai:gpt-4o-mini |
| GEMINI_API_KEY | Yes | API key for Google Gemini models. | |
| OPENAI_API_KEY | Yes | API key for OpenAI models. | |
| DEEPSEEK_API_KEY | Yes | API key for DeepSeek models. | |
| ANTHROPIC_API_KEY | Yes | API key for Anthropic models. | |
| DEFAULT_TEAM_MODELS | No | A JSON array string representing the default list of models used by the agile team. | ["openai:gpt-4.1","anthropic:claude-3-7-sonnet","gemini:gemini-2.5-pro"] |
| DEFAULT_DECISION_MAKER_MODEL | No | The default model used to make decisions in team workflows. | openai:gpt-4o-mini |
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 |
|---|---|
| prompt_toolA | |
| prompt_from_file_toolB | |
| prompt_from_file2file_toolA | |
| list_providers_toolB | |
| list_models_toolB | |
| persona_dm_toolB | |
| persona_ba_toolB | |
| persona_pm_toolC | |
| persona_sw_toolB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_mcp_assets | List MCP Assets prompt for comprehensive server capability overview. Provides dynamic listing of all available prompts, tools, and resources with usage examples and quick start guidance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
There is significant functional overlap between tools, particularly among the persona tools (ba, dm, pm, sw) which share similar decision-making functionality and parameters, and between prompt_from_file_tool and prompt_tool which differ only in input source. However, the descriptions help clarify distinctions, such as persona specializations and file vs. text input.
The naming follows a mixed convention: most tools use snake_case with descriptive names (e.g., list_models_tool, persona_ba_tool), but there are inconsistencies like 'prompt_from_file2file_tool' which uses '2' instead of 'to', and 'prompt_tool' is overly generic compared to others. The pattern is readable but not fully uniform.
With 9 tools, the count is reasonable for an LLM orchestration and persona-based server. It covers provider/model listing, persona generation, and prompt handling, though some tools feel redundant (e.g., multiple persona tools with similar structures). The scope is well-defined but could be streamlined.
The server provides good coverage for LLM model management and persona-based generation, with tools for listing providers/models, sending prompts, and specialized personas. Minor gaps include lack of update/delete operations for models or personas, and no tool for managing provider configurations, but core workflows are supported.