MCP Toolbox for Databases vs Run402
A side-by-side look at the MCP Toolbox for Databases and Run402 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Toolbox for Databases for databases work as a local process; choose Run402 for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Toolbox for Databases when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Choose Run402 when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
up, deploy, status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 53/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16,831 | 24 |
| Directory activity | 8 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View MCP Toolbox for Databases | View Run402 |
Tools & capabilities
MCP Toolbox for Databases tools
No tool names declared yet. Check the project README from the listing page.
Run402 tools 8
upThe first deploy: any missing setup (wallet, tier, project, workspace link), then the deploy. Returns the `run402.up.result` envelope.deployApplies a ReleaseSpec to a project (`r.project(id).apply`): database, functions, site, `site.public_paths`, assets, subdomains, `routes.replace`. Returns the `DeployResult`.statusr.status()`: the wallet the server acts as (`local_label`, `server_label`, address), tier and lease, allowance, projects, active project.whoamir.orgs.whoami()`: the remote principal, its authenticators, org memberships, and sign-in session grade.doctorr.doctor()`: `{ ok, blocking[], warnings[], checks[] }`.docsThe SDK reference and the `run` primer, shipped in the package: `topic` (a namespace or section) or `search`.runRuns a TypeScript snippet against the SDK in a sandbox; returns the value, the captured logs, and the SDK calls it made.expand_resultPages a stored result: a `run` value or its logs, a `docs` answer, `up`'s detail.
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 Toolbox for Databases
{
"mcpServers": {
"mcp-toolbox-for-databases": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/server"
]
}
}
}
Run402
{
"mcpServers": {
"run402": {
"command": "npx",
"args": [
"-y",
"run402-mcp"
]
}
}
}
Frequently asked questions
MCP Toolbox for Databases is categorized under Databases and uses a local stdio subprocess. Run402 belongs to Databases and uses a local stdio subprocess. Pick MCP Toolbox for Databases for databases work and Run402 for databases.
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 Toolbox for Databases is listed as free. Run402 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 mcp-toolbox-for-databases and run402 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Toolbox for Databases has a quality signal of 53/100 (Good) with 8 views, 0 installs and 16,831 GitHub stars. Run402 has 60/100 (Good) with 1 views, 0 installs and 24 GitHub stars.