terraform-setup
Install (deploy) MCP Gateway & Registry on AWS using the Terraform aws-ecs stack (ECS Fargate, Aurora, DocumentDB, Keycloak). Asks whether you are running from an EC2 instance or a local laptop, confirms the required AWS IAM permissions are in place, clones the repository, bootstraps the toolchain (uv, AWS CLI, Terraform), configures terraform.tfvars, runs the two-stage terraform apply, and completes post-deployment setup. Does NOT create IAM roles itself — it tells you the permissions you need and offers to guide you through setting them up.
npx skills add agentic-community/mcp-gateway-registry --skill terraform-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guided deployment of the MCP Gateway & Registry to AWS via Terraform:
- Confirms deployment environment (EC2 instance vs. local laptop) and implications for AWS credentials
- Confirms required AWS IAM permissions are in place
- Clones the MCP Gateway & Registry repository
- Bootstraps the toolchain:
uv+uv sync(providing the AWS CLI in the project venv), Terraform, and supporting tools - Helps configure
terraform/aws-ecs/terraform.tfvars - Runs
terraform apply(one apply in CloudFront Only mode; two-stage certs-first flow is for custom-domain mode) - Runs automated post-deployment setup and registers the AWS KB MCP server
- Ends with a complete summary of every step taken
By default core services pull pre-built images from public ECR; no image build step is required.
How it works
- The skill starts by performing Step 0, determining RUN_ENV (EC2 or local) and other environment details, and then proceeds only after collecting user input (Step 0 questions).
- It asks for INSTALL_DIR, with a default of ~/mcp-gateway-registry, and expands the path.
- It asks for STORAGE_BACKEND, defaulting to documentdb, and stores as STORAGE_BACKEND (documentdb or external mongodb options).
- It asks for AWS_REGION and validates DocumentDB support if STORAGE_BACKEND is documentdb.
- It asks for ENABLE_OBSERVABILITY; if not chosen, it sets enable_observability = false in terraform.tfvars to avoid missing image URIs.
- It documents deployment mode as CloudFront Only and provides the exact messaging about URLs.
- It requires AWS credentials and IAM permissions as specified in the Phase 1 section and notes whether RUN_ENV is ec2 or local.
- It logs step results in a Phase 0 entry: { 0, "Environment & Mode Selection", DONE, "Env: ${RUN_ENV}, Region: ${AWS_REGION} (DocumentDB-verified), Mode: CloudFront Only, Dir: ${INSTALL_DIR}" }
When to use it
- Use when provisioning MCP Gateway & Registry on AWS via Terraform in ECS Fargate, with optional DocumentDB storage and optional observability.
- Use when you want a guided, stepwise setup that validates environment, IAM permissions, and deployment parameters before applying Terraform.
What it can touch
- It touches Terraform configuration via
terraform/aws-ecs/terraform.tfvarsand controls deployment flow. It requires access to AWS and the repository clone.
Caveats
- The skill does not create IAM roles for the EC2 instance or local user; it instructs you to ensure credentials or an attached instance role exist. If RUN_ENV = ec2, attach an IAM role to the instance; if RUN_ENV = local, configure AWS credentials.
- It warns about cost (roughly $170–330/month in us-east-1) and that running terraform destroy tears it down.
- If STORAGE_BACKEND = documentdb, region must support DocumentDB; otherwise, a region check is performed and non-supported regions are rejected until a supported region is chosen.
- Observability requires building images if enabled; by default, enable_observability is set to false unless you supply/build the two images."
# MCP Gateway & Registry — Terraform (AWS ECS) Install Skill **Repository:** https://github.com/agentic-community/mcp-gateway-registry **This skill:** https://github.com/agentic-community/mcp-gateway-registry/blob/main/.claude/skills/terraform-setup/SKILL.md **Full Terraform guide:** https://github.com/agentic-community/mcp-gateway-registry/blob/main/terraform/aws-ecs/README.md ## How to run this skill without cloning the repository This skill is self-contained. You can invoke it from any directory in Claude Code. It will clone the repository for you. ``` /terraform-setup ``` Or reference it remotely if you have not installed this repo: ``` @https://raw.githubusercontent.com/agentic-community/mcp-gateway-registry/main/.claude/skills/terraform-setup/SKILL.md ``` --- ## What this skill does **`/terraform-setup`** — Guided deployment of the MCP Gateway & Registry to AWS via Terraform: - Confirms where you are running from (EC2 instance vs. local laptop) and what that means for AWS credentials - Confirms the AWS IAM permissions the deployment requires are in place - Clones the MCP Gateway & Registry repository - Bootstraps the toolchain: `uv` + `uv sync` (which provides the AWS CLI in
- How to run this skill without cloning the repository
- What this skill does
- AWS services / resources this deploys (tell the user up front)
- CRITICAL: First action is ALWAYS Step 0
- Step tracking
- Step 0: Determine Environment and Mode — MUST BE FIRST, NO EXCEPTIONS
- Phase 1: AWS Credentials & IAM Permissions (READ THIS CAREFULLY)
- How the requirement applies to YOUR environment
- Verify the current identity
- Phase 2: Prerequisites Check
- Phase 3: Clone Repository and Bootstrap Toolchain
- 3a. Clone (or reuse) the repository
- 3b. Run uv sync (this provides the AWS CLI in the venv)
- 3c. Make the venv AWS CLI usable
echo "Installation directory: ${INSTALL_DIR}"
Run ONLY if STORAGE_BACKEND = documentdb. Needs an AWS CLI (available after Phase 3 uv sync).
if ${AWS} ssm get-parameters-by-path \
echo "DOCDB_SUPPORTED in ${AWS_REGION}"
else
echo "DOCDB_NOT_SUPPORTED in ${AWS_REGION} — pick a different region"
fi
aws sts get-caller-identity 2>&1 || echo "AWS CLI not found yet — it will be available after uv sync (Phase 3). Re-verify then."
echo "=== git ==="; git --version 2>/dev/null && echo "GIT_OK" || echo "GIT_FAIL"
echo "=== Docker ==="; docker --version 2>/dev/null && echo "DOCKER_OK" || echo "DOCKER_FAIL (only needed if building custom images)"What does the terraform-setup skill do?
Install (deploy) MCP Gateway & Registry on AWS using the Terraform aws-ecs stack (ECS Fargate, Aurora, DocumentDB, Keycloak). Asks whether you are running from an EC2 instance or a local laptop, confirms the required AWS IAM permissions are in place, clones the repository, bootstraps the toolchain (uv, AWS CLI, Terraform), configures terraform.tfvars, runs the two-stage terraform apply, and completes post-deployment setup. Does NOT create IAM roles itself — it tells you the permissions you need and offers to guide you through setting them up.
How do I install it?
Run `npx skills add agentic-community/mcp-gateway-registry --skill terraform-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentic-community/mcp-gateway-registry, a repository with 845 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.