What is the key difference between Cortex and MCP Orchestrator?

Cortex belongs to the Aggregators category with local stdio execution, while MCP Orchestrator belongs to the Aggregators category with local stdio execution.

How do I install Cortex or MCP Orchestrator 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 Cortex and MCP Orchestrator free or paid?

Cortex operates under a BYOK (Pay Provider Direct) model (API Key required). MCP Orchestrator operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cortex lists 6 tools with 3 views and 21 GitHub stars. MCP Orchestrator lists 2 tools with 2 views and 6 GitHub stars.

Can I use both Cortex and MCP Orchestrator 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.

Side-by-Side Model Context Protocol Comparison

Cortex vs MCP Orchestrator

In-depth architectural comparison of the Cortex and MCP Orchestrator 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

Cortex

Aggregators · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

MCP Orchestrator

Aggregators · Local stdio

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

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

Which MCP Server Should You Choose?

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

Choose MCP Orchestrator 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).
Primary tools included: tool_search, call_remote_tool.

Explore MCP Orchestrator Details

Feature & Specification Comparison

Specification	Cortex gzoonet Aggregators	MCP Orchestrator rupinder2 Aggregators
Summary	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.	Central hub that aggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading.
Category & Scope

Tools & Capabilities Breakdown

Cortex Tools (6)

Local knowledge graph for project files

LLM-based entity and relationship extraction

Natural-language graph queries with citations

Optional keyword and vector search

Cloud, hybrid, and local LLM routing

CLI and web dashboard

MCP Orchestrator Tools (2)

tool_search

Search for tools using BM25 relevance ranking or regex pattern matching. Searches across tool names, descriptions, and argument names/descriptions. By default, uses BM25 natural language search. Set use_regex=True to search using Python regex patterns instead. Returns tool_reference blocks for discovered tools with deferred loading.

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

Cortex Configuration

mcpServers (Claude Desktop / Cursor)

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

MCP Orchestrator Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rupinder2-mcp-orchestrator": {
      "command": "uvx",
      "args": [
        "mcp-orchestrator"
      ]
    }
  }
}

Frequently Asked Questions

Cortex is categorized under Aggregators and uses a local stdio subprocess. In contrast, MCP Orchestrator belongs to Aggregators using local stdio subprocess. Select Cortex when you need capabilities focused on aggregators and MCP Orchestrator when you require tools for aggregators.

More alternatives to Cortex More alternatives to MCP Orchestrator Aggregators category hub