Wisp MCP server

Wisp MCP — connect a WISP game panel to AI

English · Français

Wisp MCP is a source-available Model Context Protocol server for the WISP game panel Client API. It lets MCP-compatible AI clients inspect and manage game servers through the panel instead of giving the AI unrestricted access to the host machine.

It is hosting-provider agnostic. If your hosting company gives you a WISP panel and a Client API token, use that panel URL. No provider-specific code path is required.

Start with the visual guide: https://wisp.hinoake.com/en/

Do I have a WISP panel?

If your game-server panel looks like this, it is likely WISP:

Typical WISP client dashboard. Hosts can white-label WISP, so colors, logo and domain may differ.

If you are unsure, ask your host: “Does my server use WISP, and can I create a WISP Client API token?” See How to recognize WISP.

What it can do

• inspect server state, CPU, memory, disk and network usage;
• browse paginated directories, read configs and tail logs;
• search large files and read bounded chunks without flooding the model context;
• create files, or safely edit existing plugin/config files with SHA-256 change detection;
• send console commands;
• start, stop and restart servers;
• create and inspect backups;
• manage databases when enabled;
• inspect audit logs and common panel state;
• run locally with stdio or remotely with Streamable HTTP;
• keep destructive operations behind a separate capability switch.

Because it targets WISP rather than one game, the same MCP can be used with Rust, Minecraft and other game servers managed by WISP.

Install on a Linux VPS

For Debian 12 or Ubuntu 24.04+:

curl -fsSL https://raw.githubusercontent.com/BreezeDelegate/wisp-mcp/main/install-vps.sh | sudo bash

The installer asks for:

1. the WISP panel URL supplied by your host;
2. an optional default server ID;
3. your WISP Client API token in a hidden terminal prompt.

It creates a dedicated system user, stores credentials outside Git, and runs wisp-mcp doctor before reporting success.

For a deeper read-only API compatibility check, run wisp-mcp compatibility. It verifies the minimal response contract used by the MCP without modifying the game server.

For ChatGPT, install the OpenAI tunnel helper at the same time:

curl -fsSL https://raw.githubusercontent.com/BreezeDelegate/wisp-mcp/main/install-vps.sh | sudo bash -s -- --with-openai

Connect your AI client

Wisp MCP is not tied to one model vendor. It implements standard MCP transports.

ChatGPT

Use OpenAI Secure MCP Tunnel for an always-on private VPS, then add the MCP as a custom app in ChatGPT Developer Mode. See ChatGPT setup.

Claude Code

Claude Code can launch Wisp MCP directly. If Wisp MCP is on a remote VPS, use SSH as the stdio command:

claude mcp add --scope user wisp -- ssh user@your-vps /usr/local/bin/wisp-mcp-stdio

Then verify:

claude mcp get wisp

Other MCP clients

Use one of the standard transports:

Shortened. The full README is on GitHub.