Skip to main content
Glama
neco001

Python Executor MCP Server

by neco001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Python Executor MCP Server

No user-submitted related servers found.

    Related Servers

    • turhal-python-runner-mcp

      berkayturhal38-cloud
      F
      license
      Not graded
      quality
      C
      maintenance
      Executes Python code in isolated subprocesses with resource limits and timeout, designed for safe execution in Docker containers.
      -

    • mcp-run-isolated-python

      Kigstn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to execute Python code securely in a sandboxed environment. Supports configurable restrictions like no network access and returns results including files.
      MIT

    • Python Sandbox MCP Server

      Ajaja
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to execute Python code in a restricted sandbox for calculations and data analysis, without giving them a real shell.
      -
    • MCP Run Python by pydantic

      MCP Run Pythonofficial

      pydantic
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables secure execution of Python code in a sandboxed WebAssembly environment using Pyodide and Deno. Automatically handles package management and captures complete execution results including stdout, stderr, and return values.
      6,782 PyPI
      194
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: run_python for a single snippet and run_python_batch for parallel execution. Descriptions explicitly state when to use each, eliminating ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent pattern: 'run_python' and 'run_python_batch', with the second adding a descriptive qualifier. This is predictable and easy to understand.

    Tool Count3/5

    With only two tools, the server feels minimal. The tools cover the core need, but the count is borderline per calibration standards (1-2 tools is considered thin).

    Completeness4/5

    For a Python execution server, single and batch execution cover the primary use cases. Minor gaps exist (e.g., no explicit environment management), but the core functionality is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources