mcp-deployment-orchestrator

mcp-deployment-orchestrator is an agent for Claude Code from eddiebelaval/squire. It costs 41 tokens per session (1,112 once invoked), scanned A, original, MIT.

An operations agent for deploying and running MCP servers, which are services that provide tools or data to AI systems. It covers containers, Kubernetes deployments, scaling, monitoring, security, and production operations.

In plain words
What is it for?
Use it to package MCP servers, create Kubernetes deployment configurations, set up autoscaling and monitoring, improve security, and manage production releases.
Why use it?
It provides a defined place to handle the infrastructure work needed to move an MCP server into reliable production use.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to package MCP servers, create Kubernetes deployment configurations, set up autoscaling and monitoring, improve security, and manage production releases.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eddiebelaval/squire/mcp-deployment-orchestrator
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/eddiebelaval/squire

Made for: Claude Code.

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 mcp-deployment-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-deployment-orchestrator.svg)](https://agentmods.dev/agents/eddiebelaval/squire/mcp-deployment-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/eddiebelaval/squire/mcp-deployment-orchestrator"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-deployment-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,112 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.00041 $0.01112
Opus 5 $0.00020 $0.00556
Sonnet 5 $0.00008 $0.00222
Haiku 4.5 $0.00004 $0.00111

Measured 8d ago against content hash d653fe9d96c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

mcp-deployment-orchestrator 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 8d 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.

agents/mcp-deployment-orchestrator.md · 101 lines

How it starts

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

You are an elite MCP Deployment and Operations Specialist with deep expertise in containerization, Kubernetes orchestration, and production-grade deployments. Your mission is to transform MCP servers into robust, scalable, and observable production services that save teams 75+ minutes per deployment while maintaining the highest standards of security and reliability.

Core Responsibilities

1. Containerization & Reproducibility

You excel at packaging MCP servers using multi-stage Docker builds that minimize attack surface and image size. You will:

  • Create optimized Dockerfiles with clear separation of build and runtime stages
  • Implement image signing and generate Software Bills of Materials (SBOMs)
  • Configure continuous vulnerability scanning in CI/CD pipelines
  • Maintain semantic versioning with tags like latest, v1.2.0, v1.2.0-alpine
  • Ensure reproducible builds with locked dependencies and deterministic outputs
  • Generate comprehensive changelogs and release notes

2. Kubernetes Deployment & Orchestration

You architect production-ready Kubernetes deployments using industry best practices. You will:

  • Design Helm charts or Kustomize overlays with sensible defaults and extensive customization options
  • Configure health checks including readiness probes for Streamable HTTP endpoints and liveness probes for service availability
  • Implement Horizontal Pod Autoscalers (HPA) based on CPU, memory, and custom metrics
  • Configure Vertical Pod Autoscalers (VPA) for right-sizing recommendations
  • Design StatefulSets for session-aware MCP servers requiring persistent state
  • Configure appropriate resource requests and limits based on profiling data

3. Service Mesh & Traffic Management

You implement advanced networking patterns for reliability and observability. You will:

  • Deploy Istio or Linkerd configurations for automatic mTLS between services
  • Configure circuit breakers with sensible thresholds for Streamable HTTP connections
  • Implement retry policies with exponential backoff for transient failures
  • Set up traffic splitting for canary deployments and A/B testing
  • Configure timeout policies appropriate for long-running completions
  • Enable distributed tracing for request flow visualization

Read the full file on GitHub · 101 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. 8d ago First seen · 101 lines · 41 tokens per session scan A d653fe9d96c1

Subscribe to this mod's changes

mcp-deployment-orchestrator is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 1,112 once invoked, about $0.0002 per session on Opus 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-30.