MCP server analytics Your server is live. What are people doing with it?

MCP server analytics shows who uses your server, which AI clients they use, and whether they come back. Flowlines connects tool calls to users, clients, sessions and use cases, and turns that activity into product and business signals: adoption, buying intent, unmet needs and recurring issues, with notifications for the team that needs to act.

100 analyzed MCP sessions per month, free. No credit card. Connect your assistant, then instrument your server.

From server activity to a product decision.

Explore the overview, users and use cases of an example customer-operations server.

SessionsPer client · last 14 days

0sessions

By client · sessions

Claude3,06942%
ChatGPT2,24731%
Claude Code1,20316%
Cursor83211%
UsersKnown people, by activity
UserClientSessionsTool callsIssuesLast activity
MRMaya R.NorthstarClaude149602 min ago
PNPriya N.StudioClaude381,28418 min ago
MDMarc D.ParcelChatGPT2196201 h ago
AKAiko K.FieldworkCCursor1773123 h ago
JBJonas B.OrbitClaude Code125060Yesterday
Synthetic data · interactive product example

What is MCP server analytics?

MCP server analytics measures who uses a Model Context Protocol server, from which AI clients, for which jobs, and whether they come back. Flowlines provides it for teams that ship an MCP server, with users, clients, tools, sessions and returning users in one place.

Infrastructure monitoring tells you whether the service is available. Tool-call telemetry tells you which operation ran and whether it failed. Server analytics adds people, clients, sessions and repeat usage, so you can tell adoption from a busy test script.

Analytics for MCP servers or an analytics MCP server?

Analytics for MCP servers measures how people use an MCP server you ship, and Flowlines is analytics for MCP servers; an analytics MCP server is something else, an MCP server that lets an AI assistant query an analytics product.

If you ship an MCP server and want to know who uses it, which clients call it and what fails, you need analytics for MCP servers. If you want your assistant to answer questions such as last week's signups from your product analytics, you need that product's MCP server. Flowlines does both for its own data: it measures your MCP server, and its own MCP server lets your assistant ask questions about those measurements.

Analytics for MCP servers or an analytics MCP server?
QuestionAnalytics for MCP serversAnalytics MCP server
What it measuresYour MCP server's users, clients, tools and sessions.Whatever the analytics product behind it already tracks.
Who uses itThe team that builds and ships the MCP server.Anyone who wants an assistant to read their analytics.
Example questionHow many users came back to my server this week?How many signups did we get last week?

Is anyone using my MCP server?

Flowlines shows how many distinct people call your MCP server, how many sessions they run and which tools they use, so you can tell real adoption from a test script.

Count users, sessions and tool calls for a fixed window, and exclude internal and test traffic. One script can generate hundreds of calls, while ten people with two sessions each is real adoption. Keep calls without a known user visible as their own group.

Is anyone using my MCP server?
CountWhat it tells youRead it with
Distinct usersHow many people or accounts called the server.Identity coverage; shared accounts are not individual people.
SessionsHow many separate jobs were attempted.Whether sessions come from your integration or are inferred.
Tool callsHow much work the server did.Users and sessions; retries and pagination inflate it.
Internal trafficActivity from your own team and tests.Exclude it before reporting adoption.

How many users come back?

Flowlines shows how many users come back to your MCP server in each period, and which AI client they use.

A returning MCP user is someone active in the selected window who was also active in an earlier one; returning users divided by active users gives the returning share. A first call can be curiosity. A second week of activity usually means the server became part of someone's workflow.

How many users come back?
MeasureDefinitionExample (synthetic)
Active usersUsers with at least one call in the window.24 users in the last 7 days.
New usersActive users with no earlier activity.User 036, 4 sessions.
Returning usersActive users who were also active before the window.User 014, 18 sessions; User 028, 12 sessions.
Returning shareReturning users divided by active users.Report it with identity coverage and the window used.

Which AI clients call my server?

Flowlines groups your MCP server's calls by AI client, such as Claude, ChatGPT or Cursor, and keeps calls without a client name in an unknown group.

Client names are reported by the calling application. They tell you where usage comes from, not who the person is. Different clients can attempt different jobs, so compare similar use cases before concluding that one client works better with your tools.

Which AI clients call my server?
Client viewUseful forCaveat
Calls and users by clientSeeing where adoption comes from.A client is an application, not an end user.
Tools by clientSpotting a tool one client never reaches.Check discovery and permissions before blaming the tool.
Errors by clientFinding client-specific breakage.Compare the same job; mixes of work differ.
Unknown clientMeasuring missing metadata.Keep it visible instead of dropping it.

Measure the business behind the tool calls.

Your MCP is a product surface. Measure whether users return, what they need and when they show commercial interest. Flowlines connects these business KPIs to the sessions behind them, so a sales, product or customer team can act on more than a traffic chart.

