deploy

A command-line deployment tool for MCP servers, which are programs that provide tools to AI applications. It supports several cloud targets and includes commands for deployment setup, logs, metrics, testing, rollback, and removal.

In plain words
What is it for?
Use it to initialise deployment settings, deploy to AWS Lambda, Google Cloud Run, Cloudflare Workers, or pmcp.run, inspect operations, test releases, roll back, or destroy deployments.
Why use it?
It brings common deployment and operational actions into one command-line workflow, including options for OAuth configuration and preserving customised deployment files.

Command

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.

agentmods
npx agentmods add commands/paiml/rust-mcp-sdk/deploy
Clone the repo
git clone --depth 1 https://github.com/paiml/rust-mcp-sdk
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.04446
Opus 5 $0.00000 $0.02223
Sonnet 5 $0.00000 $0.00889
Haiku 4.5 $0.00000 $0.00445

Measured 2d ago against content hash 49b6a36a6d86, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

cargo-pmcp/docs/commands/deploy.md · 430 lines

How it starts

The opening of the file, as written. The whole thing — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cargo pmcp deploy

Deploy MCP server to cloud platforms.

Usage

cargo pmcp deploy [OPTIONS] [SUBCOMMAND]

When invoked without a subcommand, builds and deploys to the configured target.

Description

Deploy to AWS Lambda, Google Cloud Run, Cloudflare Workers, or pmcp.run. Includes full lifecycle management: init, deploy, logs, metrics, test, rollback, and destroy.

Deploy Options

Option Description
--target <TARGET> Deployment target: aws-lambda, cloudflare-workers, google-cloud-run, pmcp-run
--shared-pool <POOL> Use shared OAuth pool for SSO (pmcp-run only)
--no-oauth Skip OAuth configuration during deployment
--regenerate-stack (alias --force) Overwrite an existing deploy/lib/stack.ts. By default the file is preserved if it already exists (so an operator-curated stack is never silently clobbered); pass this flag to regenerate it from the loaded config.

Subcommands

Subcommand Description
init Initialize deployment configuration
logs View deployment logs
metrics View deployment metrics
test Test the deployment
rollback Rollback to previous version
destroy Remove the deployment
secrets Manage deployment secrets
outputs Show deployment outputs
login Login to deployment target
logout Logout from deployment target
oauth Manage OAuth configuration
status Check async operation status

deploy (no subcommand)

Build and deploy to the configured target.

cargo pmcp deploy --target aws-lambda
cargo pmcp deploy --target pmcp-run --shared-pool agent-framework

Flow

For AWS Lambda targets, cargo pmcp deploy runs:

  1. Loads .pmcp/deploy.toml via DeployConfig::load.
  2. Validates the [iam] section — runs the same gate as cargo pmcp validate deploy and fails fast before any AWS API call if validation errors are present. Warnings print to stderr but don't block.
  3. Builds the Lambda binary.
  4. Regenerates deploy/lib/stack.ts from the loaded config — splices the [iam] and [metadata] declarations into the CDK template at single seams. Changes to .pmcp/deploy.toml therefore take effect on the next cargo pmcp deploy without manual re-init. Guard: if deploy/lib/stack.ts already exists, it is preserved (the write is skipped and a one-line preserved existing deploy/lib/stack.ts notice prints) so an operator-curated stack is never silently overwritten. Pass --regenerate-stack (alias --force) to overwrite it. A missing file is always scaffolded flag-free.
  5. Runs cdk deploy with --require-approval never.

Read the full file on GitHub · 430 lines

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. 2d ago First seen · 430 lines · 0 tokens per session scan A 49b6a36a6d86

Subscribe to this mod's changes

deploy is a command published in the GitHub repository paiml/rust-mcp-sdk (53 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,446 tokens. 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-30.