bult:deploy

bult:deploy is a command for Claude Code from bultcloud/mcp-server. It costs 17 tokens per session (91 once invoked), scanned A, original, MIT.

A command for deploying the current project to Bult.ai, a service that hosts or runs projects, and checking whether the deployment succeeds.

In plain words
What is it for?
Finding the active Bult project, deploying the current code, checking deployment status, and investigating failed services.
Why use it?
It organizes deployment and status checking in one workflow instead of leaving you to inspect the linked project and service logs manually. If a service fails, it examines recent logs and summarizes the problem.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the bult-ai plugin — 3 commands shipped together , and of bult-ai

Good fit Finding the active Bult project, deploying the current code, checking deployment status, and investigating failed services.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bultcloud/mcp-server/deploy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/bultcloud/mcp-server

Made for: Claude Code.

Or install bult-ai, the plugin that ships this one along with the rest of its 3 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for bult:deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/bultcloud/mcp-server/deploy/github.svg)](https://agentmods.dev/commands/bultcloud/mcp-server/deploy)
Your own site
<a href="https://agentmods.dev/commands/bultcloud/mcp-server/deploy"><img src="https://agentmods.dev/badge/commands/bultcloud/mcp-server/deploy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for bult:deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/bultcloud/mcp-server/deploy"><img src="https://agentmods.dev/badge/commands/bultcloud/mcp-server/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 91 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00091
Opus 5.5 $0.00007 $0.00036
Sonnet 5.5 $0.00003 $0.00018
Haiku 4.5 $0.00002 $0.00009

Measured 1mo ago against content hash 0d2fe31c00fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bult:deploy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

extensions/claude-code/commands/deploy.md · 15 lines

What it actually says

Use Bult to deploy the current project.

Steps:

  1. Identify the active or linked Bult project.
  2. If no project is selected, list projects and ask the user which one to use.
  3. Deploy the project.
  4. Check deployment status.
  5. If a service fails, inspect recent logs and summarize the failure.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 15 lines · 17 tokens per session scan A 0d2fe31c00fe

Subscribe to this mod's changes

bult:deploy is a command published in the GitHub repository bultcloud/mcp-server (2 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 91 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.