Cloady
Official# @cloady/mcp
Local [MCP](https://modelcontextprotocol.io) server for [Cloady](https://cloady.com) — 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
Create an API token in the dashboard under **Account → API tokens**.
### Claude Code
```sh
claude mcp add cloady -e BEARER_TOKEN_CLOADY=cldy_… -- npx -y @cloady/mcp
```
### Claude Desktop / Cursor / any MCP client
```json
{
"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](https://cloady.com/docs).
## Distribution
This repository contains the source and build already published as `@cloady/mcp@0.5.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](https://cloady.com/privacy) for data handling and contact information. Use the minimum necessary token scope; write tools can change or delete resources.
The 0.5.1 desktop bundle adds tool titles and conservative read/write annotations to the 0.5.0 API implementation. The Cursor configuration continues to use the published npm 0.5.0 release.
TDQS
Scored across 88 tools
Most tools have clear distinct purposes, but a few pairs like 'deployApp' and 'createAppDeploy' have overlapping functionality that could cause misselection. The descriptions help clarify, but the sheer number of tools increases the chance of confusion.
Tool names generally follow a verb_noun pattern, but the verbs are inconsistent (list, get, create, update, set, check, stream, etc.) and some pairs like 'verifyPhone' vs 'startPhoneVerification' use different structures. The naming is readable but not highly uniform.
With 88 tools, this server is far beyond a typical well-scoped set (3-15) and even exceeds the 'extreme mismatch' threshold of 50+. The sheer volume makes it overwhelming and likely to contain redundant or overly granular operations.
The toolset appears to cover a broad range of CRUD and lifecycle operations across apps, workspaces, billing, and security. While some gaps might exist (e.g., no explicit 'deleteToken' but 'revokeToken' serves that purpose), the coverage seems comprehensive for the domain.