Self-host MCP Inspector with Levelrail
The official visual tester for Model Context Protocol servers: connect, list tools and resources and call them from the browser. MIT licensed. Open the logs to copy the session token.
- Authormodelcontextprotocol
- LicenceMIT
- Memory256 MiB
- Services1
How to self-host MCP Inspector
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/modelcontextprotocol/inspector:2.14.0
-
Create the app
One service starts in a single Compose app, on port 6274.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the deployment logs, copy the proxy session token and paste it into the Inspector configuration.
MCP Inspector requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 6274
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then MCP Inspector. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the MCP Inspector docs page.
Deploy MCP Inspector your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy MCP Inspector from the CLI
levelrail-cli templates deploy mcp-inspector --name my-mcp-inspector Deploy MCP Inspector with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/mcp-inspector/deploy MCP Inspector configuration
MCP Inspector services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mcp-inspector | ghcr.io/modelcontextprotocol/inspector:2.14.0 | 6274 | none |
MCP Inspector environment variables
| Variable | Service | Value |
|---|---|---|
| HOST | mcp-inspector | Preset by the template |
Ports and volumes
- Ports
- 6274
- Volumes
- none
MCP Inspector FAQ
How much memory does MCP Inspector need?
The catalog lists about 256 MiB of memory for MCP Inspector.
Does MCP Inspector run on arm64?
For MCP Inspector, arm64 support is not confirmed; amd64 is unknown.
What licence is MCP Inspector under?
MCP Inspector is licensed under MIT, which is permissive, with few conditions on reuse.
Does MCP Inspector need configuration before it starts?
No. The template fills in its own defaults.
Which ports does MCP Inspector use?
MCP Inspector listens on port 6274 inside the stack.
Can I deploy MCP Inspector on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for MCP Inspector, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/modelcontextprotocol/inspector:2.14.0 is what you deploy there.