registry/deploy/README.md

MCP Registry Kubernetes Deployment

This directory contains Pulumi infrastructure code to deploy the MCP Registry service to a Kubernetes cluster. It supports multiple Kubernetes providers: Azure Kubernetes Service (AKS) and local (using existing kubeconfig).

Quick Start

Local Development

Pre-requisites:

• Pulumi CLI installed
• Access to a Kubernetes cluster via kubeconfig. You can run a cluster locally with minikube.

1. Set Pulumi's backend to local: pulumi login --local
2. Init the local stack: pulumi stack init local (fine to leave password blank)
3. Set your config:

   # General environment
   pulumi config set mcp-registry:environment local
   
   # To use your local kubeconfig (default)
   pulumi config set mcp-registry:provider local
   # Alternative: To use AKS
   # pulumi config set mcp-registry:provider aks
   
   # GitHub OAuth
   pulumi config set mcp-registry:githubClientId <your-github-client-id>
   pulumi config set --secret mcp-registry:githubClientSecret <your-github-client-secret>
   

4. Deploy: go build && PULUMI_CONFIG_PASSPHRASE="" pulumi up --yes
5. Access the repository via the ingress load balancer. You can find its external IP with kubectl get svc nginx-ingress-ingress-nginx-controller -n ingress-nginx (with minikube, if it's 'pending' you might need minikube tunnel). Then run curl -H "Host: mcp-registry-local.example.com" -k https://<EXTERNAL-IP>/v0/ping to check that the service is up.

Production Deployment (AKS)

Note: This is how the production deployment will be set up once. But then the plan will be future updates are effectively a login + pulumi up from GitHub Actions.

Pre-requisites:

• Pulumi CLI installed
• A Microsoft Azure account
• Azure CLI installed

1. Login to Azure: az login
2. Create a resource group: az group create --name official-mcp-registry-prod --location eastus
3. Add the storage resource provider: az provider register --namespace Microsoft.Storage
4. Create a storage account: az storage account create --name officialmcpregistryprod --resource-group official-mcp-registry-prod --location eastus --sku Standard_LRS
5. Add the 'Storage Blob Data Contributor' role assignment for yourself on the storage account: az role assignment create --assignee $(az ad signed-in-user show --query id -o tsv) --role "Storage Blob Data Contributor" --scope "/subscriptions/$(az account show --query id -o tsv)/resourceGroups/official-mcp-registry-prod"
6. Create a container: az storage container create --name pulumi-state --account-name officialmcpregistryprod
7. Set Pulumi's backend to Azure: pulumi login 'azblob://pulumi-state?storage_account=officialmcpregistryprod'
8. Init the production stack: pulumi stack init prod

• TODO: This has a password that maybe needs to be shared with select contributors?

9. Deploy: go build && PULUMI_CONFIG_PASSPHRASE="" pulumi up --yes
10. Access the repository via the ingress load balancer. You can find its external IP with kubectl get svc nginx-ingress-ingress-nginx-controller -n ingress-nginx or view it in the Pulumi outputs. Then run curl -H "Host: mcp-registry-prod.example.com" -k https://<EXTERNAL-IP>/v0/ping to check that the service is up.

Structure

├── main.go              # Pulumi program entry point
├── Pulumi.yaml          # Project configuration
├── Pulumi.local.yaml    # Local stack configuration
├── Pulumi.prod.yaml     # Production stack configuration
├── Makefile             # Build and deployment targets
├── go.mod               # Go module dependencies
├── go.sum               # Go module checksums
└── pkg/                 # Infrastructure packages
    ├── k8s/             # Kubernetes deployment components
    │   ├── cert_manager.go    # SSL certificate management
    │   ├── deploy.go          # Deployment orchestration
    │   ├── ingress.go         # Ingress controller setup
    │   ├── mongodb.go         # MongoDB deployment
    │   └── registry.go        # MCP Registry deployment
    └── providers/       # Kubernetes cluster providers
        ├── types.go           # Provider interface definitions
        ├── aks/               # Azure Kubernetes Service provider
        └── local/             # Local kubeconfig provider

Architecture Overview

Deployment Flow

1. Pulumi program starts in main.go
2. Configuration is loaded from Pulumi config files
3. Provider factory creates appropriate cluster provider (AKS or local)
4. Cluster provider sets up Kubernetes access
5. k8s.DeployAll() orchestrates complete deployment:
   • Certificate manager for SSL/TLS
   • Ingress controller for external access
   • MongoDB for data persistence
   • MCP Registry application

Configuration

Parameter	Description	Required
environment	Deployment environment (dev/prod)	Yes
provider	Kubernetes provider (local/aks)	No (default: local)
githubClientId	GitHub OAuth Client ID	Yes
githubClientSecret	GitHub OAuth Client Secret	Yes

Troubleshooting

Check Status

kubectl get pods
kubectl get deployment
kubectl get svc
kubectl get ingress
kubectl get svc -n ingress-nginx

View Logs

kubectl logs -l app=mcp-registry
kubectl logs -l app=mongodb