Skip to content

Management Overview

This section provides operational guidance for running and maintaining a production instance of MCP Gateway.

Whether you're self-hosting, running in the cloud, or deploying to Kubernetes, this section helps you monitor, back up, and maintain the system.


🧭 What's Covered

Page Description
Backups How to persist and restore your database, configs, and resource state
Export & Import Complete configuration management with CLI, API, and Admin UI
Export/Import Tutorial Step-by-step tutorial for getting started with export/import
Export/Import Reference Quick reference guide for export/import commands and APIs
Bulk Import Import multiple tools at once for migrations and team onboarding
Metadata Tracking πŸ“Š NEW - Comprehensive audit trails and entity metadata tracking
Well-Known URIs Configure robots.txt, security.txt, and custom well-known files
Logging Configure structured logging, log destinations, and log rotation

πŸ” Runtime Config via .env

Most operational settings (logging level, database pool size, auth mode) are controlled through .env or environment variables.

Update the file and restart the container or process to apply changes.


πŸ§ͺ Health & Readiness

Expose the /health endpoint for use with:

  • Cloud load balancer health checks
  • Kubernetes probes
  • CI/CD smoke tests

Sample check:

curl http://localhost:4444/health

Expected response:

{ "status": "healthy"}

πŸ” Service Restart Commands

Depending on your environment:

  • docker restart mcpgateway
  • kubectl rollout restart deployment/mcpgateway