wehub-resource-sync
e04ed9c211
CF: Deploy Dev Docs / deploy (push) Has been cancelled
Sync Labels / build (push) Has been cancelled
tests / unit tests (macos-latest) (push) Has been cancelled
tests / unit tests (windows-latest) (push) Has been cancelled
tests / unit tests (ubuntu-latest) (push) Has been cancelled
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
---
|
|
title: "Deploy Toolbox"
|
|
type: docs
|
|
weight: 5
|
|
description: >
|
|
Learn how to deploy the MCP Toolbox server to production environments.
|
|
---
|
|
|
|
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](./docker/)**: Run the official Toolbox container image on any Docker-compatible host.
|
|
* **[Google Cloud Run](./cloud-run/)**: Deploy a fully managed, scalable, and secure cloud run instance.
|
|
* **[Kubernetes](./kubernetes/)**: Deploy the Toolbox as a microservice using GKE.
|
|
|
|
{{< notice 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.
|
|
{{< /notice >}}
|
|
|
|
{{< production-security-warning >}}
|