Cloady

@cloady/mcp

Local MCP server for Cloady — gives AI assistants the whole Cloady API as tools: workspaces, apps, deploys, environment variables, domains, volumes, members, integrations, billing and support tickets.

Generated from Cloady's OpenAPI contract, so every REST operation is a tool named after its operation id (listVars, createVar, deployApp, execCommand). It runs over stdio and calls https://cloady.com with your API token.

Setup

For the OAuth-based Claude plugin, see Cloady for Claude. It connects to the hosted MCP endpoint without installing the npm server or copying an API token.

Gemini CLI extension

Install the extension from this repository:

gemini extensions install https://github.com/Cloady/cloady-mcp

Open Gemini CLI and run /mcp auth cloady to sign in to Cloady through OAuth. Complete any required account verification and choose the narrowest scope for your task: read, deploy, or full. No API key or local npm server is needed for this extension.

Try "List my Cloady workspaces and running apps", "Explain the latest deployment failure from my app's build logs", or "Show available database templates and pricing before creating anything."

The extension sends tool arguments to https://cloady.com/api/mcp and returns permitted results to Gemini. These can include account and workspace metadata, application configuration, code, logs, metrics, database content, and support messages, depending on the tools you request. Google handles received results under its own policies; Cloady's handling, retention, and deletion are described in the Privacy Policy. An account-level connection can cover all workspaces the account belongs to, subject to scope and workspace role. Revoke its token in Cloady Account → API tokens to stop future requests. Revocation does not delete hosted data or copies already received by Gemini.

Review the target workspace, app, environment, region, and any charges before authorizing changes. Write tools can change or delete resources. The extension is free; hosted resources follow Cloady pricing. Support and deletion requests: hello@cloady.com.

The Gemini extension and Claude plugin are versioned separately from the local npm package.

Qwen Code

Qwen Code supports Gemini CLI extensions and converts their manifest during installation:

qwen extensions install https://github.com/Cloady/cloady-mcp

Use Cloady's OAuth connection in your client. The same account permissions, data handling, and hosting charges described above apply. See Qwen Code's extension documentation.

Local stdio package

Create an API token in the dashboard under Account → API tokens.

Claude Code

claude mcp add cloady -e BEARER_TOKEN_CLOADY=cldy_… -- npx -y @cloady/mcp

Claude Desktop / Cursor / any MCP client

{

"mcpServers": { "cloady": { "command": "npx", "args": ["-y", "@cloady/mcp"], "env": { "BEARER_TOKEN_CLOADY": "cldy_…" } } } }

API_BASE_URL overrides the target if you run Cloady elsewhere.

Tools

One per API operation. Arguments are the operation's path parameters, query parameters and body fields flattened into one object, so createVar takes workspaceSlug, appSlug, env, region, key, value and isSecret.

The token's scope (read / deploy / full) and your workspace role are enforced by the API on every call, exactly as they are for the dashboard and the SDKs.

Docs

Full reference at cloady.com/docs.

Distribution

This repository contains the source and build published as @cloady/mcp@0.18.0 on npm, plus directory packaging. Run npm install and npm start. The Cursor plugin uses the pinned npm release. MCPB bundles include production dependencies.

Privacy Policy

This local server forwards tool arguments to the Cloady API using your configured API token. See Cloady Privacy Policy for data handling and contact information. Use the minimum necessary token scope; write tools can change or delete resources.

The 0.18.0 desktop bundle adds tool titles and conservative read/write annotations to the 0.18.0 API implementation. The Cursor configuration uses the published npm 0.18.0 release.