Skip to content

Conversation

michalismeng
Copy link

What's changed

Introduce the 'inspector' command, which starts the MCP inspector tool. Internally it launches the inspector with npx @modelcontextprotocol/inspector and passes any addition arguments the user gives.

Closes #51

(See the issue for some more details)


Screenshot from 2025-08-26 10-55-01

Notes

The issue mentions the following in the desired solution:

Warn the user that they need the relevant binaries on their machine when they enter a command in the UI

Currently, mcpd inspector prints to the terminal whatever the underlying npx process prints, so there will be dev-style details of the error:

New STDIO connection request
Query parameters: {"command":"uvx","args":"mcp-server-time@latest", ....

and in the UI we get a message from the inspector itself, for example:

error: Could not find the `uv` binary at either of: ...

Not sure if this is enough, glad to discuss if more is needed here.

Introduce the 'inspector' command, which starts the MCP inspector tool
via an npx process for interaction with 'try me out' style MCP servers.

Also, add a note to the docs.
@peteski22 peteski22 self-requested a review August 27, 2025 15:05
@peteski22 peteski22 self-assigned this Aug 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support inspector style command
2 participants