Learn how to deploy the MCP Toolbox server to production environments.
2 minute read
Once you have tested your MCP Toolbox configuration locally, you can deploy the server to a highly available, production-ready environment.
Choose your preferred deployment platform below to get started:
Docker: Run the official Toolbox container image on any Docker-compatible host.
Google Cloud Run: Deploy a fully managed, scalable, and secure cloud run instance.
Kubernetes: Deploy the Toolbox as a microservice using GKE.
Tip
Production Security: When moving to production, never hardcode passwords or
API keys directly into your tools.yaml. Always use environment variable
substitution and inject those values securely through your deployment platform’s
secret manager.
To enable HTTPS, you must provide a valid pair of --tls-cert and --tls-key
files; specifying only one will cause the server to fail at startup.
⚠️ Production Security Warning
Secure your deployment: By default, Toolbox uses HTTP
and runs on all hosts (--allowed-hosts) and all origins
(--allowed-origins). While convenient, this is
insecure and could expose you to unauthorized access of
your toolbox instances. Please review the example under reference/cli to
secure your instances.
Note: The server issues a warning in the logs if these are set to the wildcard *.
Prevent DNS Rebinding: Use the --allowed-hosts flag to specify a list of hosts for validation.