MCP Run Python vs SMB Sandbox
A side-by-side look at the MCP Run Python and SMB Sandbox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SMB SandboxCode Execution · Local subprocess (stdio)Mock small-business CRM, inbox, calendar, invoicing and phone tools for testing AI agents safely.33EmergingAuth: not declaredVerdict: choose MCP Run Python for code execution work as a local process; choose SMB Sandbox for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Run Python when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
SChoose SMB Sandbox when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SMB Sandbox | |
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 48/100 · Fair | 33/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 20,470 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Run Python | View SMB Sandbox |
Tools & capabilities
MCP Run Python tools
No tool names declared yet. Check the project README from the listing page.
SMB Sandbox tools
No tool names declared yet. Check the project README from 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.
MCP Run Python
{
"mcpServers": {
"pydantic-pydantic-ai-mcp-run-python": {
"command": "uvx",
"args": [
"--with",
"pydantic-ai-harness",
"clai"
]
}
}
}
SMB Sandbox
{
"mcpServers": {
"smb-sandbox": {
"command": "npx",
"args": [
"-y",
"@teamshift/sandbox-mcp"
]
}
}
}
Frequently asked questions
MCP Run Python is categorized under Code Execution and uses a local stdio subprocess. SMB Sandbox belongs to Code Execution and uses a local stdio subprocess. Pick MCP Run Python for code execution work and SMB Sandbox for code execution.
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.
MCP Run Python is listed as free. Auth: no auth required. SMB Sandbox has no declared pricing — check the project's own site. 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 pydantic-pydantic-ai-mcp-run-python and smb-sandbox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Run Python has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 20,470 GitHub stars. SMB Sandbox has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.