mcp-github-copilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Send a prompt to GitHub Copilot and return the response. Uses logged-in Copilot CLI credentials automatically. |
| list_modelsA | List available Copilot models. |
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 2 tools
The two tools are completely distinct: one sends prompts to Copilot, the other lists available models. There is no overlap or ambiguity between them.
The naming is inconsistent: 'query' is a single-word verb while 'list_models' follows a verb_noun pattern. The generic 'query' also lacks specificity compared to 'list_models'.
With only two tools, the server feels minimal but borderline appropriate for a basic Copilot integration. It covers essential actions but leaves little room for a richer workflow.
The server covers the core action of querying Copilot and listing models, but lacks features like streaming, conversation management, or model details, which may be expected in a fuller implementation.