Evidra vs ParallelSandbox

A side-by-side look at the Evidra and ParallelSandbox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Evidra logoEvidraCloud PlatformsFail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.35FairAuth: not declaredParallelSandbox logoParallelSandboxCloud Platforms · Local subprocess (stdio)Remote Linux boxes for coding agents: Docker, a browser, screenshots, logs, human takeover.61GoodAuth: oauth 2.0

Verdict: choose Evidra for cloud platforms work; choose ParallelSandbox for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Evidra logoChoose Evidra when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore Evidra

ParallelSandbox logoChoose ParallelSandbox when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like parallelsandbox_connect.
Explore ParallelSandbox

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEvidra logoEvidraParallelSandbox logoParallelSandbox
CategoryCloud PlatformsCloud Platforms
Quality signal35/100 · Fair61/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars150
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Evidra tools

No tool names declared yet. Check the project README from the listing page.

ParallelSandbox tools 1

  • parallelsandbox_connectConnect ParallelSandbox, or check sign-in status. If sign-in is pending, show the person the returned link to sign in and allow their AI tool. Call again after they finish.

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.

Evidra

No confirmed install command for Evidra yet — follow the setup steps linked from its listing page rather than a guessed package name.

ParallelSandbox

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "parallelsandbox-2": {
      "command": "npx",
      "args": [
        "-y",
        "parallelsandbox-mcp"
      ]
    }
  }
}

Frequently asked questions

Evidra is categorized under Cloud Platforms and uses an install path we have not confirmed yet. ParallelSandbox belongs to Cloud Platforms and uses a local stdio subprocess. Pick Evidra for cloud platforms work and ParallelSandbox for cloud platforms.

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. Evidra has no confirmed install command yet — follow its own setup instructions.

Evidra has no declared pricing — check the project's own site. ParallelSandbox is listed as free. Auth: oauth 2.0. 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 evidra-2 and parallelsandbox-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Evidra has a quality signal of 35/100 (Fair) with 3 views, 0 installs and 15 GitHub stars. ParallelSandbox has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.