skills/mcp-use__mcp-use
1
0
Fork 0
mirror of https://github.com/mcp-use/mcp-use.git synced 2026-09-14 18:06:01 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(inspector): add self-hosting guide (#1861)

Browse Source 
* docs(inspector): add self-hosting guide

The inspector README and feature table reference self-hosting with Docker,
but the docs site had no page for it (mcp-use.com/docs/inspector/self-hosting
404s). Add the guide based on the README's self-hosting section: Docker Hub
image, docker run / compose deployment, environment variables, and how
self-hosting compares to the hosted and CLI options.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(inspector): bind examples to loopback, add exposure warning and air-gapped transfer steps

Addresses review feedback on #1861:
- trim wordy intro sentence
- quick start and deployment examples now bind 127.0.0.1 to avoid
  exposing the Inspector proxy on all interfaces; added Warning with
  reverse-proxy/firewall guidance for remote access
- add docker save/load transfer steps for air-gapped hosts

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: ayaanmacmini3 <ayaanmacmini3@ayaanmacmini3s-Mac-mini.local>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Ayaan Gazali
2026-07-21 10:00:46 -07:00
committed by GitHub
parent 2eb524e099
commit 9978343d63
2 changed files with 94 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs.json
+2
View File
@@ -224,6 +224,7 @@
"inspector/keyboard-shortcuts",
"inspector/command-palette",
"inspector/integration",
"inspector/self-hosting",
"inspector/debugging-chatgpt-apps"
]
},
@@ -705,6 +706,7 @@
"inspector/keyboard-shortcuts",
"inspector/command-palette",
"inspector/integration",
"inspector/self-hosting",
"inspector/debugging-chatgpt-apps"
]
}
docs/inspector/self-hosting.mdx
+92
View File
@@ -0,0 +1,92 @@
---
title: "Self-Hosting"
description: "Deploy your own MCP Inspector instance with Docker."
icon: "container"
---
Run the Inspector on your own infrastructure when you need full control over your debugging environment.
The official Docker image is published at [`mcpuse/inspector`](https://hub.docker.com/r/mcpuse/inspector) on Docker Hub.
## Quick start
```bash
docker run -d -p 127.0.0.1:8080:8080 --name mcp-inspector mcpuse/inspector:latest
```
Then open `http://localhost:8080` to access your self-hosted Inspector.
<Warning>
Anyone who can reach the Inspector can use it to connect to and call your MCP servers. The examples bind to `127.0.0.1` so the Inspector is only reachable from the host itself. If you need remote access, put it behind a reverse proxy with authentication and TLS, or restrict access with firewall rules — don't publish port 8080 on all interfaces.
</Warning>
## Deployment options
<Tabs>
<Tab title="Docker Run">
```bash
docker run -d \
--name mcp-inspector \
-p 127.0.0.1:8080:8080 \
mcpuse/inspector:latest
```
</Tab>
<Tab title="Docker Compose">
```yaml
services:
mcp-inspector:
image: mcpuse/inspector:latest
ports:
- "127.0.0.1:8080:8080"
restart: unless-stopped
healthcheck:
test: ["CMD", "wget", "-q", "--spider", "http://localhost:8080/inspector"]
interval: 30s
timeout: 10s
retries: 3
```
</Tab>
</Tabs>
<Note>
The image is based on `node:20-alpine`, which ships `wget` (BusyBox) but not `curl` — use `wget` in healthchecks.
</Note>
## Ports
The container always listens on port `8080` — the image's start command pins it with `--port 8080`, so a `PORT` environment variable has no effect. To serve on a different host port, remap it with Docker instead:
```bash
docker run -d -p 127.0.0.1:3001:8080 mcpuse/inspector:latest
```
`NODE_ENV=production` is already set in the image; no environment variables are required.
## Air-gapped installation
For hosts without registry access, transfer the image as a tarball:
```bash
# On a connected host
docker pull mcpuse/inspector:latest
docker save mcpuse/inspector:latest -o mcp-inspector.tar
# On the air-gapped host
docker load -i mcp-inspector.tar
```
<Note>
When connecting from a self-hosted Inspector to an MCP server on another host, the browser must be able to reach the server directly, or you can use the proxy connection mode. See [Connection settings](/inspector/connection-settings) for when to use each.
</Note>
## Alternatives
Self-hosting is one of three ways to run the Inspector:
| Option | Command | Best for |
| --- | --- | --- |
| Hosted | [inspector.mcp-use.com](https://inspector.mcp-use.com) | Quick testing, no install |
| Local CLI | `npx @mcp-use/inspector` | Local development |
| Self-hosted | `docker run mcpuse/inspector:latest` | Production, enterprise, air-gapped |
Servers built with `mcp-use` also auto-mount the Inspector at `/inspector` — see the [Inspector overview](/inspector/index).