Arch Tools MCP vs Cortex

In-depth architectural comparison of the Arch Tools MCP and Cortex 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 Arch Tools MCP when:

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

Explore Arch Tools MCP Details

Choose Cortex when:

• You need dedicated capabilities in the Aggregators domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• Primary tools included: Local knowledge graph for project files, LLM-based entity and relationship extraction, Natural-language graph queries with citations.

Explore Cortex Details

Feature & Specification Comparison

Specification	Arch Tools MCP Aggregators	Cortex gzoonet Aggregators
Summary	61 AI agent tools under one key. Web, AI, voice, data, crypto & more. Stripe + x402 USDC payments.	Local-first knowledge graph for developers. Watches project files, extracts entities and relationships via LLMs, builds a queryable knowledge graph with web dashboard and CLI. Provides 4 MCP tools: getstatus, listprojects, findentity, querycortex.
Category & Scope	Aggregators

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

{
  "mcpServers": {
    "gzoonet-cortex": {
      "command": "npx",
      "args": [
        "-y",
        "@gzoo/cortex"
      ]
    }
  }
}

Related MCP Server Comparisons