Movatterモバイル変換

[0]ホーム
URL:

Skip to main content
Developer tools

MCP Inspector

In-depth guide to using the MCP Inspector for testing and debugging Model Context Protocol servers

TheMCP Inspector is an interactive developer tool for testing and debugging MCP servers. While theDebugging Guide covers the Inspector as part of the overall debugging toolkit, this document provides a detailed exploration of the Inspector’s features and capabilities.

Getting started

Installation and basic usage

The Inspector runs directly throughnpx without requiring installation:
npx @modelcontextprotocol/inspector <command>
npx @modelcontextprotocol/inspector <command> <arg1> <arg2>

Inspecting servers from npm or PyPI

A common way to start server packages fromnpm orPyPI.
  • npm package
  • PyPI package
npx -y @modelcontextprotocol/inspector npx <package-name> <args># For examplenpx -y @modelcontextprotocol/inspector npx @modelcontextprotocol/server-filesystem /Users/username/Desktop
npx @modelcontextprotocol/inspector uvx <package-name> <args># For examplenpx @modelcontextprotocol/inspector uvx mcp-server-git --repository ~/code/mcp/servers.git

Inspecting locally developed servers

To inspect servers locally developed or downloaded as a repository, the most commonway is:
  • TypeScript
  • Python
npx @modelcontextprotocol/inspector node path/to/server/index.js args...
npx @modelcontextprotocol/inspector \  uv \  --directory path/to/server \  run \  package-name \  args...
Please carefully read any attached README for the most accurate instructions.

Feature overview

The MCP Inspector interface

The Inspector provides several features for interacting with your MCP server:

Server connection pane

  • Allows selecting thetransport for connecting to the server
  • For local servers, supports customizing the command-line arguments and environment

Resources tab

  • Lists all available resources
  • Shows resource metadata (MIME types, descriptions)
  • Allows resource content inspection
  • Supports subscription testing

Prompts tab

  • Displays available prompt templates
  • Shows prompt arguments and descriptions
  • Enables prompt testing with custom arguments
  • Previews generated messages

Tools tab

  • Lists available tools
  • Shows tool schemas and descriptions
  • Enables tool testing with custom inputs
  • Displays tool execution results

Notifications pane

  • Presents all logs recorded from the server
  • Shows notifications received from the server

Best practices

Development workflow

  1. Start Development
    • Launch Inspector with your server
    • Verify basic connectivity
    • Check capability negotiation
  2. Iterative testing
    • Make server changes
    • Rebuild the server
    • Reconnect the Inspector
    • Test affected features
    • Monitor messages
  3. Test edge cases
    • Invalid inputs
    • Missing prompt arguments
    • Concurrent operations
    • Verify error handling and error responses

Next steps

Was this page helpful?

⌘I
[8]ページ先頭
©2009-2025 Movatter.jp