Self-host MCP Inspector on a VPS

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.

levelrail-cli templates deploy mcp-inspector --name my-mcp-inspector

Specification

Status
Listed
Category
Developer Tools
Services
mcp-inspector
Ports
6274
Volumes
0
Memory
about 256 MiB
arm64
unknown
amd64
unknown
Settings to fill in
none
Listing
Community template

About MCP Inspector

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.

What it deploys

MCP Inspector runs as one service in a single Compose app, listening on port 6274.

ServiceImageTagPortsVolumes
mcp-inspector ghcr.io/modelcontextprotocol/inspector 2.14.0 6274 none

Before you install

  • CPU architecture. arm64 unknown. The scan could not read a manifest or the tag is chosen at install time. This is not a claim either way.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.

Settings and environment

You do not have to fill in anything. Values are never shown here.

ServiceVariableValue
mcp-inspectorHOSTPreset by the template

First run

  1. Open the deployment logs, copy the proxy session token and paste it into the Inspector configuration.

Install MCP Inspector on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get mcp-inspector
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy mcp-inspector --name my-mcp-inspector

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then MCP Inspector.

More in Developer Tools

All Developer Tools templates