Custom skills, agents, and MCP servers in usage metrics API

GitHub's Copilot usage metrics API now reports the configured names of customer-defined skills, custom agents, Model Context Protocol (MCP) servers, slash commands and plugins instead of grouping them under `other` or `custom`, the company said in a changelog entry. Each `totals_by_*` array now holds up to 25 entries per record, up from five, with remaining activity combined into a trailing `other` entry, while `interaction_count` and the `distinct_*_use_count` fields are calculated as before. Names are collected from Copilot CLI, the GitHub Copilot app, Agent Client Protocol integrations such as JetBrains and the Copilot SDK, requiring Copilot CLI 1.0.97 or later or Copilot SDK v1.0.21 or later, and appear only in report days processed after the release.

Improvement Custom skills, agents, and MCP servers in usage metrics API Copilot usage metrics now show the names of the skills, custom agents, Model Context Protocol MCP servers, slash commands, and plugins that your organization creates, instead of grouping them under other or custom . This builds on the agentic CLI customization metrics https://github.blog/changelog/2026-09-17-agentic-cli-customizations-now-in-the-usage-metrics-api/ released in September. What’s new whats-new - Named entries: In enterprise and organization reports, including per-user 1-day and 28-day reports, aggregated 1-day reports, and day totals in aggregated 28-day reports, the totals by skill , totals by custom agent , totals by mcp , totals by slash cmd , and totals by plugin arrays now show the configured name of a customer-defined item instead of other or custom . - More entries: Each totals by list now includes up to 25 entries per record, up from five, so you can see more of the long tail of customizations your developers use. Any remaining activity is combined into a trailing other entry. - Unchanged counts: interaction count and the distinct use count fields are calculated the same way as before. Why this matters why-this-matters The customizations that matter most to an organization are often the ones its own teams build. Administrators can now see which internal skills, custom agents, and MCP servers developers actually use, track adoption after rolling out a new one, and focus enablement where it is needed. Important notes important-notes - Coverage: Names are reported from Copilot CLI interactive sessions and prompt mode , the GitHub Copilot app, Agent Client Protocol ACP integrations such as JetBrains, and the Copilot SDK. Prompt mode, the app, and ACP integrations require Copilot CLI 1.0.97 or later. The Copilot SDK requires v1.0.21 or later. IDEs report names when their agent experiences run on the Copilot SDK v1.0.21 or later. Names aren’t reported from an IDE’s built-in chat telemetry. - Configured names: Names are reported as they are configured, trimmed and limited to 128 characters. Names that look like file paths stay grouped under other or custom . Review names before sharing reports outside your organization. - Accuracy: These metrics come from client telemetry and can undercount activity, for example when clients are outdated or telemetry is blocked. Use them to understand trends and adoption rather than for exact accounting. - History: Names appear starting with report days processed after this release. Earlier days still show other or custom . - Access: Reports are available to enterprise owners and billing managers, organization owners, and anyone with a custom organization or enterprise role that grants the “View Copilot Metrics” permission. The Copilot usage metrics policy must be enabled. Visit the Copilot usage metrics API documentation https://docs.github.com/rest/copilot/copilot-usage-metrics to get started.