API Governance vs Godot MCP

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

API Governance logoAPI GovernanceAgreements & Coordination · Local subprocess (stdio)Contract-change authorization for AI agents. Signed receipts verify offline.55GoodAuth: not declaredGodot MCP logoGodot MCPGaming · Local subprocess (stdio)A MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.67GreatAuth: no auth required

Verdict: choose API Governance for agreements & coordination work as a local process; choose Godot MCP for gaming as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

API Governance logoChoose API Governance when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: CODERIFTS_API_KEY.
  • You want tools like preflight_change_set, verify_receipt, get_decision_details.
Explore API Governance

Godot MCP logoChoose Godot MCP when

  • You need dedicated capabilities in the Gaming domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: GODOT_PATH, DEBUG.
  • You want tools like launch_editor, run_project, get_debug_output.
Explore Godot MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAPI Governance logoAPI GovernanceGodot MCP logoGodot MCP
CategoryAgreements & CoordinationGaming
Quality signal55/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsCODERIFTS_API_KEYGODOT_PATHDEBUG
Verified ownerCommunity listingCommunity listing
GitHub stars06,293
Directory activity 1 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools314

Tools & capabilities

API Governance tools 3

  • preflight_change_setPreflight a complete base→head change set of contract artifacts. Returns risk score and breaking-change analysis. With `preflight_mode: "authorize"` (and `context.operation`), returns a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) and may mint a signed chain-receipt. With `prefligh…
  • verify_receiptVerify a signed chain-receipt you already hold: signature authenticity, body binding, and (when lifecycle indices are available) whether it is currently authorized for a stated operation/target. Requires `token`. Does not re-diff specs.
  • get_decision_detailsRetrieve a past decision by `decision_id` (preferred) or `fingerprint`: stored report, breaking changes, scores, and linked receipt metadata if present. Not for a new analysis of the current change set.

Godot MCP tools 14

  • launch_editorLaunch Godot editor for a specific project
  • run_projectRun the Godot project and capture output
  • get_debug_outputGet the current debug output and errors
  • stop_projectStop the currently running Godot project
  • get_godot_versionGet the installed Godot version
  • list_projectsList Godot projects in a directory
  • get_project_infoRetrieve metadata about a Godot project
  • create_sceneCreate a new Godot scene file
  • add_nodeAdd a node to an existing scene
  • load_spriteLoad a sprite into a Sprite2D node
  • export_mesh_libraryExport a scene as a MeshLibrary resource
  • save_sceneSave changes to a scene file
  • +2 more on the listing page

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.

API Governance

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "api-governance-2": {
      "command": "npx",
      "args": [
        "-y",
        "coderifts"
      ],
      "env": {
        "CODERIFTS_API_KEY": "YOUR_CODERIFTS_API_KEY_HERE"
      }
    }
  }
}

Godot MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "coding-solo-godot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "env": {
        "GODOT_PATH": "YOUR_GODOT_PATH_HERE",
        "DEBUG": "YOUR_DEBUG_HERE"
      }
    }
  }
}

Frequently asked questions

API Governance is categorized under Agreements & Coordination and uses a local stdio subprocess. Godot MCP belongs to Gaming and uses a local stdio subprocess. Pick API Governance for agreements & coordination work and Godot MCP for gaming.

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.

API Governance has no declared pricing — check the project's own site. Godot MCP is listed as free. Auth: no auth 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 api-governance-2 and coding-solo-godot-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, API Governance has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Godot MCP has 67/100 (Great) with 10 views, 0 installs and 6,293 GitHub stars.