Runno vs Edict

In-depth architectural comparison of the Runno and Edict MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Runno when:

• You need dedicated capabilities in the Code Execution domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Runno Details

Choose Edict when:

• You need dedicated capabilities in the Code Execution domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: EDICT_TRANSPORT.
• Primary tools included: edict_schema, edict_version, edict_examples.

Explore Edict Details

Feature & Specification Comparison

Specification	Runno Code Execution	Edict Sowiedu Code Execution
Summary	Sandboxed runtime for programming languages and WASI binaries. Works in the browser, on your server, or via MCP.	Agent-first programming language: agents produce JSON AST, the compiler validates, type-checks, effect-checks, verifies contracts via Z3/SMT, and compiles to WASM. 19 MCP tools for the full compile-and-execute loop.
Category & Scope	Code Execution

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "runno": {
      "command": "npx",
      "args": [
        "@runno/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "sowiedu-edict": {
      "command": "npx",
      "args": [
        "-y",
        "edict-lang"
      ],
      "env": {
        "EDICT_TRANSPORT": "YOUR_EDICT_TRANSPORT_HERE"
      }
    }
  }
}

Related MCP Server Comparisons