deploy-mcp

Deploy and manage the everyrow MCP server across Kubernetes environments.

51|6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/futuresearch/everyrow-sdk --skill deploy-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-mcp
Source: https://github.com/futuresearch/everyrow-sdk/tree/main/.claude/skills/deploy-mcp
Command: npx skills add https://github.com/futuresearch/everyrow-sdk --skill deploy-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables reliable, repeatable deployment, redeployment, rollback, scaling, and status checks for the everyrow MCP server so teams can move changes to staging and production with confidence and minimal manual toil.

Core Features & Use Cases

  • GitHub Actions-driven CI/CD: Run checks, build and push Docker images, and trigger Helm upgrades from a workflow.
  • Atomic Helm upgrades & rollbacks: Perform atomic Helm upgrades that auto-rollback on failure and inspect history for troubleshooting.
  • Secrets & scaling management: Update SOPS-encrypted secrets, scale replicas temporarily via kubectl or persistently via Helm values, and monitor pod rollout and workflow status.
  • Use Case: Merge a PR to main, then run the Deploy MCP Server workflow to build, push, and release a new image to staging, verify rollout, and optionally promote to production.

Quick Start

Trigger the Deploy MCP Server GitHub Actions workflow on main with deploy_staging=true to perform a staging deploy.

Frequently Asked Questions about deploy-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Docker image to GKE using GitHub Actions and Helm?

To deploy a Docker image to GKE using GitHub Actions and Helm, trigger a workflow that builds and pushes the image to a registry, then performs an atomic Helm upgrade with auto-rollback on failure for safe staging and production releases.

What is an atomic Helm upgrade and how does it handle deployment failures?

An atomic Helm upgrade applies changes to Kubernetes and automatically rolls back to the previous state if the deployment fails, preventing broken releases from affecting staging or production environments.

Can I manage SOPS-encrypted secrets and scale replicas with kubectl in a CI/CD pipeline?

Yes, you can update SOPS-encrypted secrets and scale replicas using kubectl within GitHub Actions workflows, scaling temporarily via kubectl or persistently by updating Helm values.

How do I rollback a Kubernetes deployment and inspect Helm history for troubleshooting?

You can rollback a Kubernetes deployment and inspect Helm history for troubleshooting by triggering the rollback action in your GitHub Actions workflow, which reverts to a previous stable release.

Does this deployment workflow support monitoring pod rollout and workflow status?

Yes, the deployment workflow supports monitoring pod rollout and workflow status, verifying the Kubernetes rollout after a Helm upgrade and tracking the GitHub Actions workflow status.