What is the key difference between Nexus and Kagimcp?

Nexus belongs to the Search & Data Extraction category with local stdio execution, while Kagimcp belongs to the Search & Data Extraction category with local stdio execution.

How do I install Nexus or Kagimcp 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 Nexus and Kagimcp free or paid?

Nexus operates under a BYOK (Pay Provider Direct) model (API Key required). Kagimcp operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Nexus lists 6 tools with 2 views and 23 GitHub stars. Kagimcp lists 2 tools with 2 views and 468 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both adawalli-nexus and kagisearch-kagimcp 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, Nexus has a Quality Score of 40 /100 ( Fair ) with 2 views, 0 installs, and 23 GitHub stars. Kagimcp holds a Quality Score of 51 /100 ( Good ) with 2 views, 0 installs, and 468 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Nexus vs Kagimcp

In-depth architectural comparison of the Nexus and Kagimcp 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

Nexus

Search & Data Extraction · Local stdio

Quality: 40/100 (Fair) | Auth: API Key required

Kagimcp

Search & Data Extraction · Local stdio

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

Verdict Summary: Choose Nexus if you need specialized Search & Data Extraction tools running via a local process. Choose Kagimcp if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Nexus when:

You need dedicated capabilities in the Search & Data Extraction 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: OPENROUTER_API_KEY.
Primary tools included: Supports multiple OpenRouter AI models including Perplexity Sonar and Grok 4, Real-time web search with configurable timeouts and model tiers, Structured citation extraction from AI responses.

Explore Nexus Details

Choose Kagimcp when:

You need dedicated capabilities in the Search & Data Extraction 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: KAGI_API_KEY, FASTMCP_LOG_LEVEL, KAGI_SEARCH_TIMEOUT, KAGI_EXTRACT_TIMEOUT, KAGI_MAX_RETRIES, KAGI_HIDDEN_PARAMS.

Feature & Specification Comparison

Specification	Nexus adawalli Search & Data Extraction	Kagimcp kagisearch Search & Data Extraction
Summary	AI-powered web search server using Perplexity Sonar models with source citations. Zero-install setup via NPX.	The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
Category & Scope	Search & Data Extraction	Search & Data Extraction

Tools & Capabilities Breakdown

Nexus Tools (6)

Supports multiple OpenRouter AI models including Perplexity Sonar and Grok 4

Real-time web search with configurable timeouts and model tiers

Structured citation extraction from AI responses

Request caching, deduplication, and automatic retries

Zero-install deployment via bunx or npx

TypeScript strict mode with full type coverage

Kagimcp Tools (2)

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

Nexus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "adawalli-nexus": {
      "command": "npx",
      "args": [
        "-y",
        "adawalli-nexus"
      ],
      "env": {
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
      }
    }
  }
}

Kagimcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kagisearch-kagimcp": {
      "command": "npx",
      "args": [
        "-y",
        "kagisearch-kagimcp"
      ],
      "env": {
        "KAGI_API_KEY": "YOUR_KAGI_API_KEY_HERE",
        "FASTMCP_LOG_LEVEL": "YOUR_FASTMCP_LOG_LEVEL_HERE",
        "KAGI_SEARCH_TIMEOUT": "YOUR_KAGI_SEARCH_TIMEOUT_HERE",
        "KAGI_EXTRACT_TIMEOUT": "YOUR_KAGI_EXTRACT_TIMEOUT_HERE",
        "KAGI_MAX_RETRIES": "YOUR_KAGI_MAX_RETRIES_HERE",
        "KAGI_HIDDEN_PARAMS": "YOUR_KAGI_HIDDEN_PARAMS_HERE"
      }
    }
  }
}

Frequently Asked Questions

Nexus is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select Nexus when you need capabilities focused on search & data extraction and Kagimcp when you require tools for search & data extraction.

More alternatives to Nexus More alternatives to Kagimcp Search & Data Extraction category hub