Best for
- Developers who need a unified AI endpoint
- Users of Claude Code, Cursor, Cline, Codex, or other coding agents
- Teams interested in free tiers, cost-aware routing, and local deployment
O
OmniRoute
Community
A free AI gateway for 290+ providers through one endpoint
GitHub source repository ↗
54FMRS · D
The source presents OmniRoute as a broad open-source local AI gateway focused on multi-provider routing, free-tier aggregation, fallback resilience, and token compression. No individual MCP tool identifiers are provided, so the tools list is left empty.
OmniRoute is an MIT-licensed, local-first AI gateway that connects one endpoint to 290+ providers and 500+ models, including 90+ providers with free tiers. It offers quota-aware automatic fallback, 19 routing strategies, RTK and Caveman token compression, MCP and A2A support, and compatibility with multiple coding tools.
Tools
The tool list has not been reviewed yet.
Setup
From the repository root, run npm install && npm run dev, or install globally with npm install -g omniroute. Start the stdio MCP server with omniroute --mcp, or connect to http://localhost:20128/api/mcp/stream or /api/mcp/sse. The README also provides this Claude Code command: claude mcp add-server omniroute --type http --url http://localhost:20128/api/mcp/stream.
Fit and risk
Not for
- Users who only need one model through its official client
- Users unwilling to manage provider keys, quotas, and routing policies
- Users seeking a hosted cloud service or official product integration not documented in the source
Required permissions
- Access to the local OmniRoute gateway and its MCP interfaces
- Use of configured provider credentials or built-in keyless free providers
- MCP access to routing, providers, combos, cache, compression, and memory; remote tokens support read, write, and admin scopes
- Process-spawning routes remain restricted to loopback access
Risks and side effects
- Automatic fallback may send requests to different providers or models
- Remote MCP exposes access to 104 tools, subject to token scopes and configuration
- Free tiers, quotas, provider terms, and availability may change; the README notes ToS flags for some providers
- Aggressive compression can alter context wording, although code, URLs, JSON, and structured data are preserved
Troubleshooting
- Confirm that the local service is running at http://localhost:20128
- Run omniroute doctor to inspect providers, ports, and native dependencies
- Verify the MCP endpoint path: /api/mcp/stream or /api/mcp/sse
- If auto does not respond, check the health and quota status of built-in or configured providers
- For remote mode, verify the selected context, token scope, and connection settings
Use cases
Unifying access to multiple AI providers and models
Configuring automatic routing and quota fallback for coding agents
Reducing tool-output and context token usage through compression
Allowing MCP or A2A agents to manage gateway providers, combos, caching, and memory
Supported clients
Claude DesktopFull support
CursorFull support
Claude CodeFull support