[FEATURE] Expose plugin install metrics to marketplace plugin authors

Resolved 💬 4 comments Opened Mar 9, 2026 by dacharyc Closed Apr 6, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Plugin authors who publish to the official Anthropic marketplace (claude-plugins-official) have no way to see how many users have installed their plugins. The /plugin Discover tab displays install counts to end users, so this data exists server-side, but it isn't exposed to authors through any API, dashboard, or other mechanism I could discover.

This makes it difficult for plugin authors to:

  • Understand adoption and prioritize maintenance efforts
  • Justify continued investment in plugin development to their organizations
  • Measure the impact of updates or new features

Proposed Solution

Expose plugin install metrics to verified plugin authors. This could take several forms (in rough order of simplicity):

  1. Console dashboard — A page at console.anthropic.com or platform.claude.com showing install counts for plugins you've submitted, similar to npm download stats or VS Code extension metrics
  2. API endpoint — A programmatic way to query install/active-user counts for plugins you own
  3. Periodic reports — Email or webhook notifications with install trends

Even just total install counts visible to the submitting author would be a meaningful starting point.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

_No response_

Additional Context

We're developing an official plugin for our enterprise, which we'll distribute through the Anthropic marketplace. We can see that the /plugin UI shows install counts next to listed plugins, but we have no way to access this data for our own plugins — either in aggregate or over time.

This was previously requested in #15972, which was auto-closed due to inactivity. Filing a new issue as suggested since that one is now locked.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