A
licenseA
qualityC
maintenanceMCP server for GitHub Copilot that allows querying any Copilot model programmatically using existing Copilot CLI credentials, with support for file attachments and model discovery.
2
10 npm
MIT
github-copilot-cli-mcp-server
by slcwahn
Related Servers
Alternatives to github-copilot-cli-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceWraps the local Qoder CLI into an MCP server, enabling any MCP client to delegate coding tasks to a local Qoder agent with session management, sandboxed permissions, and model selection.348 npmMIT
- AlicenseCqualityDmaintenanceConnects MCP-enabled editors to GitHub Copilot CLI for non-interactive code analysis, batch processing, and code review.1015 npm5MIT
- AlicenseAqualityBmaintenanceMCP server for opencode that queries GitHub Copilot models via a persistent opencode server, requiring no API keys.2631 npm1MIT
- AlicenseBqualityCmaintenanceWraps the copilot CLI into MCP tools, allowing third-party MCP clients to invoke Copilot through prompt and command tools.2GPL 3.0
- AlicenseNot gradedqualityCmaintenanceThin MCP server wrapping the Gemini CLI for AI assistants, supporting workspace-aware multi-repository analysis and forward-compatible flags.MIT
TDQS
A4/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct role: run starts a new one-shot conversation, list shows available sessions, resume continues an existing session by ID, and respond answers permission prompts. No two tools overlap in purpose, and the descriptions reinforce the boundaries.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: resume_copilot_session, run_copilot_conversation, list_copilot_sessions, respond_to_copilot. The pattern makes the action and target of each tool immediately predictable.
Tool Count5/5
Four tools is well-scoped for a thin MCP server wrapping GitHub Copilot CLI. Each tool covers a necessary part of the session workflow—start, list, resume, and respond—without redundant or filler tools.
Completeness4/5
The core session lifecycle is covered: starting, listing, resuming, and handling permission input. Minor gaps exist, such as no explicit way to terminate a session or fetch full session transcripts, but these are not critical for the server's apparent purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues