Tenki Sandbox MCP vs MCP Js
A side-by-side look at the Tenki Sandbox MCP and MCP Js MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tenki Sandbox MCP for code execution work as a local process; choose MCP Js for code execution over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose MCP Js when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
run_js, get_execution, get_execution_output.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 40/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | TENKI_API_KEYTENKI_AUTH_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 59 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Tenki Sandbox MCP | View MCP Js |
Tools & capabilities
Tenki Sandbox MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Js tools 5
run_jsStateful: queue execution → `{execution_id}`. Stateless: run and return `{output, error?}`.get_executionPoll status/result of an execution.get_execution_outputRead paginated console output (line or byte).cancel_executionTerminate a running execution.list_executionsList executions and their status.
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.
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"
}
}
}
}
MCP Js
{
"mcpServers": {
"r33drichards-mcp-js": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
Tenki Sandbox MCP is categorized under Code Execution and uses a local stdio subprocess. MCP Js belongs to Code Execution and uses a remote HTTP/SSE transport. Pick Tenki Sandbox MCP for code execution work and MCP Js 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.
Tenki Sandbox MCP has no declared pricing — check the project's own site. MCP Js is listed as free. Auth: api key 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 tenki-sandbox-mcp and r33drichards-mcp-js as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tenki Sandbox MCP has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. MCP Js has 57/100 (Good) with 2 views, 0 installs and 59 GitHub stars.