| FMRS | 43 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 4 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 14 / 20 |
|---|
| Maintenance | 8 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 14 / 20 |
|---|
| Best for | - Developers who regularly use Claude Code, Codex CLI, Gemini CLI, or other supported AI coding CLIs.
- Users seeking to reduce context usage from large repositories, logs, screenshots, and skill files.
- Users comfortable with modifying local AI-client configuration and creating indexes and caches.
| - 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 seeking a standard MCP server manifest, documented MCP transport, or directly callable MCP tool inventory.
- Users who do not want a global npm package, registered hooks, or client-configuration changes.
- Production users requiring validated macOS support; the README labels macOS as untested.
| - 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 | - Requires installing a global Node.js/npm package.
- Requires writing client configuration and hook files for supported AI tools.
- Requires reading project files, Git information, and relevant session data to build indexes, caches, and compact manifests.
- The optional worker runs as a local background process.
| - 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 | - Hooks intercept or rewrite reads, Bash commands, screenshots, and other tool calls, which can change how original output is presented.
- Indexes, caches, and session manifests store project or tool output locally; the README does not document complete retention or encryption behavior.
- The README claims to scan fetched web content and block prompt injection, but this should not replace human review or the client's own security controls.
- Some bridges are not validated against live instances, including the documented Qwen, OpenClaw, and pi integrations; Copilot hook failures can deny all tool calls in a session.
- Repository metadata says NOASSERTION for the license, while the README badge shows PolyForm Noncommercial; verify the repository license before use.
| - 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 Code, Codex, Gemini CLI, Qwen Code, GitHub Copilot CLI, OpenCode, pi, Grok CLI | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 0 | 15 |
|---|