copilot-usage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_DIR | No | Cache directory (default: ./cache) | ./cache |
| GITHUB_ORG | No | Organization name | |
| GITHUB_TOKEN | Yes | GitHub Personal Access Token | |
| GITHUB_ENTERPRISE | No | Enterprise slug |
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 |
|---|---|
| get_copilot_metrics_for_enterpriseA | Get daily Copilot usage metrics for the entire GitHub Enterprise (code completions, chat usage, active users, language/editor breakdown) |
| get_copilot_metrics_for_orgA | Get daily Copilot usage metrics for a GitHub Organization (code completions, chat usage, active users, language/editor breakdown) |
| get_copilot_metrics_for_teamC | Get daily Copilot usage metrics for a specific team within an Organization |
| get_copilot_seat_assignmentsC | Get Copilot seat assignments for an Organization (user list with last activity date, editor info, plan type) |
| get_copilot_usage_summaryA | Get a combined summary of Copilot usage across Enterprise, Organization, and seat assignments. Optionally include team-level metrics. |
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 5 tools
Each tool has a clearly distinct purpose targeting different aspects of Copilot usage data. The enterprise, organization, team, seat assignments, and summary tools all operate at different scopes with no functional overlap, making tool selection unambiguous.
All tools follow a perfect 'get_copilot_[noun]_[preposition]_[target]' pattern with consistent snake_case throughout. The naming convention is highly predictable and readable across all five tools.
Five tools is an ideal number for this focused domain of Copilot usage analytics. Each tool serves a distinct reporting function without redundancy, providing comprehensive coverage while maintaining a manageable interface.
The toolset provides complete coverage for Copilot usage reporting across all relevant scopes (enterprise, organization, team, seat assignments) with a convenient summary tool. There are no obvious gaps in the analytics surface for this specific domain.