# ZapX MCP server

> Manage ZAP-Hosting game servers, VPS, TeamSpeak servers and domains from your AI client.

- Listing: https://mcp.tc/i/zapx
- Connect: use the server's own URL `https://zap-hosting.com/api/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: ZAP-Hosting
- Homepage: <https://zap-hosting.com/en/mcp>

## About

ZapX connects an AI client to your ZAP-Hosting services. You can check service status, read logs and the console, run console commands, browse and edit config files, create and restore backups, and prepare plan changes with a price preview. It covers game servers, VPS and TeamSpeak servers.

It runs as a hosted remote endpoint over streamable HTTP, with nothing to install. Users sign in with their ZapX account through OAuth. MCP access is included with ZapX Pass Plus and above. Permissions are set per connection, and critical actions ask for confirmation.

## What it can do

- List services and check live status
- Read console output and run console commands
- Browse directories and edit config files
- Create, list and restore backups
- Preview prices and request plan changes
- Control services such as restart

## Example prompts

- "Which services do I have at ZAP-Hosting and which are running?"
- "Show the last console lines of my game server."
- "Create a backup of my service, then list all backups."
- "Show me the price preview for upgrading my VPS to 8 GB RAM."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http zapx https://zap-hosting.com/api/mcp
```

2. Start Claude Code, type `/mcp`, pick **zapx** and choose **Authenticate**. A browser window opens for the ZAP-Hosting sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **ZapX** and paste this URL:

```url
https://zap-hosting.com/api/mcp
```

3. Click **Add**, then **Connect**, and sign in when ZAP-Hosting asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=ZapX&connectorUrl=https%3A%2F%2Fzap-hosting.com%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://zap-hosting.com/api/mcp` and click **Add**.

3. Click **Connect** and sign in when ZAP-Hosting asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://zap-hosting.com/api/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to ZAP-Hosting to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=zapx&config=eyJ1cmwiOiJodHRwczovL3phcC1ob3N0aW5nLmNvbS9hcGkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "zapx": {
      "url": "https://zap-hosting.com/api/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=zapx&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fzap-hosting.com%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"zapx","type":"http","url":"https://zap-hosting.com/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "zapx": {
      "type": "http",
      "url": "https://zap-hosting.com/api/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "zapx": {
      "serverUrl": "https://zap-hosting.com/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add zapx --url https://zap-hosting.com/api/mcp
codex mcp login zapx
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.zapx]
url = "https://zap-hosting.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http zapx https://zap-hosting.com/api/mcp
```

Then, inside Gemini CLI, run `/mcp auth zapx` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "zapx": {
      "type": "http",
      "url": "https://zap-hosting.com/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://zap-hosting.com/api/mcp`.

## Recent changes

- 2026-11-16 00:24 UTC: Tracking started: version 1.0.0. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/zapx#history (Atom feed: https://mcp.tc/i/zapx/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-11
- Updated: 2026-11-11

---
Source: https://mcp.tc/i/zapx (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
