copilot-status-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for monthly quota support (fallback if GITHUB_COPILOT_TOKEN not set) | |
| GITHUB_COPILOT_TOKEN | No | Copilot-issued OAuth token for full rate-limit support |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_copilot_statusA | Retrieve GitHub Copilot quota and rate-limit status: whether the 5-hour session window is exhausted and when it resets, weekly window usage, and monthly quota for chat, completions, and premium 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 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly and uniquely defined.
The tool name follows a standard verb_noun pattern, is descriptive, and is internally consistent despite being the only tool.
A single tool feels thin for a server, but it could be justified if the entire purpose is status retrieval. However, it falls at the borderline of the typical 3-15 tool range.
The tool comprehensively covers the domain of Copilot status, including session window, weekly usage, monthly quota, and premium models. No obvious gaps exist for its stated purpose.