Skip to main content
You can track MCP server usage using metrics exposed by the API gateway. The Lucidworks team provides a ready-made Grafana dashboard to visualize MCP request volume, latency, and error rates.
New to Lucidworks MCP? See the MCP Server overview for setup instructions and configuration details.

​
How MCP usage is measured

All MCP traffic enters Lucidworks Search through the API gateway at the /mcp route. The gateway records a per-route latency histogram, gateway_request_time_secs, on every request. The label routeId="mcp-server" isolates MCP traffic from all other gateway routes, providing a clean MCP-only view without touching the MCP server itself. The histogram carries these labels: The histogram exposes three series families:
  • gateway_request_time_secs_count — total number of requests
  • gateway_request_time_secs_sum — sum of all request durations in seconds
  • gateway_request_time_secs_bucket — histogram buckets that power the latency percentiles

​
Dashboard overview

The Lucidworks team configures Grafana dashboards for your Lucidworks Search environment. Contact your Lucidworks representative for dashboard access and customization options. The MCP monitoring dashboard includes panels organized into three sections: overview metrics, latency analysis, and traffic breakdown.
Imported Grafana dashboard showing MCP server usage metrics

​
Overview metrics

​
Latency metrics

​
Traffic metrics and errors

​
Notes

  • This dashboard measures MCP usage at the gateway, which is the cleanest signal for request volume, status, and latency. It does not break usage down per MCP tool (such as Search_documents, Get_document) — that would require additional instrumentation in the MCP server.
  • The same metric (spring_cloud_gateway_requests_seconds) is also emitted by the gateway as a Micrometer summary; the dashboard uses the gateway_request_time_secs histogram because it supports latency percentiles.