tjariy-code-interpreter-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | AWS region for Bedrock AgentCore CodeInterpreter | us-west-2 |
| AWS_PROFILE | No | AWS profile to use for credentials | default |
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 |
|---|---|
| execute_codeC | Execute code in a secure sandboxed environment. Supports Python, JavaScript, and TypeScript. |
| execute_commandC | Execute a shell command in the sandbox environment |
| read_filesA | Read file contents from the sandbox filesystem |
| write_filesC | Write files to the sandbox filesystem |
| list_filesA | List files in a directory in the sandbox |
| remove_filesB | Remove files from the sandbox filesystem |
| start_sessionC | Start a new code interpreter session |
| stop_sessionA | Stop the current code interpreter session |
| get_sessionB | Get information about a specific session |
| list_sessionsA | List all code interpreter sessions |
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 10 tools
execute_code and execute_command both involve running something, which could cause minor confusion, but the former is for Python/JavaScript/TypeScript code and the latter is for shell commands. File operations and session operations are each clearly distinct from one another.
All tools follow a consistent verb_noun snake_case pattern such as execute_code, list_files, start_session, and stop_session. The naming is predictable and easy to navigate.
10 tools is well-scoped for a code interpreter sandbox, covering execution, shell commands, file management, and session lifecycle without redundancy. Each tool serves a clear and necessary purpose.
The toolset provides complete lifecycle coverage for sessions and files, plus code and shell execution. There are no obvious missing operations that would prevent an agent from accomplishing typical sandbox tasks.