Transport Across Environments

Transporting MCP Servers across Org

What Needs to Move

Item	How to Move
Application code	CI/CD pipeline (automatic) — same Docker image, different config
Tool definitions (tools.yaml, manifest.yaml)	Update config in the target environment's deployment
FAISS index	Copy the .faiss file to the target FAISS_INDEX_PATH

Step-by-Step Promotion

Step 1 — Verify all tools work in DEV
         → call tools/list, then tools/call, check responses

Step 2 — Update config.yaml and tools.yaml for the target environment

Step 3 — Deploy via CI/CD pipeline
         → DevOps team handles Docker image promotion (same image, new config)

Step 4 — Copy updated FAISS index to the target environment path
         → match the FAISS_INDEX_PATH set for that environment

Step 5 — Set current_environment in config.yaml to the target (qa or prod)

Step 6 — Run smoke tests
         → call tools/list and verify expected tools appear
         → call tools/call on a key tool and validate the response

Step 7 — Repeat for PROD once QA validation passes

Environment-Specific Items to Update Per Promotion

Config Item	Action
current_environment in config.yaml	Set to qa or prod as appropriate
Backend URLs in config.yaml	Confirm correct base_url per environment under destinations
FAISS_INDEX_PATH env variable	Point to the correct .faiss file for the target env
DB_CONN env variable	Update to target environment's database connection string
API Keys / Auth tokens	Rotate and update per environment's secrets management

---