MCP Inspector v0.21.0: resource refresh button does nothing
In MCP Inspector v0.21.0 on Chrome/Windows 11, clicking the refresh button on the Resources tab after List Resources does not trigger another resources/read request. The bottom history shows no new read, the server receives nothing, and the displayed content stays stale. Is there a fix or workaround?
Originally asked on GitHub: https://github.com/modelcontextprotocol/inspector/issues/1120
3 answers
The issue is closed as completed in the tracker, but this thread does not name a fixing version. Reproduction in v0.21.0: connect to MCP, open the Resources tab, click List Resources, select a resource, then click the refresh button in the right panel. Expected result: another resources/read appears in the bottom history and reaches the server. Actual result: no request is sent, no history entry appears, and the previous content remains on screen.
One project member confirmed the same problem with regular resources, not only resource templates, and mentioned it happened with a relatively large resource. Another commenter reports that the issue seems to have started with v0.20.0 and that v0.19.0 appears to behave correctly; no one in the thread confirms downgrading as a tested workaround. A later comment suggested the UI should show cached content when you do not refresh, instead of keeping the previous resource's content, but that behavior was not implemented in this thread.
General advice: to verify whether the refresh button actually emits a request, watch the server-side logs or the browser network tab instead of relying only on the Inspector history panel. No security issue is mentioned in this thread.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Clicked the refresh button in the right panel after listing and selecting a resource. No resources/read request appeared in the bottom history, no request reached the server, and the previous content stayed on screen.
Source: https://github.com/modelcontextprotocol/inspector/issues/1120 (opens external site)
Did this work for you?What @spmallette tried on GitHub (Outcome unclear)
Observed that the problem seems to start with v0.20.0 and that v0.19.0 appears to work correctly, but did not confirm a downgrade as a fix.
Did this work for you?
Related questions
- MCP Inspector 0.10.2 sends null for unset optional params (error -32602)?
- Why does npx @modelcontextprotocol/inspector fail with 'mcp-inspector: command not found' after 0.10.0?
- How do I increase MCP Inspector's 10-second request timeout?
- MCP Inspector crashes with 'Controller is already closed' on fastmcp Streamable HTTP
- Why does the MCP Inspector Docker container refuse connections on localhost:6274, and how do I fix it?