What is the key difference between Cortex and Apifable?

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

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

Cortex operates under a BYOK (Pay Provider Direct) model (API Key required). Apifable 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 20 GitHub stars. Apifable lists 7 tools with 1 views and 10 GitHub stars.

Can I use both Cortex and Apifable 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 Cortex or Apifable 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 Cortex and Apifable free to use, or do they require API keys?

Cortex is listed under a BYOK (Pay Provider Direct) model with API Key required . Apifable 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 Cortex and Apifable at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both gzoonet-cortex and ycs77-apifable 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, Cortex has a Quality Score of 55 /100 ( Good ) with 3 views, 0 installs, and 20 GitHub stars. Apifable holds a Quality Score of 48 /100 ( Fair ) with 1 views, 0 installs, and 10 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Cortex vs Apifable

In-depth architectural comparison of the Cortex and Apifable 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: 55/100 (Good) | Auth: API Key required

Apifable

Aggregators · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Cortex if you need specialized Aggregators tools running via a local process. Choose Apifable 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)).
You have access to required keys: CORTEX_API_KEY, CORTEX_SERVER_AUTH_TOKEN.
Primary tools included: Watches project files (md, ts, js, py, json, yaml) for changes, Extracts entities and infers relationships using LLMs, Detects contradictions and duplicates automatically.

Explore Cortex Details

Choose Apifable 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).
You have access to required keys: MY_API_KEY.
Primary tools included: get_spec_info, list_endpoints_by_tag, search_endpoints.

Feature & Specification Comparison

Specification	Cortex gzoonet Aggregators	Apifable ycs77 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.	MCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.
Category & Scope	Aggregators

Tools & Capabilities Breakdown

Cortex Tools (6)

Watches project files (md, ts, js, py, json, yaml) for changes

Extracts entities and infers relationships using LLMs

Detects contradictions and duplicates automatically

Supports semantic search combining keyword and vector similarity

Provides web dashboard with live feed and query explorer

MCP server exposing tools: getstatus, listprojects, findentity, querycortex

Apifable Tools (7)

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"
      ],
      "env": {
        "CORTEX_API_KEY": "YOUR_CORTEX_API_KEY_HERE",
        "CORTEX_SERVER_AUTH_TOKEN": "YOUR_CORTEX_SERVER_AUTH_TOKEN_HERE"
      }
    }
  }
}

Apifable Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ycs77-apifable": {
      "command": "npx",
      "args": [
        "-y",
        "ycs77-apifable"
      ],
      "env": {
        "MY_API_KEY": "YOUR_MY_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Cortex More alternatives to Apifable Aggregators category hub