Skip to main content

Live Preview

You can preview the inspector at inspector.mcp-use.com See Live Inspector

​
Self-Hosting MCP Inspector

Deploy the MCP Inspector to your own infrastructure with a single Docker container. Perfect for enterprise environments, air-gapped networks, or when you need full control over your debugging environment.

Docker Image

The MCP Inspector provides an official Docker image via Docker Hub that can be used for deployments on any system that is running Docker. Here’s a one-liner that will start a container running the Inspector.
docker run -d -p 8080:8080 --name mcp-inspector mcpuse/inspector:latest
Docker Hub

​
Quick Deploy

https://mintcdn.com/mcpuse/-dX3pYiRHSZpYTFG/images/railway.svg?fit=max&auto=format&n=-dX3pYiRHSZpYTFG&q=85&s=4290dab651b4071ed3251ea14cf03df9

Railway

Deploy instantly to Railway with automatic HTTPS and custom domains. Deploy on Railway

​
CLI Usage

You can also run the inspector using the CLI. See the CLI Usage guide for command-line options and examples.

​
Docker Deployment

​
Using Docker Run

Deploy locally or on any Docker-compatible infrastructure: 
docker run -d \
  --name mcp-inspector \
  -p 8080:8080 \
  -e NODE_ENV=production \
  mcpuse/inspector:latest

​
Using Docker Compose

For more complex deployments with environment variables: 
version: '3.8'
services:
  mcp-inspector:
    image: mcpuse/inspector:latest
    ports:
      - "8080:8080"
    environment:
      - NODE_ENV=production
      - PORT=8080
      # Optional: Allow embedding from specific origins
      - MCP_INSPECTOR_FRAME_ANCESTORS=https://app.example.com https://dev.example.com
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080"]
      interval: 30s
      timeout: 10s
      retries: 3

​
Environment Variables

All configuration is optional. The inspector works out of the box with sensible defaults.
VariableDefaultDescription
NODE_ENVproductionNode.js environment
PORT8080Port to run the inspector on
HOST0.0.0.0Host to bind to
MCP_INSPECTOR_FRAME_ANCESTORS'self' in production, * in devConfigure which origins can embed inspector widgets in iframes. Use space-separated origins (e.g., "https://app.example.com https://dev.example.com") or * for all.

​
Support

For self-hosting support: Visit inspector.mcp-use.com to try the hosted version first!