Ploi Cloud MCP Server

Ploi Cloud MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. European cloud hosting. Use your favorite AI coding assistant to easily deploy and manage apps on Ploi Cloud.

What you get

Official Model Context Protocol (MCP) server for Bult.ai, a DevOps platform and cloud hosting Platform-as-a-Service for deploying apps, GitHub repositories, Docker images, databases, and services with AI agents.

• Deploy GitHub repositories, Docker images, databases, and app services from
• Project lifecycle tools: list, inspect, create, update, delete, deploy, start,
• Service management for daemon and database services, including Docker image and
• Persistent volumes, route/domain mappings, templates, service logs, and build
• MCP tool annotations for read-only, idempotent, and destructive operations
• Works over stdio with Claude Desktop, Claude Code, Cursor, Google Antigravity and other MCP-compatible

What the assistant can call

Once Ploi Cloud is connected, these are the calls the assistant has available:

• Projects — The Projects tool exposed by this server
• Services — The Services tool exposed by this server
• Volumes — The Volumes tool exposed by this server
• Routes — The Routes tool exposed by this server
• Templates — The Templates tool exposed by this server

Setting it up

The server ships on npm as @bultcloud/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 3 environment variables: BULT_API_URL, BULT_API_TOKEN, DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or newer. - Bult API token.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ploi Cloud's toolset — Projects, Services, Volumes and 2 more — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ploi cloud mcp server does with a few real requests.