What is the key difference between Edict and Openapi To MCP?

Edict belongs to the Code Execution category with local stdio execution, while Openapi To MCP belongs to the Code Execution category with local stdio execution.

How do I install Edict or Openapi To MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Edict and Openapi To MCP free or paid?

Edict operates under a Free / Open Source model (No auth required). Openapi To MCP operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Edict lists 22 tools with 2 views and 12 GitHub stars. Openapi To MCP lists 4 tools with 2 views and 34 GitHub stars.

Can I use both Edict and Openapi To MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Edict vs Openapi To MCP

In-depth architectural comparison of the Edict and Openapi To MCP 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.

At a Glance & Executive Verdict

Edict

Code Execution · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Openapi To MCP

Code Execution · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Edict if you need specialized Code Execution tools running via a local process. Choose Openapi To MCP if your workspace requires Code Execution integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

Choose Openapi To MCP when:

You need dedicated capabilities in the Code Execution domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: BEARER_TOKEN, OAUTH_2_CLIENT_ID, OAUTH_2_CLIENT_SECRET, OAUTH_2_TOKEN_URL, OAUTH_2_USERNAME, OAUTH_2_PASSWORD, OAUTH_2_REFRESH_TOKEN.
Primary tools included: .

Feature & Specification Comparison

Specification	Edict Sowiedu Code Execution	Openapi To MCP ouvreboite Code Execution
Summary	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.	⃣ ☁️ - Lightweight MCP server to access any API using their OpenAPI specification. Supports OAuth2 and full JSON schema parameters and request body.
Category & Scope

Tools & Capabilities Breakdown

Edict Tools (22)

edict_schema

Returns the full AST JSON Schema — the spec for how to write programs

edict_version

Returns compiler version and capability info

edict_examples

Returns 41 example programs as JSON ASTs (includes schema snippet)

edict_validate

Validates AST structure (field names, types, node kinds)

edict_check

Full pipeline: validate → resolve names → type check → effect check → verify contracts

edict_compile

Compiles a checked AST to WASM (returns base64-encoded binary)

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).

Edict Configuration

mcpServers (Claude Desktop / Cursor)

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

Openapi To MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ouvreboite-openapi-to-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ouvreboite-openapi-to-mcp"
      ],
      "env": {
        "BEARER_TOKEN": "YOUR_BEARER_TOKEN_HERE",
        "OAUTH_2_CLIENT_ID": "YOUR_OAUTH_2_CLIENT_ID_HERE",
        "OAUTH_2_CLIENT_SECRET": "YOUR_OAUTH_2_CLIENT_SECRET_HERE",
        "OAUTH_2_TOKEN_URL": "YOUR_OAUTH_2_TOKEN_URL_HERE",
        "OAUTH_2_USERNAME": "YOUR_OAUTH_2_USERNAME_HERE",
        "OAUTH_2_PASSWORD": "YOUR_OAUTH_2_PASSWORD_HERE",
        "OAUTH_2_REFRESH_TOKEN": "YOUR_OAUTH_2_REFRESH_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

Edict is categorized under Code Execution and uses a local stdio subprocess. In contrast, Openapi To MCP belongs to Code Execution using local stdio subprocess. Select Edict when you need capabilities focused on code execution and Openapi To MCP when you require tools for code execution.

More alternatives to Edict More alternatives to Openapi To MCP Code Execution category hub Canonical compare URL