deploy-mcp

deploy-mcp is a skill for Claude Code from futuresearch/futuresearch-python. It costs 58 tokens per session (1,404 once invoked), scanned A, original, MIT.

A guide for deploying the FutureSearch MCP server to staging or production on Google Kubernetes Engine, Google's managed Kubernetes service. It covers releases, rollbacks, scaling, and deployment checks.

In plain words
What is it for?
Use it to deploy, redeploy, roll back, scale, monitor, or check the status of the FutureSearch MCP server.
Why use it?
It provides repeatable commands and checks for moving the MCP server between environments and confirming that its containers are running.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

Part of the futuresearch plugin — 4 skills shipped together

Good fit Use it to deploy, redeploy, roll back, scale, monitor, or check the status of the FutureSearch MCP server.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/futuresearch/futuresearch-python/deploy-mcp
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.

Any agent
npx skills add futuresearch/futuresearch-python --skill deploy-mcp
Clone the repo
git clone --depth 1 https://github.com/futuresearch/futuresearch-python

Made for: Claude Code.

Or install futuresearch, the plugin that ships this one along with the rest of its 4 skills.

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 deploy-mcp

README.md
[![agentmods](https://agentmods.dev/badge/skills/futuresearch/futuresearch-python/deploy-mcp/github.svg)](https://agentmods.dev/skills/futuresearch/futuresearch-python/deploy-mcp)
Your own site
<a href="https://agentmods.dev/skills/futuresearch/futuresearch-python/deploy-mcp"><img src="https://agentmods.dev/badge/skills/futuresearch/futuresearch-python/deploy-mcp/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 deploy-mcp

Your own site · 80×15
<a href="https://agentmods.dev/skills/futuresearch/futuresearch-python/deploy-mcp"><img src="https://agentmods.dev/badge/skills/futuresearch/futuresearch-python/deploy-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,404 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00058 $0.01404
Opus 5.5 $0.00023 $0.00562
Sonnet 5.5 $0.00012 $0.00281
Haiku 4.5 $0.00006 $0.00140

Measured 4d ago against content hash 680530094a0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-mcp 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 4d 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.

.claude/skills/deploy-mcp/SKILL.md · 143 lines

How it starts

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

Deploying the MCP Server

Deploying more than just the MCP server? Start from the deploy-to-staging skill (repo root .claude/skills/) — it routes a change through every layer of the stack in dependency order. This skill owns only the MCP layer.

Quick Deploy

Staging (from main)

gh workflow run "Deploy MCP Server" -f branch=main -f deploy_staging=true

Production (from main)

gh workflow run "Deploy MCP Server" -f branch=main -f deploy_production=true

Both environments

gh workflow run "Deploy MCP Server" -f branch=main -f deploy_staging=true -f deploy_production=true

From a feature branch

gh workflow run "Deploy MCP Server" -f branch=feat/my-branch -f deploy_staging=true

Monitoring a Deploy

# Watch the workflow run
gh run list --workflow="Deploy MCP Server" --limit 3
gh run watch <run-id>

# Check pod rollout
kubectl rollout status deploy/futuresearch-mcp-staging -n futuresearch-mcp-staging --timeout=5m

# Verify pods are running
kubectl get pods -n futuresearch-mcp-staging -o wide

How It Works

The GitHub Actions workflow (.github/workflows/deploy-mcp.yaml) does:

  1. Checks — ruff lint + pytest on the target branch
  2. Build & push — Docker image to GAR, tagged with short SHA (+ latest on main)
  3. Deploy — Helm upgrade with layered values:
    • values.yaml — base config
    • values.staging.yaml — staging overrides (MCP_SERVER_URL, REDIS_DB, replicaCount, host)
    • values.secrets.staging.yaml — SOPS-decrypted secrets (Supabase, API keys)

The deploy uses --atomic so it auto-rolls back on failure.

Scaling Replicas

Via Helm values (persistent)

Edit futuresearch-mcp/deploy/chart/values.staging.yaml:

replicaCount: 2  # Change this

Commit, push, and redeploy.

Via kubectl (temporary, resets on next deploy)

# Staging
kubectl scale deploy futuresearch-mcp-staging -n futuresearch-mcp-staging --replicas=3

# Take offline
kubectl scale deploy futuresearch-mcp-staging -n futuresearch-mcp-staging --replicas=0

Read the full file on GitHub · 143 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. 4d ago Changed 680530094a0f
  2. 1mo ago First seen · 143 lines · 58 tokens per session scan A 36d444280669

Subscribe to this mod's changes

deploy-mcp is a skill published in the GitHub repository futuresearch/futuresearch-python (57 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 1,404 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

deploy-from-stale-worktree-silent-rollback

Diagnose "I deployed a new Cloud Run / Docker image but a bunch of recently merged fixes regressed in production." Use when: (1) the deploy script does gcloud builds submit ... "${SCRIPTDIR}" or docker build (build context = local filesystem, NOT a git ref), (2) the user has many git worktrees / multiple checkouts of…

wan-huiyan/agent-traffic-control · 405 tokens

kubernetes-architect

Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration.

ushibo/brigade · 31 tokens

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…

microsoft/skills · 166 tokens

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…

microsoft/skills · 106 tokens

deploy-gen

Generate deployment configurations (Docker, Kubernetes) for the current project.

jmagly/aiwg · 15 tokens

scaffold

Provisioning infrastructure via cloud IaC (Terraform/OpenTofu/CloudFormation/Pulumi) and local dev environments (Docker Compose, env vars). Use for IaC design or multi-cloud provisioning.

simota/agent-skills · 43 tokens