codex-codebuddy-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_codebuddy_sessionA | Configure an isolated CodeBuddy ACP session without starting its process. Use launch_mode="ssh" to run CodeBuddy remotely over an existing OpenSSH configuration. The CodeBuddy process starts lazily on the first prompt. |
| prompt_codebuddyA | Send a text prompt to the bound CodeBuddy session. This lazily starts CodeBuddy. The result either completes the turn or returns a permission request for respond_codebuddy_permission. |
| respond_codebuddy_permissionC | Resolve a pending CodeBuddy permission request and continue the turn. |
| cancel_codebuddy_turnA | Cancel the active turn while keeping the CodeBuddy session available. |
| close_codebuddy_sessionC | Close and remove a CodeBuddy bridge session. |
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 5 tools
Each tool targets a clearly distinct action: session creation, session teardown, sending a prompt, resolving a permission request, and cancelling a turn. There is no overlap or ambiguity between these operations.
All tool names follow a predictable snake_case verb_noun pattern: create_, close_, prompt_, respond_, cancel_. The shared 'codebuddy' anchor makes the set easy to scan and understand.
Five tools cover the full interaction lifecycle without redundancy. Each tool corresponds to a distinct phase of using a CodeBuddy session, so the count is well-scoped for the server's purpose.
The tool surface covers the complete workflow: create a session, prompt it, handle permission requests, cancel turns, and close the session. There are no obvious dead ends or missing operations needed for the advertised functionality.