You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MCP Inspector consists of two main components that work together:
10
+
11
+
-**MCP Inspector Client (MCPI)**: A React-based web UI that provides an interactive interface for testing and debugging MCP servers
12
+
-**MCP Proxy (MCPP)**: A Node.js server that acts as a protocol bridge, connecting the web UI to MCP servers via various transport methods (stdio, SSE, streamable-http)
13
+
14
+
Note that the proxy is not a network proxy for intercepting traffic. Instead, it functions as both an MCP client (connecting to your MCP server) and an HTTP server (serving the web UI), enabling browser-based interaction with MCP servers that use different transport protocols.
15
+
7
16
## Running the Inspector
8
17
9
18
### Requirements
10
19
11
20
- Node.js: ^22.7.5
12
21
22
+
### Quick Start (UI mode)
23
+
24
+
To get up and running right away with the UI, just execute the following:
25
+
26
+
```bash
27
+
npx @modelcontextprotocol/inspector
28
+
```
29
+
30
+
The server will start up and the UI will be accessible at `http://localhost:6274`.
31
+
13
32
### From an MCP server repository
14
33
15
34
To inspect an MCP server implementation, there's no need to clone this repo. Instead, use `npx`. For example, if your server is built at `build/index.js`:
0 commit comments