The Deployer vs Bult
The Deployer is an MCP server published by thedploy.com. Marketplaces we read that list it: 1 (Official MCP Registry). Bult is an MCP server published by bultcloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  The Deployer |  Bult |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 622 Downloads/week (npm): 92 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 173 Downloads/week (npm): 20 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | The Deployer | Bult |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.thedploy.com/api/v1/mcp) | On your machine (@bultcloud/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/avinash147-1193/thedeployer-mcp | github.com/bultcloud/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
The Deployer
Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.
Bult
Deploy and manage Bult apps from AI coding agents.
How to run each
The Deployer As a remote MCP server
claude mcp add --transport http deployer https://app.thedploy.com/api/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: THEDEPLOYER_API_KEY (secret), Authorization header
Bult As a local MCP server: npm package
claude mcp add --env "BULT_API_TOKEN=<YOUR_BULT_API_TOKEN>" --env "BULT_API_URL=<YOUR_BULT_API_URL>" --transport stdio bult -- npx -y @bultcloud/mcp-serverRequires: BULT_API_TOKEN (secret), BULT_API_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only The Deployer has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only The Deployer asks for
THEDEPLOYER_API_KEY (secret)
Only Bult asks for
BULT_API_TOKEN (secret)BULT_API_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: The Deployer · What it can do: Bult · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.