mcp-github-copilot
by kud
README.md
<div align="center">




**MCP server for GitHub Copilot — query any Copilot model programmatically via the official SDK.**
<a href="https://kud.io/projects/mcp-github-copilot">Website</a> · <a href="https://kud.io/projects/mcp-github-copilot/docs">Documentation</a>
</div>
## Features
- **No extra API key** — uses your existing GitHub Copilot CLI credentials automatically.
- **Any model** — target GPT-5, Codex, Claude Sonnet, or any model your subscription grants.
- **File and image attachments** — attach local files or base64 blobs alongside a prompt.
- **Model discovery** — list available models with context window limits and billing multipliers.
- **Streaming progress** — sends MCP progress notifications for each streamed chunk.
## Install
```sh
npm install -g @kud/mcp-github-copilot
```
## Usage
Add the server to your MCP client configuration:
```json
{
"mcpServers": {
"mcp-github-copilot": {
"command": "mcp-github-copilot"
}
}
}
```
### Tools
| Tool | Description |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `query` | Send a prompt to a Copilot model and return the response. Accepts an optional `model` name and optional `attachments` (file paths or base64 blobs). |
| `list_models` | List all available Copilot models with capabilities, context window limits, and billing multipliers. |
## Development
```sh
git clone https://github.com/kud/mcp-github-copilot.git
cd mcp-github-copilot
npm install
npm run dev
```
📚 **Full documentation → [mcp-github-copilot/docs](https://kud.io/projects/mcp-github-copilot/docs)**
TDQS
A3.5/5.0
Scored across 2 tools
Disambiguation5/5
The two tools are completely distinct: one sends prompts to Copilot, the other lists available models. There is no overlap or ambiguity between them.
Naming Consistency2/5
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'.
Tool Count3/5
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.
Completeness3/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo issues