mcp-inspector
Skill188 starsChanged 8 months agoMITView on GitHub
MCP Protocol Inspection and Debugging with Inspector CLI
2 other projects use a version of this.
Adopted by
Most recently taken up by
- LeanMeanCleanApps/CleanModelContextProtocoltheir own version, first seen Nov 8, 2026
- MCPJam/inspectortheir own version, first seen Oct 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- MCPJam/inspector★ 2.3ksame name
- LeanMeanCleanApps/CleanModelContextProtocol★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .github/instructions/copilot-instructions.mdCopilot instructions
- dxt-packagingSkill
- mcp-developmentSkill
- mcp-refactoringSkill
- mcp-testingSkill
- publishingSkill
- raindrop-mcp-publishingSkill
- SKILL.mdSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Ensure you have Node.js and npx installed.
- Distinctive: line 21
Run the following command in your VS Code terminal:
- Distinctive: line 35
Use Inspector CLI to wrap your MCP server and inspect protocol traffic.
- Distinctive: line 50
Use Inspector CLI flags for advanced filtering, logging, and output formatting.
- Very specific: line 52
Use Vitest or your preferred test runner to automate CLI checks (see tests/inspector.test.ts for examples).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MCP Inspector Skill
Guidelines for using the MCP Inspector tool in CLI mode for protocol inspection, debugging, and tool listing in a VS Code environment.
Prerequisites
- Ensure you have Node.js and npx installed.
- Install MCP Inspector:
npx -y @modelcontextprotocol/inspector --help - Build your MCP server (e.g.,
bun run buildor equivalent).
Usage Examples
List Available Tools
Run the following command in your VS Code terminal:
npx -y @modelcontextprotocol/inspector --cli node build/index.js --method tools/listSend a Protocol Request (e.g., ping)
npx -y @modelcontextprotocol/inspector --cli node build/index.js --method pingDebugging and Inspection
- Use Inspector CLI to wrap your MCP server and inspect protocol traffic.
- Example for STDIO server:
npx -y @modelcontextprotocol/inspector node build/index.js- For HTTP server:
npx -y @modelcontextprotocol/inspector node build/server.jsTips
- Use Inspector CLI flags for advanced filtering, logging, and output formatting. See Inspector documentation for details.
- Integrate Inspector CLI commands into your VS Code tasks or launch configurations for automated inspection and debugging.
- Use Vitest or your preferred test runner to automate CLI checks (see
tests/inspector.test.tsfor examples).
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.