tjariy-code-interpreter-mcp-server
Related Servers
Alternatives to tjariy-code-interpreter-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server providing stateful code execution (Python/JavaScript) with SQL query support, file I/O, and artifact management, replacing Azure Code Interpreter.MIT
- AlicenseAqualityCmaintenanceMCP server that gives AI assistants a secure gVisor-isolated sandbox to run Python or JavaScript code, returning stdout, stderr, and exit codes without local access.115 npmMIT
- AlicenseNot gradedqualityCmaintenanceProduction-grade MCP server that enables AI assistants to execute code securely in isolated E2B sandboxes.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that executes TypeScript/JavaScript code in a sandboxed Bun environment with permission-based security controls, code snippets, and a web management UI.-
- AlicenseAqualityDmaintenanceA general-purpose MCP server providing web search, persistent memory storage, and secure code execution capabilities. It enables AI agents to search the web, store and retrieve data, and run Python/JavaScript code in sandboxed environments.8MIT
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server that enables LLMs to safely execute code, control file systems, search the web, and integrate with services like Gmail and TMDB.MIT
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.