Exogram Authority Runtime vs Weckr

In-depth architectural comparison of the Exogram Authority Runtime and Weckr 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).
• Primary tools included: create_entities, create_relations, add_observations.

Explore Exogram Authority Runtime Details

Choose Weckr 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).
• Primary tools included: Analyze cost by customer, feature, and model, Surface unprofitable users and plans, Calculate request-level cost, revenue, and margin.

Explore Weckr Details

Feature & Specification Comparison

Specification	Exogram Authority Runtime Developer Tools	Weckr Developer Tools
Summary	Model Context Protocol server for the Exogram Authority Runtime.	Ask which of your customers cost more in LLM calls than they pay, per user and per feature.
Category & Scope	Developer Tools	Developer Tools
Quality signal

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": {
    "weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons