nexus  by grafbase

AI router for unified LLM and MCP access

Created 1 month ago
318 stars

Top 85.0% on SourcePulse

GitHubView on GitHub
Project Summary

Nexus is an AI router designed to aggregate and manage multiple AI models, APIs, and Model Context Protocol (MCP) servers through a unified endpoint. It enables centralized control, routing, and governance for complex AI stacks, benefiting developers and organizations building AI-powered applications.

How It Works

Nexus acts as a central gateway, abstracting the complexity of interacting with various LLM providers (OpenAI, Anthropic, Google) and MCP servers. It supports multiple MCP server types (STDIO, SSE, HTTP) and LLM providers, routing requests based on configured models. Its context-aware tool search allows natural language queries across all connected tools, enhancing discoverability and usability.

Quick Start & Requirements

  • Installation:
    • Linux/Windows (WSL)/macOS: curl -fsSL https://nexusrouter.com/install | bash
    • Docker: docker pull ghcr.io/grafbase/nexus:latest
  • Configuration: Requires a nexus.toml file for setup.
  • Dependencies: None explicitly mentioned beyond standard system tools for the binary install. Docker image handles dependencies.
  • Documentation: https://nexusrouter.com/docs

Highlighted Details

  • Unified API for OpenAI, Anthropic, and Google LLMs.
  • Supports STDIO, SSE, and streamable HTTP MCP servers.
  • Context-aware fuzzy search for MCP tools.
  • Comprehensive rate limiting (global, per-IP, per-server, per-tool, token-based).
  • Optional OAuth2 integration for securing endpoints.
  • Token forwarding allows users to supply their own API keys.

Maintenance & Community

Licensing & Compatibility

  • Licensed under the Mozilla Public License 2.0 (MPL-2.0).
  • Compatible with commercial use and closed-source linking, subject to MPL-2.0 terms.

Limitations & Caveats

  • Token-based rate limiting relies on client identification being enabled and configured.
  • STDIO server tool discovery is dynamic and may take time after startup.
  • OAuth2 configuration requires careful setup of JWKs URLs and claims validation for security.
Health Check
Last Commit

12 hours ago

Responsiveness

Inactive

Pull Requests (30d)
107
Issues (30d)
9
Star History
309 stars in the last 30 days

Explore Similar Projects

Feedback? Help us improve.