code-execution-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_EXEC_LOG_DIR | No | Log directory (default empty = logging disabled) | |
| CODE_EXEC_EXECUTABLE | No | Shell executable (default: /bin/bash on Unix, powershell.exe on Windows) | /bin/bash |
| CODE_EXEC_INIT_COMMANDS | No | Init commands (semicolon-separated, run when creating new sessions, empty by default) | |
| CODE_EXEC_DIALOG_TIMEOUT | No | Timeout for dialog prompts in seconds | 5 |
| CODE_EXEC_MAX_EXEC_TIMEOUT | No | Maximum execution timeout in seconds | 180 |
| CODE_EXEC_FIRST_OUTPUT_TIMEOUT | No | Timeout for first output in seconds | 30 |
| CODE_EXEC_BETWEEN_OUTPUT_TIMEOUT | No | Timeout between output chunks in seconds | 15 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_terminalD | – |
| execute_pythonD | – |
| get_outputD | – |
| reset_terminalD | – |
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
The two execution tools (execute_terminal and execute_python) are distinct by target environment, but without descriptions an agent might initially confuse them. get_output and reset_terminal are clearly distinct.
All tool names follow a consistent verb_noun snake_case pattern: execute_terminal, execute_python, get_output, reset_terminal. This is uniform and predictable.
Four tools is well-scoped for a code execution server: two execution methods, output retrieval, and terminal reset. Each tool earns its place.
The core lifecycle of execute, retrieve output, and reset is covered. Minor gaps exist around managing multiple concurrent sessions or explicit error/status checks, but agents can work within this surface.