Exogram Authority Runtime vs Marrow

In-depth architectural comparison of the Exogram Authority Runtime and Marrow 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 Exogram Authority Runtime when:

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

Explore Exogram Authority Runtime Details

Choose Marrow when:

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

Explore Marrow Details

Feature & Specification Comparison

Specification	Exogram Authority Runtime Developer Tools	Marrow Developer Tools
Summary	Model Context Protocol server for the Exogram Authority Runtime.	Runtime governance, proof, outcome closure, and fleet intelligence for MCP-compatible AI agents.
Category & Scope	Developer Tools	Developer Tools

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": {
    "exogram-authority-runtime": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "marrow-3": {
      "command": "npx",
      "args": [
        "-y",
        "--package"
      ]
    }
  }
}

Related MCP Server Comparisons