MCP server: Add usage metrics #711
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
Instrument every MCP tool with the new
shared.TrackToolExecutionhelper so each handler automatically emitstools.<tool_name>.count_*andduration_msmetrics, marking success viatracker.MarkSuccess()just before returning.Tag metrics with human-readable organization names by introducing a cached org-name resolver (pkg/tools/internal/shared/org_resolver.go) wired through
tools.ConfigureMetrics(provider)(called once during server bootstrap) and backed by the organization gRPC client + stub support.Document the workflow in
AGENTS.mdso future tools follow the same pattern, and add targeted unit tests for both the metrics helper and resolver caching logic.✅ Checklist
This change requires documentation update