GitHub Copilot Usage MCP Server
Related Servers
Alternatives to GitHub Copilot Usage MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that retrieves GitHub Copilot usage metrics and seat assignment data across Enterprise, Organization, and Team levels. It allows users to monitor code completions, chat activity, and active user counts through integrated tools.55 npmMIT
- AlicenseAqualityCmaintenanceMCP server to check GitHub Copilot quota, rate-limit status, and reset times from any MCP client.110 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes GitHub Copilot premium request usage as an MCP tool, providing a breakdown by model and cost.MIT
- FlicenseAqualityBmaintenanceMCP server that exposes a single tool to retrieve ChatGPT/Codex quota via the signed-in Codex CLI, reporting rate-limit windows and usage percentages.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.494 npmISC
- AlicenseAqualityCmaintenanceA lightweight MCP server that enables fetching public GitHub user profiles, repository stats, recent events, and pull request insights through simple tool calls.2140 npm1MIT
TDQS
Scored across 3 tools
The three tools all retrieve GitHub Copilot usage data, but each targets a different output format (raw, human-readable, summary). While distinct, an agent might still be uncertain which to use for a given task, though descriptions clarify the differences.
All tool names follow a consistent 'get_copilot_usage' prefix with suffixes that clearly indicate the output type (empty, _formatted, _summary). This pattern is predictable and easy to understand.
With exactly 3 tools, the count is well-scoped for a focused server that provides usage information in three formats. It covers the necessary variations without being excessive or insufficient.
The surface covers the primary use case of retrieving Copilot usage data, offering different formats. Minor gaps exist, such as the absence of historical data or team-specific queries, but these are not essential for the stated purpose.