MCP Ask-to-Code
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host for SSE mode | 127.0.0.1 |
| MCP_NAME | No | Server name | Autonomous Code Agent |
| MCP_PORT | No | Port for SSE mode (0 for stdio) | 0 |
| CLAUDE_CMD | No | Claude CLI binary path | claude |
| CLAUDE_MODEL | No | Model to use (e.g. claude-sonnet-4-20250514, opus) | |
| MCP_TOOL_NAME | No | Tool function name | ask_autonomous_agent |
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 |
|---|---|
| ask_autonomous_agentA | AUTONOMOUS AGENT: Solves a coding task or answers a question by running an internal agent. This tool has full access to the filesystem, can run tests, read files, and analyze logic. |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap.
With a single tool, naming is trivially consistent; no pattern conflicts exist.
One tool for a broad coding-assistance domain is extremely thin; typical servers have at least a few tools to separate concerns.
The single tool attempts to cover the entire domain, but users cannot compose or select finer-grained operations, leading to a black-box experience.