| layout | default |
|---|---|
| title | MCP Inspector Tutorial |
| nav_order | 160 |
| has_children | true |
| format_version | v2 |
Learn how to use
modelcontextprotocol/inspectorto test MCP servers across stdio, SSE, and streamable HTTP, with safer auth defaults and repeatable CLI automation.
MCP Inspector is the primary developer surface for validating MCP server behavior before rolling changes into production clients. It combines an interactive web UI with a CLI mode so teams can run both exploratory and automated checks.
This track focuses on:
- establishing a reliable first-run setup for local and remote MCP servers
- understanding proxy and transport behavior to avoid false debugging signals
- using CLI mode in automation loops for regression checks
- hardening auth, local binding, and origin controls when running the proxy
- repository:
modelcontextprotocol/inspector - stars: about 9.3k
- latest release:
0.21.1(published 2026-02-27)
flowchart LR
A[Server under test] --> B[MCP Proxy]
B --> C[Inspector UI]
B --> D[Inspector CLI]
C --> E[Interactive debugging]
D --> F[Scripted validation]
| Chapter | Key Question | Outcome |
|---|---|---|
| 01 - Getting Started | How do I run Inspector quickly and verify connectivity? | Working baseline |
| 02 - Architecture, Transports, and Session Model | How do proxy, client, and transport layers interact? | Clear debugging model |
| 03 - UI Debugging Workflows: Tools, Resources, Prompts | How should I use the UI to inspect server behavior end to end? | Faster issue isolation |
| 04 - CLI Mode, Automation, and CI Loops | How do I automate MCP checks without opening a browser? | Repeatable command-line validation |
| 05 - Security, Auth, and Network Hardening | How do I reduce local attack surface when using the proxy? | Safer local and shared environments |
| 06 - Configuration, Timeouts, and Runtime Tuning | Which settings matter most for long-running or interactive tools? | Better reliability under load |
| 07 - Inspector in Server Development Lifecycle | How does Inspector fit into day-to-day MCP server development? | Stable dev workflow |
| 08 - Production Ops, Testing, and Contribution | How do teams operate Inspector usage over time and contribute safely? | Operational playbook |
- how to validate MCP servers consistently across UI and CLI pathways
- how to handle transport-specific behavior without mixing concerns
- how to tune timeout/session settings for realistic tool workloads
- how to apply auth and origin controls to reduce remote execution risk
- Inspector README
- Inspector Client README
- Inspector Scripts README
- Inspector Development Guide
- Inspector Release Notes
- Inspector License
Start with Chapter 1: Getting Started.
- Start Here: Chapter 1: Getting Started
- Back to Main Catalog
- Browse A-Z Tutorial Directory
- Search by Intent
- Explore Category Hubs
- Chapter 1: Getting Started
- Chapter 2: Architecture, Transports, and Session Model
- Chapter 3: UI Debugging Workflows: Tools, Resources, Prompts
- Chapter 4: CLI Mode, Automation, and CI Loops
- Chapter 5: Security, Auth, and Network Hardening
- Chapter 6: Configuration, Timeouts, and Runtime Tuning
- Chapter 7: Inspector in Server Development Lifecycle
- Chapter 8: Production Ops, Testing, and Contribution
Generated by AI Codebase Knowledge Builder