# Cloady MCP server

> Manage Cloady app and database hosting: deployments, logs, resource monitoring, services and workspace settings.

- Listing: https://mcp.tc/i/cloady
- Connect: use the server's own URL `https://cloady.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: Cloady (NeptoLab)
- Homepage: <https://cloady.com/>

## About

Connects an AI assistant to Cloady, a cloud platform for hosting apps and databases. It covers deployment management, reading logs, resource monitoring, services and workspace configuration.

The hosted endpoint uses Streamable HTTP, and users sign in to their Cloady account through OAuth. A local alternative runs with npx -y @cloady/mcp and a Cloady API token supplied in the BEARER\_TOKEN\_CLOADY environment variable.

## What it can do

- Manage deployments
- Read service logs
- Monitor resource usage
- Manage services in a workspace
- Configure workspace settings

## Example prompts

- "Show the latest logs for my backend API service on Cloady."
- "Redeploy my Marketing Site app."
- "How much CPU and RAM is my workspace using right now?"
- "List the services in my Acme workspace."

## Install

### Claude Code

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

```bash
claude mcp add --transport http cloady https://cloady.com/api/mcp
```

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

```url
https://cloady.com/api/mcp
```

3. Click **Add**, then **Connect**, and sign in when Cloady (NeptoLab) 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=Cloady&connectorUrl=https%3A%2F%2Fcloady.com%2Fapi%2Fmcp>) (opens connector settings)

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

3. Click **Connect** and sign in when Cloady (NeptoLab) 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://cloady.com/api/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Cloady (NeptoLab) 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=cloady&config=eyJ1cmwiOiJodHRwczovL2Nsb2FkeS5jb20vYXBpL21jcCJ9>) (opens Cursor)

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

`mcp.json`:

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

Or from a terminal:

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

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

`.vscode/mcp.json`:

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

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

`config.toml`:

```toml
[mcp_servers.cloady]
url = "https://cloady.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http cloady https://cloady.com/api/mcp
```

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

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-27
- Updated: 2026-10-27

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