A side-by-side look at the MCP Run Python and SanctionsKit developer MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Run Python for code execution work as a local process; choose SanctionsKit developer MCP for code execution. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 48/100 · Fair | 29/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | 1 |
| 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 SanctionsKit developer MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"pydantic-pydantic-ai-mcp-run-python": {
"command": "uvx",
"args": [
"--with",
"pydantic-ai-harness",
"clai"
]
}
}
}
No confirmed install command for SanctionsKit developer MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.