github-copilot-cli-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COPILOT_CLI_PATH | No | Path to Copilot CLI binary | (auto-detect) |
| COPILOT_PERMISSION_MODE | No | Permission mode: autonomous or interactive | autonomous |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_copilot_conversationA | Execute a prompt with GitHub Copilot CLI. Runs Copilot in non-interactive mode (-p) and returns the complete response. Use this for one-shot tasks like code generation, explanation, debugging, etc. In interactive permission mode, may return with needsInput=true if Copilot asks a permission question — use respond_to_copilot to answer. |
| resume_copilot_sessionA | Resume a previous Copilot CLI session by session ID. This continues an existing conversation with additional context or follow-up questions. |
| list_copilot_sessionsA | List available Copilot CLI sessions that can be resumed. Also shows any sessions waiting for permission input. |
| respond_to_copilotA | Respond to a Copilot CLI permission question in interactive mode. When Copilot asks for permission (e.g., 'Allow file modification?'), use this tool to send the user's response (e.g., 'yes', 'no', or custom text). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.