Our MCP

Deploy anywhere. We currently support AWS, custom VPS, and GCE. More services are coming soon. Search the directory for CloudPloy/Claude-plugin .

The plugin URL is https://claude.ai/directory/cloudploy (opens in a new tab) .

1. Open Claude on the web or in the desktop app.
2. Go to Customize, then Connectors. Paste CloudPloy/Claude-plugin into the search.
3. Or open https://claude.ai/directory/cloudploy (opens in a new tab) and choose Connect.
4. Sign in to CloudPloy in the browser and approve the connection. The MCP uses the team you sign in to.
5. Start a chat and ask it to list your servers. If the tools are missing, open the connector again and finish sign-in.

Yes. Claude Code installs the same plugin. Search for CloudPloy/Claude-plugin .

The plugin URL is https://claude.ai/directory/cloudploy (opens in a new tab) .

1. Open Claude Code.
2. Run /plugin and paste CloudPloy/Claude-plugin . The desktop app has the same search under Plugins.
3. Sign in to CloudPloy in the browser and approve the connection.
4. If you already connected CloudPloy/Claude-plugin in Claude with this account, don't install it again. Run /mcp and confirm CloudPloy/Claude-plugin is listed. Finish sign-in there if it isn't.
5. Ask it to list your servers. The plugin includes the deploy skill, so it checks connected credentials and the cost before it creates a server.

To add the server without the plugin, run this in the project. Add --scope user before --transport if you want it in every project. Then run /mcp and sign in.

claude mcp add --transport http cloudploy https://app.cloudploy.com/mcp

In the ChatGPT desktop app, add an MCP server. Name it CloudPloy .

The server URL is https://app.cloudploy.com/mcp .

1. Open the ChatGPT desktop app.
2. Open Settings, then MCP servers, then Add server.
3. Paste CloudPloy as the name.
4. Choose Streamable HTTP.
5. Paste https://app.cloudploy.com/mcp as the URL.
6. Save, then choose Restart.
7. When the server shows that it needs sign-in, choose Authenticate. The browser opens. Sign in to CloudPloy and approve the connection.
8. In the composer, type /mcp to confirm CloudPloy is connected.

Codex and the Codex IDE extension read this same list. The desktop app writes it to ~/.codex/config.toml. A trusted project can keep its own copy in .codex/config.toml.

Add the same MCP server. If you already added it in the ChatGPT desktop app, Codex reads that list. From the terminal, the server URL is https://app.cloudploy.com/mcp .

codex mcp add cloudploy --url https://app.cloudploy.com/mcp
codex mcp login cloudploy
codex mcp list

1. codex mcp add registers the server.
2. codex mcp login cloudploy opens the browser so you can sign in.
3. codex mcp list shows whether CloudPloy is configured.
4. In a Codex session, /mcp shows the connected servers.

The default file is ~/.codex/config.toml. For one repo, use .codex/config.toml inside a trusted project.

1. Open Cursor Settings, then MCP. You can also add it from Customize.
2. Add a remote server named CloudPloy . Paste https://app.cloudploy.com/mcp . The transport is Streamable HTTP.
3. Cursor opens the browser. Sign in to CloudPloy. Leave the header field empty. This MCP uses OAuth, not a pasted token.
4. For one project, put the file at .cursor/mcp.json. For every project, use ~/.cursor/mcp.json.
5. Reload the window if the tools don't show up. Then ask Cursor to list your CloudPloy servers.

{
  "mcpServers": {
    "cloudploy": {
      "url": "https://app.cloudploy.com/mcp"
    }
  }
}

Name it CloudPloy . The server URL is https://app.cloudploy.com/mcp . Run this from the project that should use the MCP. Add --global on the first command if you want it in every project.

opencode mcp add cloudploy --url https://app.cloudploy.com/mcp
opencode mcp auth cloudploy

1. opencode mcp add writes the server into your config.
2. opencode mcp auth cloudploy opens the browser for sign-in. In the app, /mcps does the same thing.
3. OAuth stays on unless you set oauth to false. Don't add an Authorization header.

The current config puts the server under mcp.servers. Older OpenCode puts the name directly under mcp and sets enabled to true.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "cloudploy": {
        "type": "remote",
        "url": "https://app.cloudploy.com/mcp"
      }
    }
  }
}

Any client that can call a remote MCP server over HTTP, and sign in with OAuth, can use the same server.

1. Add a remote server. The transport name is usually Streamable HTTP.
2. Name it CloudPloy .
3. Paste https://app.cloudploy.com/mcp . Don't append a token or an API key.
4. When the client asks you to authenticate, finish sign-in in the browser.
5. Ask it to list your servers. If that fails, the sign-in didn't finish, or the client is still on a local stdio server.

The server is also listed in the MCP Registry.