PRIMS vs Tenki Sandbox MCP
A side-by-side look at the PRIMS and Tenki Sandbox MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PRIMS for code execution work over a hosted endpoint; choose Tenki Sandbox MCP 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 PRIMS when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
run_code, list_dir, preview_file.
Choose Tenki Sandbox MCP when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TENKI_API_KEY, TENKI_AUTH_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 51/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | TENKI_API_KEYTENKI_AUTH_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 30 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View PRIMS | View Tenki Sandbox MCP |
Tools & capabilities
PRIMS tools 5
run_codeExecute Python in an isolated sandbox with optional pip deps.list_dirList files/directories inside your session workspace.preview_fileReturn up to 8 KB of a text file for quick inspection.persist_artifactUpload an `output/` file to a client-provided presigned URL.mount_fileDownload a remote file once per session to `mounts/<path>`.
Tenki Sandbox MCP 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.
PRIMS
{
"mcpServers": {
"hileamlakb-prims": {
"url": "http://0.0.0.0:9000/mcp"
}
}
}
Tenki Sandbox MCP
{
"mcpServers": {
"tenki-sandbox-mcp": {
"command": "npx",
"args": [
"-y",
"@tenkicloud/mcp"
],
"env": {
"TENKI_API_KEY": "YOUR_TENKI_API_KEY_HERE",
"TENKI_AUTH_TOKEN": "YOUR_TENKI_AUTH_TOKEN_HERE"
}
}
}
}
Frequently asked questions
PRIMS is categorized under Code Execution and uses a remote HTTP/SSE transport. Tenki Sandbox MCP belongs to Code Execution and uses a local stdio subprocess. Pick PRIMS for code execution work and Tenki Sandbox MCP 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.
PRIMS is listed as free. Auth: no auth required. Tenki Sandbox MCP 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 hileamlakb-prims and tenki-sandbox-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PRIMS has a quality signal of 51/100 (Good) with 3 views, 0 installs and 30 GitHub stars. Tenki Sandbox MCP has 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.