2026-09-22 • Updated 2026-09-26 • 7 min read • Measure
How to Measure Which Documentation an AI Agent Actually Uses
Learn to compare the pages your MCP server cited with the pages you expected, using MCP Studio's free Breakdown and the passage view in Action analytics.
To measure which documentation an AI agent actually uses, read what your MCP server returned rather than your site traffic. In Context MCP Studio, the free Breakdown shows which source and client handled each request, and Action analytics shows the exact page, section, and excerpt the agent was given. Lay that list beside the pages you expected, then keep, fix, or disconnect what does not match.
By the end you will know which pages your agent relies on, which source it reaches for that you did not plan on, and what to do about each.
Why site traffic cannot answer this
An agent reads your docs without opening a browser. When Claude or Cursor asks your MCP server a question, the server returns passages directly. No page view is recorded, so your site analytics can show a page as almost unvisited while the agent cites it every day.
The surprise is usually a source you forgot. Say you connected a help center and a launch blog. You believe the agent answers refund questions from the help center, and it mostly does. It also cites the launch blog, which still describes a feature flag you have since removed from the product. That blog might have almost no human readers. The agent retrieved it anyway.
What each level of analytics shows
MCP Studio records the same details on every request, whatever your plan. The plan decides which views you can open.
Free: KPI cards, Calls Over Time, and Breakdown. The Breakdown shows which source was consulted, which tool ran, and which client made the call. A source that never appears is not being used, even if you added it. Label your own test traffic so a script you forgot was running does not become your top user.
Core, $49 a month: the request log. It adds the question text, so you can see which question pulled which source.
Core plus Action, $99 a month: the page. The Action tab shows the page, section, and excerpt returned for each request, plus which pages are used most. That is the documentation the agent was actually given.
Core plus Action plus Predictive, $149 a month: a grade per source. Each source gets an A to D grade based on how many requests it takes to reach a working answer. Use the grade to choose what to open first, and read the page before treating the letter as a verdict.
New accounts get a 30-day trial with all three paid tiers unlocked. The full comparison is in What the questions people ask your docs can tell you.
How to read it in MCP Studio
MCP Studio is the no-code builder on Appa Tools. Open the server on the dashboard. A server nobody has called has nothing to measure, so give it real traffic first. The view names are in the dashboard guide.
- Read the Breakdown by source, tool, and client. Mark your own test traffic.
- List the pages cited on the Action tab for the questions you care about, and compare that list with the pages you intended.
- Ask by hand when an expected page never appears. If a different page is cited, the heading or a retrieval rule is the next edit. A rule is how you tell the server to prefer the page you meant.
- Decide on each stale source. Disconnect it, or keep it on purpose. Disconnecting deletes the indexed copy of that source and leaves the others untouched.
How to check that it works
In the example, the Breakdown shows almost all calls on the help center. The Action tab shows the refunds article cited whenever someone asks about a refund, and the launch blog cited once, for the removed flag.
That tells you two things. The refunds article is the page to review whenever refund policy changes, because it is the one the agent hands out. The launch blog is the one to disconnect, or to keep knowing it will answer questions about an old flag. Ask the flag question again after your change and confirm the citation moved.
Questions that cite nothing are the other half of this measurement. When nothing in your content matches, the server says so rather than offering the nearest page, which gives you a clean list of what is missing. Those are documentation gaps.
What usage does and does not tell you
Cited often is not the same as correct. A source can appear on every call and still return the wrong paragraph. Open the passage. That check is Measure MCP retrieval quality.
One afternoon is a sample. A week of the same top page is a pattern. Recheck after the next batch of real requests, not after a single test from your laptop.
A page with no citations is not automatically useless. If related questions are being asked and the page never appears, it is not reaching the agent, and its heading needs work. If nobody asked, the silence says nothing about the page.
If the top page is a surprise
Do not remove it because it was not in the plan. Read the passage. If it is the right answer, the plan was wrong and the page deserves the same care as your favorites. If it is stale, disconnect that source and ask the question again.
Frequently asked questions
How can I tell which documentation an AI agent used?
Look at what your MCP server returned, not at your website analytics. Each reply that used the server cites the page its passage came from. In MCP Studio, the free Breakdown shows which source handled each request, and Action analytics shows the exact page, section, and excerpt.
Why do page views not show AI agent usage?
An AI agent reads your content through the MCP server, which returns passages directly without loading the page in a browser. No page view is recorded, so a page can look unvisited in site analytics while the agent cites it every day.
Does a page that is cited often mean it is correct?
No. Frequent citation means the agent relies on that page, which makes it important to keep accurate. Open the passage and check the fact, because a popular page can still carry an outdated sentence.
Which MCP Studio plan shows the exact passage an agent received?
The Action tab, included with Core plus Action analytics at $99 a month, shows the page, section, and excerpt for each request. The free dashboard shows which source, tool, and client handled each call. New accounts get a 30-day trial with every tier unlocked.
What should I do with a stale source the agent keeps citing?
Disconnect it if it should not answer questions, or add a retrieval rule that prefers your current source for that topic. Disconnecting deletes only the indexed copy of that source. Ask the same question afterward to confirm the citation moved.
See which pages your agent uses with MCP Studio
Open your server, read the source Breakdown, and on the Action tab compare one cited page with the page you expected. Keep the source that matches your current policy and disconnect the one that does not. Open the MCP Studio dashboard.