- Count distinct clients per tool, not just calls.
- Track week-over-week trend to see where the product is heading.
- Read adoption inside workflows, not in isolation.
Call count alone can mislead. A tool called constantly by one flaky client is not the same as a tool adopted across your whole client base. To understand adoption, look at breadth, trend, and context.
Breadth
Count distinct clients using each tool, not just calls. A tool used by every client is core; a tool used by one is niche, however loud its volume.
Trend
Track week-over-week change. Tools gaining adoption tell you where the product is heading. Tools losing it early warn you before the drop shows up in totals.
Context
Adoption lives inside workflows. A tool that is only ever the first step in a path that never completes is not really adopted; it is a dead end. Read tool usage alongside completion, not on its own.
Put together, these turn a flat list of counts into a map of what your server is actually for.
See this on your own server
TrackMCP turns your MCP server's calls into adoption, workflows, and outcomes. One line to install.