Copilot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COPILOT_BIN | No | Specify path to copilot binary if not in PATH |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| copilot_promptA | Run a non-interactive Copilot prompt ( |
| copilot_commandB | Run a general Copilot command. Use args exactly like the shell command after |
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
copilot_prompt and copilot_command overlap significantly since copilot_command can also run prompts, making it unclear which tool to use for a prompt task. The descriptions provide some clarity but do not fully resolve the boundary.
Both tool names follow a consistent 'copilot_<mode>' pattern with snake_case, which is predictable and easy to remember. The naming is uniform and well-aligned with the server's purpose.
With only 2 tools, the server is minimal but matches the narrow scope of wrapping the Copilot CLI. However, the presence of a general command makes the prompt-specific tool feel somewhat redundant, and the count is at the low end of reasonable.
The general copilot_command covers all CLI operations, avoiding dead ends, but the server lacks specialized tools for common Copilot workflows such as auth, session management, or structured prompt handling. The surface is functional yet sparse.