MCP Inspector and Official MCP Servers
- Launch MCP Inspector with npx and connect it to a local server to test tools, resources, and prompts interactively
- Use the Logs panel in Inspector to view raw JSON-RPC messages and diagnose tool failures
- Run the official filesystem and fetch MCP servers using npx without any global installation
- Verify all three sections of your notes server (tools, resources, prompts) pass inspection before connecting to Hermes 3
MCP Inspector
MCP Inspector is an official testing tool from the MCP team. It is a web UI that acts as an MCP client — it connects to any MCP server, lists its tools, resources, and prompts, and lets you call them manually and inspect the full JSON-RPC request and response. It is the fastest way to verify that a server works before wiring it to an LLM.
MCP Inspector runs via npx (no installation needed beyond Node.js):
npx @modelcontextprotocol/inspector python notes_server.py
This command launches the inspector and passes python notes_server.py as the command to spawn the server. Inspector starts the server as a child process, connects to it over stdio, and opens a browser window at http://localhost:5173 (or the next available port if 5173 is in use).
In the browser UI:
- The Tools tab lists all registered tools with their descriptions and schemas. Click a tool to open a form with input fields matching the schema. Fill in the fields and click Execute to call the tool and see the response.
- The Resources tab lists all registered resources. Click a resource to fetch its content.
- The Prompts tab lists registered prompt templates. Click one and fill in parameters to retrieve the rendered text.
- The Logs panel at the bottom shows the raw JSON-RPC messages — every request and response. This is what to check when something is not working as expected.
Test your notes server: run Inspector, navigate to Tools, call add_note with a title and content, then call list_notes to verify the note was saved. If anything fails, the Logs panel shows the exact error.
Common Inspector Issues
Port already in use: Inspector defaults to port 5173. If another process is using it, Inspector prints the alternative port in the terminal and opens the browser at that port.
Server crashes on startup: If the server exits immediately, the error appears in the terminal where you ran the npx command, not in the browser. Fix the Python error, then rerun Inspector.
Tool call returns nothing: An empty response usually means the tool function returned None. All tools should return a string — add a return statement or check for the missing branch.
Schema errors: If a type hint is not a standard JSON-serialisable type (a custom class, a file object), FastMCP cannot generate a valid schema. Use primitive types (str, int, bool, float) or standard Python containers (list, dict).
The Official MCP Server Library
The MCP organisation publishes a set of reference server implementations at github.com/modelcontextprotocol/servers. These are production-quality servers for common use cases: filesystem access, web fetching, GitHub, Brave Search, Postgres, Sqlite, and more. You do not need to build these yourself — they are available as npm packages you can run directly.
For the capstone in this track, you will connect your agent to two of them:
- @modelcontextprotocol/server-filesystem — exposes tools to read files, write files, list directories, and move files within a designated root directory. The root path is passed as a command-line argument so the server never accesses files outside it.
- @modelcontextprotocol/server-fetch — exposes a single
fetchtool that retrieves a URL and returns the page content as plain text (HTML stripped). Useful for giving the agent real-time web access without an API key.
Running the Filesystem Server
The filesystem server requires Node.js (or npx). No global install is needed:
npx -y @modelcontextprotocol/server-filesystem /path/to/workspace
Replace /path/to/workspace with the directory you want the agent to have access to. The server exposes tools including read_file, write_file, list_directory, create_directory, move_file, and search_files.
Test it with Inspector:
npx @modelcontextprotocol/inspector npx -y @modelcontextprotocol/server-filesystem ~/Desktop/workspace
In the Tools tab, call list_directory with path: "." to see the workspace contents. Call read_file with any file path to verify reading works.
Running the Fetch Server
npx -y @modelcontextprotocol/server-fetch
Test it with Inspector:
npx @modelcontextprotocol/inspector npx -y @modelcontextprotocol/server-fetch
Call the fetch tool with any URL. The server returns the page content as text. Note that some pages block automated requests — if a fetch returns a minimal response or a 403, that is the site blocking the request, not a server bug.
Connecting Inspector to Your Notes Server
Run Inspector against your completed notes server from Lessons 3 and 5:
npx @modelcontextprotocol/inspector python notes_server.py
Verify all three sections in the UI:
- Tools:
add_note,list_notes,get_note,clear_notes - Resources:
notes://schema,notes://{note_id}/content - Prompts:
research_summary_prompt
Add a few notes via the Inspector UI, list them, retrieve one by ID. Confirm the data is saved to notes.json in your working directory.
Once all three servers (notes, filesystem, fetch) pass their Inspector tests, they are ready to be wired to Hermes 3. The next two lessons cover running Hermes 3 and understanding its tool-calling format; Lesson 9 connects everything.
- MCP Inspector connects to any server over stdio — pass the server launch command as an argument to npx @modelcontextprotocol/inspector
- The Logs panel shows raw JSON-RPC request/response pairs — this is the first place to look when a tool call returns unexpected results
- The official MCP server library at github.com/modelcontextprotocol/servers provides production-ready filesystem, fetch, GitHub, and database servers you can run with npx — no code required
- The filesystem server accepts a root path argument and confines all file access to that directory — always pass a specific workspace path, never your home directory root
Progress is saved in this browser only — clear your cache or switch device and it's gone. Create a free account and it follows you everywhere.