MCP Code Mode
Related Servers
Alternatives to MCP Code Mode
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for secure, session-based Python code execution in Docker containers, enabling LLM applications to run code, manage state, and access files.9MIT
- AlicenseAqualityDmaintenanceA production-grade MCP server providing a persistent Python REPL with multi-session support, sandboxing, and timeout protection, enabling LLM agents to execute Python code across multiple turns with variables that persist between calls.121MIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server providing file operations, web search, URL scraping, and sandboxed command execution for LLM interactions.1MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server enabling LLMs to execute commands, manage files, interact with Figma, search the web, generate images, and more, extending their capabilities beyond text generation.Apache 2.0
- 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
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.121MIT
TDQS
Scored across 9 tools
Each tool has a clear and distinct purpose. run_python and run_python_stream are differentiated by streaming vs. non-streaming execution. run_with_retry adds retry logic. Learning tools (add_learning, record_semantic_failure) handle different failure types. configure, get_learnings, get_system_context, and pip_install are all unique and unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., add_learning, run_python, get_system_context. There are no deviations or mixed conventions.
With 9 tools, the set is well-scoped for a code execution MCP server. It covers execution, learning, configuration, context retrieval, and package management without redundancy or gaps.
The tool surface covers core workflows: code execution (with variants), error/semantic learning, configuration, system context, and package installation. Minor gaps exist (e.g., no tool to delete or update learnings), but overall it's nearly complete for the stated purpose.