Python Exec Sandbox vs Godot MCP

A side-by-side look at the Python Exec Sandbox and Godot MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Python Exec Sandbox logoPython Exec SandboxCode Execution · Local subprocess (stdio)Sandboxed Python execution for AI agents. PEP 723 inline deps, multi-version Python, zero pollution.52GoodAuth: not declaredGodot MCP logoGodot MCPGaming · Local subprocess (stdio)A MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.67GreatAuth: no auth required

Verdict: choose Python Exec Sandbox for code execution work as a local process; choose Godot MCP for gaming as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Python Exec Sandbox logoChoose Python Exec Sandbox when

  • You need dedicated capabilities in the Code Execution domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like execute_python, check_environment, validate_script.
Explore Python Exec Sandbox

Godot MCP logoChoose Godot MCP when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: GODOT_PATH, DEBUG.
  • You want tools like launch_editor, run_project, get_debug_output.
Explore Godot MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPython Exec Sandbox logoPython Exec SandboxGodot MCP logoGodot MCP
CategoryCode ExecutionGaming
Quality signal52/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedGODOT_PATHDEBUG
Verified ownerCommunity listingCommunity listing
GitHub stars16,281
Directory activity 2 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools314

Tools & capabilities

Python Exec Sandbox tools 3

  • execute_pythonExecute a Python script with automatic dependency management. The script can include PEP 723 inline metadata (# /// script blocks) for declaring dependencies. Additional dependencies can also be passed via the dependencies parameter and will be merged. Args: script: Python source code to execute. May include PEP 723 metadata. dependencies: Extra PEP 508 dependency specifiers to make available. timeout_seconds: Maximum execution time (1-300, default 30). Returns: Formatted output with stdout, stderr, exit code, and duration. Example - simple script: execute_python(script="print('hello')") Example - with dependencies parameter: execute_python( script="import requests; print(requests.get('https://example.com').status_code)", dependencies=["requests>=2.32"] ) Example - with inline dependency metadata (preferred for multiple deps): execute_python(script=''' # /// script # dependencies = ["pandas>=2.2", "numpy>=1.26"] # /// import pandas as pd import numpy as np print(pd.DataFrame({"a": np.arange(5)}).describe()) ''') Always pin dependency versions (e.g. "pandas>=2.2" instead of "pandas") for reproducible results. The inline metadata block (# /// script ... # ///) is the recommended way to declare dependencies directly in the script (see PEP 723: https://peps.python.org/pep-0723/). The dependencies parameter is a simpler alternative when you just need to add a few packages. Both accept standard pip-style version specifiers like "requests>=2.28" or "pandas" (see PEP 508: https://peps.python.org/pep-0508/).
  • check_environmentCheck the execution environment and report status. Returns information about Python version, uv version, platform, sandbox configuration, and cache status.
  • validate_scriptValidate a Python script's PEP 723 metadata and dependencies without executing it. Checks metadata syntax, dependency format, and requires-python compatibility. Args: script: Python source code to validate. May include inline dependency metadata (# /// script blocks, see https://peps.python.org/pep-0723/). dependencies: Extra dependency specifiers to validate, using standard pip-style format like "requests>=2.28" (see https://peps.python.org/pep-0508/). Returns: Validation result with metadata details or error information.

Godot MCP tools 14

  • launch_editorLaunch Godot editor for a specific project
  • run_projectRun the Godot project and capture output
  • get_debug_outputGet the current debug output and errors
  • stop_projectStop the currently running Godot project
  • get_godot_versionGet the installed Godot version
  • list_projectsList Godot projects in a directory
  • get_project_infoRetrieve metadata about a Godot project
  • create_sceneCreate a new Godot scene file
  • add_nodeAdd a node to an existing scene
  • load_spriteLoad a sprite into a Sprite2D node
  • export_mesh_libraryExport a scene as a MeshLibrary resource
  • save_sceneSave changes to a scene file
  • +2 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Python Exec Sandbox

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "python-exec-sandbox": {
      "command": "uvx",
      "args": [
        "mcp-python-exec-sandbox"
      ]
    }
  }
}

Godot MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "coding-solo-godot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "env": {
        "GODOT_PATH": "YOUR_GODOT_PATH_HERE",
        "DEBUG": "YOUR_DEBUG_HERE"
      }
    }
  }
}

Frequently asked questions

Python Exec Sandbox is categorized under Code Execution and uses a local stdio subprocess. Godot MCP belongs to Gaming and uses a local stdio subprocess. Pick Python Exec Sandbox for code execution work and Godot MCP for gaming.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Python Exec Sandbox has no declared pricing — check the project's own site. Godot MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add python-exec-sandbox and coding-solo-godot-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Python Exec Sandbox has a quality signal of 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Godot MCP has 67/100 (Great) with 10 views, 0 installs and 6,281 GitHub stars.