Use a defined window and the right denominator. Buying-intent incidence is the share of sessions evaluated for buying intent that contain it, not a sales conversion rate. Product-need incidence uses sessions evaluated for product needs. Missing context stays outside the evaluated population, not silently counted as a negative.

Measure the business behind the tool calls.
Business questionMeasureNext action
Are people finding repeat value?Active users and repeat usage, with identity coverageInspect the workflows returning users rely on.
Who is evaluating the product?Sessions with buying intent and buying-intent incidenceReview the account context and notify the commercial team.
What should we build next?Product needs and the sessions they affectGroup unmet requests and inspect the examples before prioritizing.
Where does the experience break?Evaluated outcomes and recurring issuesFind affected users and open the relevant sessions.

Get the signal while you can still act.

Configure notifications for buying intent, product needs and custom behavior signals. Route findings to Slack, email or a webhook. A user asking about enterprise deployment can matter just as much as a repeated tool failure.

Choose real-time delivery after analysis, or daily and weekly digests. Real-time is not an inline tool-call guard or a fixed latency guarantee: delivery follows analysis, and product-need grouping can add delay. Repeated findings are suppressed until they reopen, worsen or buying intent advances.

KPI analytics and finding alerts are different capabilities. These notifications do not promise arbitrary thresholds on external revenue, billing or CRM data. Configure a behavior your captured sessions can establish, then verify that a synthetic matching session reaches the intended destination.

More calls. More value? Not necessarily.

A rise in MCP traffic can mean new adoption, more work from existing users, or more attempts to finish the same job. The useful next step is to break the increase down by user, tool, client and session.

Suppose a customer-brief workflow moves from three calls to nine. If the same users repeat a search and cannot finish, the extra traffic is friction, not growth. If new teams run more completed briefs, it may be useful adoption. Inspect representative sessions before choosing an explanation.

Product

Find recurring requests and the tools people actually reach for before prioritizing the next capability.

Engineering

Follow a failing path from the affected session to the calls behind it, rather than starting with a global error count.

Customer teams

Filter users by tool or client to see who returns and who repeatedly encounters issues.

How Flowlines connects the pieces.

Instrument the MCP server with compatible OpenTelemetry telemetry. Flowlines organizes the observed calls by server, tool and available identity, then connects them into sessions where the context supports it.

The server overview brings together tool usage, clients, users, sessions and use cases. From there, open a tool to see what people use it for, or a session to follow the sequence and how it ended. Period comparisons help you investigate changes; they do not prove a release caused them.

A server does not automatically receive the assistant's complete conversation or final answer. What you can analyze depends on what the integration sends. Inferred sessions stay labeled as inferred.

Connect your assistant. Instrument your MCP.

The Flowlines plugin gives your assistant the setup workflow. Connecting the assistant does not automatically instrument your MCP server.

  1. Connect FlowlinesUse the button to open the supported setup path in your assistant.
  2. Instrument the serverUse the plugin's MCP observability workflow. Review what will be captured before sending production data.
  3. Verify the first callsCheck tools, identity and session coverage. Add outcome context where supported and keep missing data visible.

MCP server analytics: common questions

Is anyone using my MCP server?

Flowlines shows how many distinct people call your MCP server, how many sessions they run and which tools they use. Exclude your own team's traffic: call volume alone can come from one script.

How many users come back to my MCP server?

Flowlines shows how many users return in each period. The returning share is users active in the window who were also active earlier, divided by all active users, read with identity coverage.

Which AI clients call my MCP server?

Flowlines groups calls by AI client, such as Claude, ChatGPT or Cursor, and keeps an unknown group. Client names are reported by the calling application and identify the application, not the person.

Is Flowlines an analytics MCP server?

Flowlines is analytics for MCP servers: it measures who uses the MCP server you ship. It also has its own MCP server, so your assistant can ask questions about those measurements.

Can I track business KPIs for an MCP server?

Yes. Flowlines supports adoption analysis, evaluated outcomes, buying-intent incidence and product needs. Read each rate with its evaluated population and inspect the sessions behind it. Purchase intent is not booked revenue, and a tool returning successfully is not proof of a completed business outcome.

Does Flowlines offer real-time MCP alerts?

Flowlines supports real-time notification delivery after analysis, plus daily and weekly digests. Configure buying-intent, product-need or behavior-signal rules with Slack, email or webhook destinations. Timing depends on analysis and grouping, not a guaranteed per-call delivery deadline.

Can I use my existing OpenTelemetry setup?

Yes, if it emits the compatible MCP telemetry Flowlines needs. The Flowlines plugin can guide the instrumentation and verification. Installing the plugin alone does not instrument a server.

Start with the traffic you already have

See the work behind the calls.

Connect Flowlines and take the next step with your assistant.