ai2dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI2DEV_API_KEY | Yes | Bearer token for the AI2DEV API | |
| ANTHROPIC_MODEL | No | Anthropic model to use (default: claude-opus-4-8) | claude-opus-4-8 |
| ANTHROPIC_API_KEY | Yes | API key for Anthropic (used by LLM tools) | |
| AI2DEV_API_BASE_URL | No | Base URL of the AI2DEV API (default: placeholder) | https://api.ai2dev.example.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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_design_documentA | Generate a software design document from a project description using an LLM. Args: project_name: Name of the software project. requirements: Free-form description of what the project should do. target_audience: Optional description of who the software is for. constraints: Optional technical or business constraints to respect. |
| refine_design_documentA | Revise an existing design document based on feedback, preserving its structure. Args: design_document: The current design document (markdown). feedback: Requested changes or additional context to incorporate. |
| ask_questionB | Answer a free-form question, optionally grounded in supplied context (e.g. a design doc). Args: question: The user's question. context: Optional supporting context, such as a design document. |
| create_ai2dev_projectB | Create a new project in AI2DEV from a finalized design document. Args: project_name: Name for the new AI2DEV project. design_document: The finalized design document content. description: Optional short project description. |
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
Most tools target distinct phases (design doc generation, refinement, project creation), but 'ask_question' is generic and could be confused with other tools if used for design-related queries, though its purpose is broader.
Three tools follow a clear verb_noun pattern (generate_design_document, refine_design_document, create_ai2dev_project), but 'ask_question' breaks the pattern and does not reference the domain, causing minor inconsistency.
With 4 tools covering the core design-to-project workflow plus a general Q&A, the count is well-scoped and feels neither too sparse nor overwhelming.
The core flow (generate doc, refine doc, create project) is covered, but missing operations like listing, updating, or deleting projects create notable gaps for a complete lifecycle.