{
  "$type": "site.standard.document",
  "canonicalUrl": "https://unnecessary.tech/posts/mcp-inspector",
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiapssyuwzcr2px44bfh3evllh3pjyrrxvsn4lsaswrghmqziu4ahi"
    },
    "mimeType": "image/png",
    "size": 127060
  },
  "path": "/posts/mcp-inspector",
  "publishedAt": "2025-08-11T17:57:34.000Z",
  "site": "at://did:plc:jx54v4rmscfwzit7fmgz24ba/site.standard.publication/3mnrsqmzz3w2e",
  "tags": [
    "ai",
    "programming"
  ],
  "textContent": "In yesterday's post I wrote about how I\nthought Model Context Protocol (MCP) was one of the most interesting aspects\nof the current AI hype. I'm going to start writing about an MCP server that I\nam building, but before I start that I thought I would talk about a tool which\nis a great help in building and testing MCP servers, and that tool is MCP\nInspector.\n\n{{< image src=\"/img/mcp-inspector.png\" alt=\"An image of the user interface for the MCP Inspector tool.\" >}}\n\nMCP Inspector will act as a client for your MCP server, similar to Postman or\nthe Swagger UI, the MCP Inspector lets you connect to your MCP server, examing\nand validate it's output, and use the various tools the server exposes. For\nMCP servers that run as subprocesses listening over stdin, MCP Inspector will\neven run the subprocess for you.\n\nMCP Inspector is also up to date with the latest MCP features as it is an open\nsource project run by Anthropic, who were the originators of the MCP specification.\nTo run MCP Inspector you need to do the following:\n\n1. Install node. (On my Mac I used homebrew to install node\n   with the command brew install node.)\n2. Download and run MCP Inspector with the command npx @modelcontextprotocol/inspector.\n\nThat's it. Now you can start testing MCP servers with impunity.",
  "title": "MCP Server Programming: Inspector"
}