> ## Documentation Index > Fetch the complete documentation index at: https://docs.alpic.ai/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Understand how your MCP server is used, out of the box. ### Overview Alpic Analytics gives you a complete picture of how your MCP server is used: how many sessions and users you have, which tools are called, how fast they respond, and where errors happen. There is nothing to install. Alpic sits in front of your MCP server and records every MCP request as it passes through: the method called, the MCP client, the response time, the outcome, and the user identity when one is available. Your code stays untouched and no SDK is required. Analytics are collected separately for each environment. The dashboard defaults to your production environment; use the environment picker to switch. ### Key indicators Analytics overview Analytics overview The top of the dashboard shows five key indicators for the selected period, each compared to the previous period of the same length: * **Sessions**: how many times your app was opened * **Tool calls**: how many `tools/call` requests users, agents and an LLM intentionally invoked * **Users**: how many distinct identified people used your server * **Sessions with errors**: how many sessions contained at least one error * **Session error rate**: the share of sessions that contained an error Every metric has a precise definition. See [Metric definitions](/analytics/metrics) for exactly what each one measures, and [How users are counted](/analytics/unique-users) for the full story on user identification. ### Sessions Sessions section Sessions section The sessions chart shows sessions over time, broken down per MCP client (ChatGPT, Claude, Cursor, and so on). Below it, a daily activity calendar shows when your app is used over the past year, switchable between request volume, latency, and errors, so you can spot usage patterns and growth at a glance. ### Users Users section Users section The users chart shows unique users over time, broken down per MCP client. When your server has identified users, a Top users card ranks the most active ones. ### Tools Tools section Tools section The tool performance table lists every tool with its request count, p50 and p95 latency, and success rate. Select one or more tools to focus the charts below on them: * **Requests** over time * **Latency** over time (p50, p95, p99) * **Tokens** per call Each chart can be scoped to tool calls only, to protocol requests only (tools/list, prompts/get, and resources/read; excluding 'initialize' requests), or to everything (including `initialize` requests). ### Reliability Reliability section Reliability section The reliability section tracks errors over time, split between tool errors and MCP errors, with breakdowns by tool and by error type. See [Metric definitions](/analytics/metrics#errors) for what each error type means. ### Time ranges and granularity You can view analytics over the last day, week, month, or year, or pick a custom date range. Chart granularity adjusts automatically to the range you select, from 5 minute buckets on short ranges up to daily buckets on long ones. How far back you can look depends on your plan's analytics retention, from 7 days on the Free plan to unlimited on Enterprise. Time ranges beyond your retention appear locked in the picker. See [Plans](/pricing/plans) for details. ### Go further Exactly what each metric measures Identity sources and unique user counting Control what data is collected