MCP Catalogs
Homenexus screenshot

nexus

by Nexus-Router·427·Score 50

Nexus is a unified gateway that aggregates MCP servers, APIs, and LLM providers with security, governance, and routing capabilities.

ai-llmdeveloper-toolssecurity
25
Forks
28
Open issues
2 mo ago
Last commit
2d ago
Indexed

Overview

Nexus serves as a central hub for managing all your AI infrastructure, allowing you to connect multiple MCP servers (via STDIO, SSE, or HTTP) and various LLM providers through a single endpoint. It provides intelligent tool search across all connected resources, enabling context-aware discovery and execution. With built-in security features like OAuth2, CORS, CSRF protection, and flexible rate limiting, it offers enterprise-grade governance for AI deployments. The TOML-based configuration with environment variable substitution makes it easy to set up and customize for different environments.

Try asking AI

After installing, here are 6 things you can ask your AI assistant:

you:Central management for enterprise AI infrastructure with multiple providers and servers
you:Security-gated access to MCP resources with authentication and rate limiting
you:Unified API layer for combining different AI tools and models
you:What MCP protocols does Nexus support?
you:How does Nexus handle authentication for MCP servers?
you:Can Nexus be used as a load balancer for multiple LLM providers?

When to choose this

Choose Nexus when you need a secure gateway to consolidate multiple MCP servers and LLM providers with advanced governance features.

When NOT to choose this

Don't choose Nexus if you need a lightweight solution for connecting to a single MCP server or prefer self-hosted open-source solutions without vendor dependencies.

Tools this server exposes

3 tools extracted from the README
  • mcp_search

    Intelligent fuzzy search across all connected MCP tools using natural language queries

  • llm_openai

    Access OpenAI models through Nexus with full tool calling support

  • llm_anthropic

    Access Anthropic Claude models through Nexus with full tool calling support

Note: Tool names inferred from configuration examples and documentation of MCP server aggregation functionality. No explicit tool list found in the README.

Comparable tools

mcp-routermcp-hubmcp-server-orchestrator

Installation

Quick Install

curl -fsSL https://nexusrouter.com/install | bash

Docker

docker pull ghcr.io/grafbase/nexus:latest

Configuration

Create a nexus.toml file with your MCP servers and LLM providers:

[mcp.servers.github]
url = "https://api.githubcopilot.com/mcp/"
auth.token = "{{ env.GITHUB_TOKEN }}"

[mcp.servers.filesystem]
cmd = ["npx", "-y", "@modelcontextprotocol/server-filesystem", "/home/YOUR_USERNAME/Desktop"]

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "nexus": {
      "command": "nexus",
      "args": []
    }
  }
}

FAQ

What MCP protocols does Nexus support?
Nexus supports STDIO (subprocess), SSE (Server-Sent Events), and streamable HTTP MCP servers with automatic protocol detection for remote servers.
How does Nexus handle authentication for MCP servers?
Nexus supports multiple authentication methods including service tokens, OAuth2 forwarding, and header-based authentication for both individual servers and globally.
Can Nexus be used as a load balancer for multiple LLM providers?
Yes, Nexus provides unified routing for OpenAI, Anthropic, Google, and AWS Bedrock LLM providers with full tool calling support, allowing load balancing and aggregation.

Compare nexus with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.