AutoMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BHOOT_MOCK | No | Set to '1' for offline fixtures only; not for real work. | |
| BHOOT_MODE | No | Mode of operation. Account mode uses BHOOT_MODE=accounts (set by the launchers). | accounts |
| OPENAI_MODEL | No | OpenAI model to use, required for optional API mode. | |
| BHOOT_GROK_BIN | No | Path to the grok executable if installed in a nonstandard location. | |
| OPENAI_API_KEY | No | API key for OpenAI, required for optional API mode. | |
| ANTHROPIC_MODEL | No | Anthropic model to use, required for optional API mode. | |
| BHOOT_CODEX_BIN | No | Path to the codex executable if installed in a nonstandard location. | |
| ANTHROPIC_API_KEY | No | API key for Anthropic, required for optional API mode. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_clarificationA | Compare Claude and OpenAI answers for a technical clarification. Uses API credits in API mode, or a matching browser-captured Sonnet answer and signed-in Codex usage in accounts mode. Supply original request and relevant context. Never use this to grant permissions. If status is needs_user/error or mock is true, ask the user instead of continuing automatically. |
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 selecting between overlapping tools. The purpose is singular and clearly described.
The single tool name 'resolve_clarification' follows the verb_noun convention. With only one tool, the naming is trivially consistent and readable.
One tool feels thin for an MCP server, especially one named AutoMCP which could imply broader automation. However, the tool's narrow clarification-resolution scope makes the count borderline rather than clearly inadequate.
The tool covers the full clarification-resolution workflow, including different modes, statuses, and mock handling. No obvious additional operations are needed for the stated purpose.