What is the key difference between Aegis and Catalyst Governance?

Aegis belongs to the Security category with local stdio execution, while Catalyst Governance belongs to the Security category with local stdio execution.

How do I install Aegis or Catalyst Governance 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 Aegis and Catalyst Governance free or paid?

Aegis operates under a Free / Open Source model (No auth required). Catalyst Governance operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Aegis lists 6 tools with 3 views and 15 GitHub stars. Catalyst Governance lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Aegis and Catalyst Governance 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.

How do I install Aegis or Catalyst Governance in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Aegis and Catalyst Governance free to use, or do they require API keys?

Aegis is listed under a Free / Open Source model with No auth required . Catalyst Governance operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Aegis and Catalyst Governance at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both acacian-aegis and catalyst-governance as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Aegis has a Quality Score of 53 /100 ( Good ) with 3 views, 0 installs, and 15 GitHub stars. Catalyst Governance holds a Quality Score of 28 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Aegis vs Catalyst Governance

In-depth architectural comparison of the Aegis and Catalyst Governance 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

Aegis

Security · Local stdio

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

Catalyst Governance

Security · Local stdio

Quality: 28/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Aegis if you need specialized Security tools running via a local process. Choose Catalyst Governance if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Aegis when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Auto-instrumentation of 12 AI agent frameworks, Unified governance primitives like Action, Policy, and AuditEvent, Declarative YAML policy definitions with risk and approval rules.

Explore Aegis Details

Choose Catalyst Governance when:

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

Explore Catalyst Governance Details

Feature & Specification Comparison

Specification	Aegis Acacian Security	C Catalyst Governance Security
Summary	Policy-based governance for AI agent tool calls. YAML policies, approval gates, risk assessment, and audit logging. Cross-platform: LangChain, OpenAI, Anthropic, MCP.	Governance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger.
Category & Scope	Security	Security

Tools & Capabilities Breakdown

Aegis Tools (6)

Auto-instrumentation of 12 AI agent frameworks

Unified governance primitives like Action, Policy, and AuditEvent

Declarative YAML policy definitions with risk and approval rules

Cross-framework enforcement including LangChain, OpenAI, Anthropic, MCP

Tamper-evident audit logging and delegation chain tracking

No code changes required in existing agents

Catalyst Governance Tools (0)

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

Aegis Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "acacian-aegis": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

Catalyst Governance Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "catalyst-governance": {
      "command": "npx",
      "args": [
        "-y",
        "catalyst-governance"
      ]
    }
  }
}

Frequently Asked Questions

Aegis is categorized under Security and uses a local stdio subprocess. In contrast, Catalyst Governance belongs to Security using local stdio subprocess. Select Aegis when you need capabilities focused on security and Catalyst Governance when you require tools for security.

More alternatives to Aegis More alternatives to Catalyst Governance Security category hub