@vertracloud/mcp

Official MCP server for Vertra Cloud: gives your AI assistant (Claude, Cursor, VS Code, n8n) the tools to deploy applications, read logs, create databases and restore snapshots — on your own account, with your own API key.

Quick start · Connect from claude.ai · Tools · Prompt ideas · Common issues

Quick start

Prerequisite: Node 18 or newer.

1. In the dashboard, go to Settings → API keys, create a key and check the scopes the assistant will need (start with the read-only ones).
2. Copy the key — it’s shown only once.
3. Configure your client:

Claude Code

claude mcp add vertracloud -e VERTRA_API_KEY=your_key -- npx -y @vertracloud/mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "vertracloud": {
      "command": "npx",
      "args": ["-y", "@vertracloud/mcp"],
      "env": { "VERTRA_API_KEY": "your_key" }
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "vertracloud": {
      "command": "npx",
      "args": ["-y", "@vertracloud/mcp"],
      "env": { "VERTRA_API_KEY": "your_key" }
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "vertracloud": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@vertracloud/mcp"],
      "env": { "VERTRA_API_KEY": "your_key" }
    }
  }
}

Restart the client and ask something like “list my apps on Vertra”.

Connect from claude.ai

In the browser there’s nothing to install:

1. Open Settings → Connectors → Add custom connector.
2. Enter the URL https://mcp.vertracloud.app/mcp.
3. Click Connect and sign in to your Vertra account.
4. Check the scopes you want to grant and confirm.

Tools marked “local only” in the table below don’t show up here: they read and write files on your computer, which only makes sense in Claude Desktop, Claude Code or Cursor.

Tools

Folders and favorites are preferences persisted on the server: tools with personal change the account’s own organization, and tools with workspace change only the user’s organization within that workspace. They organize applications and databases, with no relation to Flow’s groups, layout or local storage.

Documentation

Applications

Deploys

Environment variables

Files

Network and domains

Databases

Docker images

Snapshots

Account

Workspaces

Billing

Blob storage

Templates

Stacks

Prompt ideas

• “Deploy this folder as a Node app called support-bot, with 512 MB.”
• “Why did orders-api go down? Show me the last 200 lines of the log.”
• “Create a 1 GB Postgres and put its URL in orders-api’s env.”
• “Restore yesterday’s snapshot of support-bot.”
• “Buy 3 months of Pro with the coupon LAUNCH.”
• “Read orders-api’s log, fix it in my checkout code, and deploy.”

Security

Tools that read or write files on your computer only operate inside the folder the server was started in. If your client starts the server at the system root or your user folder, point it at the project folder with VERTRA_MCP_ROOT (alongside VERTRA_API_KEY, in the configuration’s env) — files outside that folder, and credential folders like .ssh and .aws, are rejected even if the assistant asks for them.

This server only talks to the Vertra Cloud public API, always with your key — it has no permissions of its own. list_envs returns only the NAMES of environment variables: the value never leaves the server, because everything a tool returns enters the assistant’s history. The key is the boundary of what the agent can do: grant only the scopes you need, and revoke the key in the dashboard when you’re done.

Common issues

Contributing and license

Contributions are welcome — see CONTRIBUTING.md. License MIT.