| FMRS | 54 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 14 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 |
|---|
| 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
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| 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
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| 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
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| 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
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Cursor, Claude Code | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 0 | 15 |
|---|