Skip to main content
Analytics provides an overview of your server’s usage and performance, helping you understand how AI clients interact with your MCP capabilities over time. Use Analytics to identify trends, monitor reliability, and quickly spot potential issues.

​
What you can monitor

Analytics includes metrics such as:
  • Total MCP requests
  • Calls by tool, resource, or prompt
  • Successful and failed requests
  • Response time
  • Request and response size
  • MCP client usage
Use filters such as date range and capability to focus on specific activity.

​
Understanding your metrics

Analytics can help you identify common issues:
  • An increase in 401 or 403 responses may indicate expired or invalid credentials.
  • More failed requests could suggest upstream API changes, invalid inputs, or disabled capabilities.
  • Higher response times often point to slower upstream APIs or larger responses.
  • Changes in usage can help you understand how clients are interacting with your server.
For help with credential failures, see Authentication errors. For request-specific investigation, use Logs.

​
Privacy

Analytics is designed to measure usage, not capture your data. 0mcp records operational metrics needed to monitor your MCP server, such as request counts, response times, and status codes. It does not require API credentials or full request and response payloads to generate analytics. This helps you monitor performance while keeping your application data private.
Analytics stores operational measurements, not your API credentials, request bodies, or response bodies.

​
When to use Analytics vs. Logs

Use Analytics to understand overall trends and server health. Use Logs when you need to investigate a specific request, error, or capability in more detail.