# xCloud MCP server

> Manage xCloud servers, sites, WordPress, SSL, backups and deployments by asking your AI assistant.

- Listing: https://mcp.tc/i/xcloud
- Connect: use the server's own URL `https://app.xcloud.host/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: xCloud
- Homepage: <https://xcloud.host/mcp/>

## About

Connects an MCP client to an xCloud hosting account. You can manage servers, sites, WordPress installs, SSL certificates, backups and deployments from an editor or chat instead of the dashboard.

It runs as a hosted Streamable HTTP endpoint at https://app.xcloud.host/mcp. Clients with browser sign-in connect through OAuth. Headless clients such as CI can send an API key with the mcp:invoke scope as a Bearer token. An xCloud account is required.

## What it can do

- Manage servers and sites on xCloud
- Administer WordPress sites
- Handle SSL certificates
- Create and manage backups
- Run deployments
- Check which xCloud account is connected

## Example prompts

- "Who am I on xCloud?"
- "List the servers in my xCloud account"
- "Create a backup of my WordPress site before I update it"
- "Check the SSL status of my sites on xCloud"

## Install

### Claude Code

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

```bash
claude mcp add --transport http xcloud https://app.xcloud.host/mcp
```

2. Start Claude Code, type `/mcp`, pick **xcloud** and choose **Authenticate**. A browser window opens for the xCloud 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 **xCloud** and paste this URL:

```url
https://app.xcloud.host/mcp
```

3. Click **Add**, then **Connect**, and sign in when xCloud 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=xCloud&connectorUrl=https%3A%2F%2Fapp.xcloud.host%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://app.xcloud.host/mcp` and click **Add**.

3. Click **Connect** and sign in when xCloud 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://app.xcloud.host/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to xCloud 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=xcloud&config=eyJ1cmwiOiJodHRwczovL2FwcC54Y2xvdWQuaG9zdC9tY3AifQ%3D%3D>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/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=xcloud&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapp.xcloud.host%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"xcloud","type":"http","url":"https://app.xcloud.host/mcp"}'
```

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "xcloud": {
      "type": "http",
      "url": "https://app.xcloud.host/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": {
    "xcloud": {
      "serverUrl": "https://app.xcloud.host/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 xcloud --url https://app.xcloud.host/mcp
codex mcp login xcloud
```

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

`config.toml`:

```toml
[mcp_servers.xcloud]
url = "https://app.xcloud.host/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http xcloud https://app.xcloud.host/mcp
```

Then, inside Gemini CLI, run `/mcp auth xcloud` 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": {
    "xcloud": {
      "type": "http",
      "url": "https://app.xcloud.host/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://app.xcloud.host/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-11
- Updated: 2026-11-11

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