Repository navigation
[v2] Show tool count and per-tool call/log history in the web UI #2607
Description
Which client?
Web
The problem
There's no way to see how many tools a server exposes in the v2 web UI (tested on v2.9.0, Python FastMCP server over stdio with 15 tools).
Where I looked:
- Tools tab: the list header says only "Tools", with no count.
- Server card → Connection Info → Server Capabilities: shows "✓ Tools" but no count.
- Protocol panel →
tools/list→ Response: shows the fullresult.toolsarray, but you have to count the entries by hand.
Why it matters: some MCP clients cap the number of tools per server (for example, about 70 in Microsoft Copilot, as mentioned in #1171), so server authors need to check this quickly. Today the only reliable way is the CLI:
npx @modelcontextprotocol/inspector --cli <server cmd> --method tools/list | jq '.tools | length'
Steps to reproduce:
npx @modelcontextprotocol/inspector <any server with tools>- Connect, then open the Tools tab: no count is shown.
- Open Connection Info: Tools shows ✓ but no count.
#1171 asked for this on v1 and was closed because v1 is deprecated; the maintainer there asked for a fresh v2 issue.
Related gap: no per-tool call/log history
While testing the same server, I also couldn't see the call and log history for a single tool:
- Console tab (Server Console): stderr lines appear, but a tool call only shows
Processing request of type CallToolRequest. The tool name isn't shown, and the line isn't linked to the matchingtools/callentry in the Protocol panel. - Tools screen: after running a tool several times, there's no history of its previous calls, arguments, results or logs. Only the latest result is shown.
- Protocol panel: you can type a tool name in Search, but nothing groups a tool's calls together with the server logs and notifications it produced.
It would help to show, for each tool, its recent calls (arguments, result, duration) together with the log lines and notifications (notifications/message, progress) from each call.
Solution you have in mind (optional)
The v2 UX spec already describes this:
specification/v2_ux_features.md: the Tools screen wireframe heading reads "Tools (4)".specification/v2_ux_interfaces.md:CapabilityItemhas acount?: numberprop, described as the length of the corresponding list result.specification/v2_ux.md: Server Info should "show both server and client capabilities with counts".
So it would be: show Tools (N) / Prompts (N) / Resources (N) in the list headers, and a count next to each capability in Connection Info.
Alternatives or workarounds you have tried
- CLI:
--method tools/listpiped tojq '.tools | length'works, but it's outside the UI. - Copying the
tools/listresponse from the Protocol panel and counting withjqworks, but it's manual. - Counting the entries in the Tools list by eye.
Already built it locally?
No response
Before you submit
- I searched existing issues and this is not a duplicate.
- This is a request for the Inspector itself, not for the MCP specification or an SDK.
Activity
cliffhall commentedon Oct 12, 2026
Triage: Priority Low (total 4)
jqis a workaroundBoard: #28, Status
Incoming(awaiting maintainer review — no milestone yet).fix(web): withhold list counts until the first load completes (#2607)
cliffhall commentedon Oct 12, 2026
Shipped in #2708.