diff --git a/docs/toolhive/_partials/_client-compat-table.md b/docs/toolhive/_partials/_client-compat-table.md deleted file mode 100644 index cdbf42ae..00000000 --- a/docs/toolhive/_partials/_client-compat-table.md +++ /dev/null @@ -1,25 +0,0 @@ -| Client | Supported | Auto-configuration | Notes | -| -------------------------- | :-------: | :----------------: | ------------------------------------------- | -| GitHub Copilot (VS Code) | ✅ | ✅ | v1.102+ or Insiders version ([see note][3]) | -| Cursor | ✅ | ✅ | v0.50.0+ | -| Roo Code (VS Code) | ✅ | ✅ | v3.19.2+ | -| Cline (VS Code) | ✅ | ✅ | v3.17.10+ | -| Claude Code CLI | ✅ | ✅ | v1.0.27+ | -| Windsurf IDE | ✅ | ✅ | | -| Windsurf (JetBrains) | ✅ | ✅ | | -| Sourcegraph Amp CLI | ✅ | ✅ | | -| Sourcegraph Amp (VS Code) | ✅ | ✅ | | -| Sourcegraph Amp (Cursor) | ✅ | ✅ | | -| Sourcegraph Amp (Windsurf) | ✅ | ✅ | | -| LM Studio | ✅ | ✅ | v0.3.17+ | -| Goose | ✅ | ✅ | | -| GitHub Copilot (JetBrains) | ✅ | ❌ | v1.5.47+ | -| Continue (VS Code) | ✅ | ❌ | v1.0.14+ | -| Continue (JetBrains) | ✅ | ❌ | v1.0.23+ | -| PydanticAI | ✅ | ❌ | v0.2.18+ | -| ChatGPT Desktop | ✅ | ❌ | v0.2.7+ ([see note][4]) | -| Claude Desktop | ✅ | ❌ | v0.2.7+ ([see note][4]) | -| Kiro | ✅ | ❌ | v0.2.7+ ([see note][4]) | - -[3]: /toolhive/reference/client-compatibility.mdx#vs-code-with-copilot -[4]: /toolhive/reference/client-compatibility#stdio-only-client-configuration diff --git a/docs/toolhive/_partials/_remote-mcp-auth-examples.md b/docs/toolhive/_partials/_remote-mcp-auth-examples.mdx similarity index 100% rename from docs/toolhive/_partials/_remote-mcp-auth-examples.md rename to docs/toolhive/_partials/_remote-mcp-auth-examples.mdx diff --git a/docs/toolhive/concepts/mcp-primer.md b/docs/toolhive/concepts/mcp-primer.mdx similarity index 100% rename from docs/toolhive/concepts/mcp-primer.md rename to docs/toolhive/concepts/mcp-primer.mdx diff --git a/docs/toolhive/concepts/observability.md b/docs/toolhive/concepts/observability.mdx similarity index 99% rename from docs/toolhive/concepts/observability.md rename to docs/toolhive/concepts/observability.mdx index 1c4faea7..2de69a3b 100644 --- a/docs/toolhive/concepts/observability.md +++ b/docs/toolhive/concepts/observability.mdx @@ -420,7 +420,7 @@ Now that you understand how ToolHive's observability works, you can: 2. **Follow the tutorial** to set up a local observability stack with [OpenTelemetry, Jaeger, Prometheus, and Grafana](../tutorials/opentelemetry.mdx) 3. **Enable telemetry** when running your servers: - - [using the ToolHive CLI](../guides-cli/telemetry-and-metrics.md) + - [using the ToolHive CLI](../guides-cli/telemetry-and-metrics.mdx) - using the Kubernetes operator (not yet supported - [contributions welcome](https://github.com/stacklok/toolhive/releases/tag/v0.2.0)) 4. **Set up basic dashboards** to track request rates, error rates, and response diff --git a/docs/toolhive/concepts/registry-criteria.md b/docs/toolhive/concepts/registry-criteria.mdx similarity index 100% rename from docs/toolhive/concepts/registry-criteria.md rename to docs/toolhive/concepts/registry-criteria.mdx diff --git a/docs/toolhive/faq.md b/docs/toolhive/faq.mdx similarity index 98% rename from docs/toolhive/faq.md rename to docs/toolhive/faq.mdx index 49e3029e..5145fc69 100644 --- a/docs/toolhive/faq.md +++ b/docs/toolhive/faq.mdx @@ -144,7 +144,7 @@ ToolHive supports: ### How do I get my MCP server added to the ToolHive registry? The ToolHive registry has specific -[inclusion criteria](./concepts/registry-criteria.md), such as being open +[inclusion criteria](./concepts/registry-criteria.mdx), such as being open source, following good security practices, and maintaining code quality. Review the criteria and [submit your server for consideration](https://github.com/stacklok/toolhive/issues/new?template=add-an-mcp-server.md). diff --git a/docs/toolhive/guides-cli/advanced-cicd.mdx b/docs/toolhive/guides-cli/advanced-cicd.mdx index 36d619f7..f803324f 100644 --- a/docs/toolhive/guides-cli/advanced-cicd.mdx +++ b/docs/toolhive/guides-cli/advanced-cicd.mdx @@ -1,5 +1,5 @@ --- -title: Advanced CI/CD with ToolHive +title: Advanced CI/CD patterns description: Advanced CI/CD patterns for building and deploying MCP server containers with ToolHive. diff --git a/docs/toolhive/guides-cli/api-server.md b/docs/toolhive/guides-cli/api-server.mdx similarity index 100% rename from docs/toolhive/guides-cli/api-server.md rename to docs/toolhive/guides-cli/api-server.mdx diff --git a/docs/toolhive/guides-cli/build-containers.mdx b/docs/toolhive/guides-cli/build-containers.mdx index 84fbed12..fc077187 100644 --- a/docs/toolhive/guides-cli/build-containers.mdx +++ b/docs/toolhive/guides-cli/build-containers.mdx @@ -1,5 +1,5 @@ --- -title: Build MCP server containers +title: Build MCP containers description: How to build MCP server containers without running them using the ToolHive CLI. diff --git a/docs/toolhive/guides-cli/custom-permissions.mdx b/docs/toolhive/guides-cli/custom-permissions.mdx index 9768ca97..2fa313fa 100644 --- a/docs/toolhive/guides-cli/custom-permissions.mdx +++ b/docs/toolhive/guides-cli/custom-permissions.mdx @@ -19,7 +19,7 @@ in a single profile. Permission profiles control two types of access: - **Host file system access** specifies paths on your host that are mounted into - the MCP server container — see [file system access](./filesystem-access.md) + the MCP server container — see [file system access](./filesystem-access.mdx) for detailed examples - **Network access rules** let you restrict outbound HTTP(S) connectivity from the MCP server — see [network isolation](./network-isolation.mdx) for @@ -189,7 +189,7 @@ This profile grants file system access without defining any network permissions. (Note, to actually block network access, use the `--isolate-network` flag when running the server.) -See [file system access](./filesystem-access.md) for more details and specific +See [file system access](./filesystem-access.mdx) for more details and specific examples. ## Apply a permission profile @@ -233,5 +233,5 @@ When creating and using permission profiles: - [`thv run` command reference](../reference/cli/thv_run.md) - [Run MCP servers](./run-mcp-servers.mdx) -- [File system access](./filesystem-access.md) +- [File system access](./filesystem-access.mdx) - [Network isolation](./network-isolation.mdx) diff --git a/docs/toolhive/guides-cli/filesystem-access.md b/docs/toolhive/guides-cli/filesystem-access.mdx similarity index 100% rename from docs/toolhive/guides-cli/filesystem-access.md rename to docs/toolhive/guides-cli/filesystem-access.mdx diff --git a/docs/toolhive/guides-cli/group-management.md b/docs/toolhive/guides-cli/group-management.mdx similarity index 98% rename from docs/toolhive/guides-cli/group-management.md rename to docs/toolhive/guides-cli/group-management.mdx index 7a47eaa8..43d36553 100644 --- a/docs/toolhive/guides-cli/group-management.md +++ b/docs/toolhive/guides-cli/group-management.mdx @@ -1,5 +1,5 @@ --- -title: Group MCP servers +title: Organize servers into groups description: How to organize MCP servers into logical groups and configure client access. --- diff --git a/docs/toolhive/guides-cli/install.mdx b/docs/toolhive/guides-cli/install.mdx index 61f18daf..f610a639 100644 --- a/docs/toolhive/guides-cli/install.mdx +++ b/docs/toolhive/guides-cli/install.mdx @@ -314,7 +314,7 @@ To uninstall ToolHive: ## Next steps Now that you have ToolHive installed, you can start using it to run and manage -MCP servers. See [Explore the registry](./registry.md) and +MCP servers. See [Explore the registry](./registry.mdx) and [Run MCP servers](./run-mcp-servers.mdx) to get started. ## Related information diff --git a/docs/toolhive/guides-cli/manage-mcp-servers.md b/docs/toolhive/guides-cli/manage-mcp-servers.mdx similarity index 98% rename from docs/toolhive/guides-cli/manage-mcp-servers.md rename to docs/toolhive/guides-cli/manage-mcp-servers.mdx index 10a4e538..92aa0623 100644 --- a/docs/toolhive/guides-cli/manage-mcp-servers.md +++ b/docs/toolhive/guides-cli/manage-mcp-servers.mdx @@ -1,5 +1,5 @@ --- -title: Monitor and manage MCP servers +title: Manage servers description: How to monitor and manage the lifecycle of MCP servers using ToolHive. --- @@ -146,4 +146,4 @@ This will always prompt for re-authentication, even if valid tokens exist. - [`thv stop` command reference](../reference/cli/thv_stop.md) - [`thv restart` command reference](../reference/cli/thv_restart.md) - [`thv rm` command reference](../reference/cli/thv_rm.md) -- [Monitor with OpenTelemetry](../guides-cli/telemetry-and-metrics.md) +- [Monitor with OpenTelemetry](../guides-cli/telemetry-and-metrics.mdx) diff --git a/docs/toolhive/guides-cli/network-isolation.mdx b/docs/toolhive/guides-cli/network-isolation.mdx index 7de07562..2375ba07 100644 --- a/docs/toolhive/guides-cli/network-isolation.mdx +++ b/docs/toolhive/guides-cli/network-isolation.mdx @@ -323,7 +323,7 @@ default behavior of allowing traffic only from the container's own hostname, - [`thv run` command reference](../reference/cli/thv_run.md) - [Run MCP servers](./run-mcp-servers.mdx) - [Custom permissions](./custom-permissions.mdx) -- [File system access](./filesystem-access.md) +- [File system access](./filesystem-access.mdx) ## Troubleshooting diff --git a/docs/toolhive/guides-cli/registry.md b/docs/toolhive/guides-cli/registry.mdx similarity index 99% rename from docs/toolhive/guides-cli/registry.md rename to docs/toolhive/guides-cli/registry.mdx index 258ab4fc..3ef595c2 100644 --- a/docs/toolhive/guides-cli/registry.md +++ b/docs/toolhive/guides-cli/registry.mdx @@ -5,7 +5,7 @@ description: How to use the built-in registry to find MCP servers. ToolHive includes a built-in registry of MCP servers with verified configurations that meet a -[minimum quality standard](../concepts/registry-criteria.md), allowing you to +[minimum quality standard](../concepts/registry-criteria.mdx), allowing you to discover and deploy high-quality tools effortlessly. Simply select one from the list and run it securely with a single command. @@ -194,7 +194,7 @@ configurations. :::note -Registry groups are different from [runtime groups](./group-management.md). +Registry groups are different from [runtime groups](./group-management.mdx). Registry groups organize server definitions within registry files, while runtime groups organize running server instances for access control. diff --git a/docs/toolhive/guides-cli/run-mcp-servers.mdx b/docs/toolhive/guides-cli/run-mcp-servers.mdx index 40b47479..efb910c0 100644 --- a/docs/toolhive/guides-cli/run-mcp-servers.mdx +++ b/docs/toolhive/guides-cli/run-mcp-servers.mdx @@ -9,7 +9,7 @@ server settings, and run custom servers using Docker images or protocol schemes. ## Run a server from the registry -To run an MCP server from the [ToolHive registry](./registry.md), use the +To run an MCP server from the [ToolHive registry](./registry.mdx), use the [`thv run`](../reference/cli/thv_run.md) command with the name of the server you want to run. The server name is the same as its name in the registry. @@ -67,7 +67,7 @@ Use `thv search ` or `thv registry list` to discover available servers. ### Run registry groups -If you use a [custom registry](./registry.md#use-a-custom-registry) that +If you use a [custom registry](./registry.mdx#use-a-custom-registry) that includes groups, you can run multiple related servers together as a unit. This is useful when you need several servers for a specific workflow or project: @@ -83,7 +83,7 @@ thv group run dev-toolkit Running a group starts all servers defined within that group simultaneously, saving you from running each server individually. See -[Registry groups](./registry.md#organize-servers-with-registry-groups) for more +[Registry groups](./registry.mdx#organize-servers-with-registry-groups) for more information about organizing servers into groups in your custom registry. :::info[What's happening?] @@ -185,8 +185,8 @@ The group must exist before you can run a server in it. ::: -See [Group management](./group-management.md) for more details on organizing -servers into groups and configuring client access. +See [Organize servers with groups](./group-management.mdx) to learn more about +organizing servers and configuring client access. ### Mount a local file or directory @@ -194,9 +194,9 @@ To enable file system access for an MCP server, you can either use the `--volume` flag to mount specific paths or create a custom permission profile that defines read and write permissions. -See [File system access](./filesystem-access.md) for detailed examples. To +See [File system access](./filesystem-access.mdx) for detailed examples. To prevent sensitive files from being exposed when mounting a project, use -[.thvignore](./thvignore.md). +[.thvignore](./thvignore.mdx). ### Restrict network access @@ -451,6 +451,9 @@ When you use a protocol scheme, ToolHive: ::: +To build the image without running it, see +[Build MCP containers](./build-containers.mdx). + #### Examples @@ -814,7 +817,7 @@ The configuration file must contain all server settings. ## Next steps -See [Monitor and manage MCP servers](./manage-mcp-servers.md) to monitor and +See [Monitor and manage MCP servers](./manage-mcp-servers.mdx) to monitor and control your servers. ## Related information @@ -823,7 +826,7 @@ control your servers. - [Client configuration](./client-configuration.mdx) - [Secrets management](./secrets-management.mdx) - [Custom permissions](./custom-permissions.mdx) -- [File system access](./filesystem-access.md) +- [File system access](./filesystem-access.mdx) - [Network isolation](./network-isolation.mdx) ## Troubleshooting @@ -887,7 +890,7 @@ If a server crashes or exits unexpectedly: If a remote MCP server authentication fails: 1. Check the server logs for authentication errors (see - [View server logs](./manage-mcp-servers.md#view-server-logs) for the correct + [View server logs](./manage-mcp-servers.mdx#view-server-logs) for the correct log file path on your platform) 2. Verify the issuer URL is correct and accessible diff --git a/docs/toolhive/guides-cli/telemetry-and-metrics.md b/docs/toolhive/guides-cli/telemetry-and-metrics.mdx similarity index 99% rename from docs/toolhive/guides-cli/telemetry-and-metrics.md rename to docs/toolhive/guides-cli/telemetry-and-metrics.mdx index 576368c9..84d76a77 100644 --- a/docs/toolhive/guides-cli/telemetry-and-metrics.md +++ b/docs/toolhive/guides-cli/telemetry-and-metrics.mdx @@ -15,7 +15,7 @@ Datadog, and Grafana Cloud, or expose Prometheus metrics locally. ToolHive's telemetry captures detailed information about MCP interactions including traces, metrics, and performance data. For a comprehensive overview of the telemetry architecture, metrics collection, and monitoring capabilities, see -the [observability overview](../concepts/observability.md). +the [observability overview](../concepts/observability.mdx). ## Enable telemetry @@ -324,7 +324,7 @@ Telemetry adds minimal overhead when properly configured: - Tutorial: [Collect telemetry for MCP workloads](../tutorials/opentelemetry.mdx) -- [Telemetry and monitoring concepts](../concepts/observability.md) +- [Telemetry and monitoring concepts](../concepts/observability.mdx) - [`thv run` command reference](../reference/cli/thv_run.md) - [Run MCP servers](run-mcp-servers.mdx) diff --git a/docs/toolhive/guides-cli/thvignore.md b/docs/toolhive/guides-cli/thvignore.mdx similarity index 97% rename from docs/toolhive/guides-cli/thvignore.md rename to docs/toolhive/guides-cli/thvignore.mdx index ae481c36..90f50ba3 100644 --- a/docs/toolhive/guides-cli/thvignore.md +++ b/docs/toolhive/guides-cli/thvignore.mdx @@ -1,5 +1,5 @@ --- -title: Hide sensitive files with .thvignore +title: Hide sensitive files description: Use .thvignore to prevent secrets from leaking into MCP containers while keeping fast bind mounts for development. @@ -130,7 +130,7 @@ example, `.env*`, build artifacts) in your project's local `.thvignore`. ## Related information -- [File system access](./filesystem-access.md) +- [File system access](./filesystem-access.mdx) - [Run MCP servers](./run-mcp-servers.mdx) - [Network isolation](./network-isolation.mdx) - [`thv run` command reference](../reference/cli/thv_run.md) diff --git a/docs/toolhive/guides-k8s/tool-config.mdx b/docs/toolhive/guides-k8s/customize-tools.mdx similarity index 98% rename from docs/toolhive/guides-k8s/tool-config.mdx rename to docs/toolhive/guides-k8s/customize-tools.mdx index c5668359..d78939de 100644 --- a/docs/toolhive/guides-k8s/tool-config.mdx +++ b/docs/toolhive/guides-k8s/customize-tools.mdx @@ -1,5 +1,5 @@ --- -title: Configure tools for MCP servers on Kubernetes +title: Customize tools description: Filter and rename MCP server tools using the MCPToolConfig CRD and toolConfigRef. @@ -209,7 +209,7 @@ kubectl -n toolhive-system get mcpserver github -o yaml - If an MCPServer references a missing MCPToolConfig, the server enters Failed and the controller logs include the missing name and namespace. -## Related +## Related information - See the [Kubernetes CRD reference](../reference/crd-spec.mdx) for the full MCPToolConfig and MCPServerSpec schemas. diff --git a/docs/toolhive/guides-k8s/deploy-operator-helm.md b/docs/toolhive/guides-k8s/deploy-operator-helm.mdx similarity index 98% rename from docs/toolhive/guides-k8s/deploy-operator-helm.md rename to docs/toolhive/guides-k8s/deploy-operator-helm.mdx index f562bd43..88475dbc 100644 --- a/docs/toolhive/guides-k8s/deploy-operator-helm.md +++ b/docs/toolhive/guides-k8s/deploy-operator-helm.mdx @@ -71,7 +71,7 @@ kubectl logs -f -n toolhive-system This shows you the logs of the operator pod, which can help you debug any issues. For comprehensive logging and audit capabilities, see the -[Logging infrastructure](./logging-infrastructure.md) guide. +[Logging infrastructure](./logging.mdx) guide. ## Customize the operator @@ -265,7 +265,7 @@ configured during installation. ## Related information -- [Kubernetes introduction](./intro.md) - Overview of ToolHive's Kubernetes +- [Kubernetes introduction](./intro.mdx) - Overview of ToolHive's Kubernetes integration - [ToolHive operator tutorial](../tutorials/quickstart-k8s.mdx) - Step-by-step tutorial for getting started using a local kind cluster diff --git a/docs/toolhive/guides-k8s/index.mdx b/docs/toolhive/guides-k8s/index.mdx index c57d81bf..88b07f22 100644 --- a/docs/toolhive/guides-k8s/index.mdx +++ b/docs/toolhive/guides-k8s/index.mdx @@ -15,12 +15,12 @@ environments. By defining MCP servers as Kubernetes resources, the operator automates their deployment and management, making it easier to run MCP servers in multi-user environments. -:::info +:::info[Experimental] -Experimental The Kubernetes operator is still under active development and isn't -recommended for production use cases yet. Specifically, the `MCPServer` Custom -Resource Definition (CRD) is still in an alpha state so breaking changes to the -spec and its capabilities are possible. +The Kubernetes operator is still under active development and isn't recommended +for production use cases yet. Specifically, the `MCPServer` Custom Resource +Definition (CRD) is still in an alpha state so breaking changes to the spec and +its capabilities are possible. ::: diff --git a/docs/toolhive/guides-k8s/intro.md b/docs/toolhive/guides-k8s/intro.mdx similarity index 94% rename from docs/toolhive/guides-k8s/intro.md rename to docs/toolhive/guides-k8s/intro.mdx index 2bcb6d37..78f854ac 100644 --- a/docs/toolhive/guides-k8s/intro.md +++ b/docs/toolhive/guides-k8s/intro.mdx @@ -1,7 +1,6 @@ --- -title: Overview of the ToolHive Kubernetes Operator +title: Overview description: How to manage MCP servers in Kubernetes with the ToolHive operator -sidebar_label: Overview --- The ToolHive Kubernetes operator manages MCP servers in Kubernetes clusters. It @@ -16,8 +15,8 @@ Definition (CRD) is still in an alpha state so breaking changes to the spec and its capabilities are possible. See the [ToolHive Operator quickstart tutorial](../tutorials/quickstart-k8s.mdx) -to get started quickly using a local kind cluster. We'd love for you to try -itout and send feedback! +to get started quickly using a local kind cluster. We'd love for you to try it +out and send feedback! ::: @@ -52,7 +51,7 @@ flowchart TB ## Installation -[Use Helm to install the ToolHive operator](./deploy-operator-helm.md) in your +[Use Helm to install the ToolHive operator](./deploy-operator-helm.mdx) in your Kubernetes cluster. Helm simplifies the installation process and lets you manage the operator using Helm charts. diff --git a/docs/toolhive/guides-k8s/logging-infrastructure.md b/docs/toolhive/guides-k8s/logging.mdx similarity index 99% rename from docs/toolhive/guides-k8s/logging-infrastructure.md rename to docs/toolhive/guides-k8s/logging.mdx index 9175669d..aee04f65 100644 --- a/docs/toolhive/guides-k8s/logging-infrastructure.md +++ b/docs/toolhive/guides-k8s/logging.mdx @@ -1,8 +1,7 @@ --- -title: Logging infrastructure +title: Set up logging description: Configure and manage logging for ToolHive in Kubernetes environments -sidebar_label: Logging infrastructure --- The ToolHive Kubernetes operator provides comprehensive logging capabilities for diff --git a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx index c92d92cf..804aecc6 100644 --- a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx +++ b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx @@ -10,12 +10,21 @@ description: How to deploy MCP servers in Kubernetes using the ToolHive operator - [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate with your cluster - The ToolHive operator installed in your cluster (see - [Deploy the operator using Helm](./deploy-operator-helm.md)) + [Deploy the operator using Helm](./deploy-operator-helm.mdx)) ## Overview The ToolHive operator deploys MCP servers in Kubernetes by creating proxy pods -that manage the actual MCP server containers. Here's how the architecture works: +that manage the actual MCP server containers. + +:::tip + +If you need to build a container image for an MCP server that doesn't already +have one available, see the +[Build MCP containers](../guides-cli/build-containers.mdx) guide to learn how to +quickly create container images using the ToolHive CLI. + +::: ### High-level architecture @@ -108,7 +117,7 @@ deployed. - **Cluster mode (default)**: Create MCPServer resources in any namespace - **Namespace mode**: Create MCPServer resources only in allowed namespaces -See [Deploy the operator](./deploy-operator-helm.md#operator-deployment-modes) +See [Deploy the operator](./deploy-operator-helm.mdx#operator-deployment-modes) to learn about the different deployment modes. To create an MCP server, define an `MCPServer` resource and apply it to your @@ -436,12 +445,21 @@ kubectl -n describe mcpserver See the [Client compatibility](../reference/client-compatibility.mdx) reference to learn how to connect to MCP servers using different clients. +Learn how to customize MCP tools using +[filters and overrides](./customize-tools.mdx). + +Collect telemetry data from your MCP servers by following the +[Telemetry and metrics](./telemetry-and-metrics.mdx) guide. Configure audit +logging by following the [Set up logging](./logging.mdx) guide. + ## Related information - [Kubernetes CRD reference](../reference/crd-spec.mdx) - Reference for the `MCPServer` Custom Resource Definition (CRD) -- [Deploy the operator using Helm](./deploy-operator-helm.md) - Install the +- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the ToolHive operator +- [Build MCP containers](../guides-cli/build-containers.mdx) - Create custom MCP + server container images ## Troubleshooting @@ -461,7 +479,7 @@ helm get values toolhive-operator -n toolhive-system Check the `operator.rbac.scope` and `operator.rbac.allowedNamespaces` properties. If the operator runs in `namespace` mode, add the namespace where you created the `MCPServer` to the `allowedNamespaces` list. See -[Operator deployment modes](./deploy-operator-helm.md#operator-deployment-modes). +[Operator deployment modes](./deploy-operator-helm.mdx#operator-deployment-modes). If the operator runs in `cluster` mode (default) or the `MCPServer` is in an allowed namespace, check the operator logs and resource status: diff --git a/docs/toolhive/guides-k8s/telemetry-and-metrics.md b/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx similarity index 97% rename from docs/toolhive/guides-k8s/telemetry-and-metrics.md rename to docs/toolhive/guides-k8s/telemetry-and-metrics.mdx index 7268ed79..d032ed26 100644 --- a/docs/toolhive/guides-k8s/telemetry-and-metrics.md +++ b/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx @@ -1,5 +1,5 @@ --- -title: Telemetry (metrics and traces) +title: Telemetry and metrics description: How to enable OpenTelemetry (metrics and traces) and Prometheus instrumentation for ToolHive MCP servers inside of Kubernetes using the @@ -16,7 +16,7 @@ Datadog, and Grafana Cloud, or expose Prometheus metrics directly. ToolHive's telemetry captures detailed information about MCP interactions including traces, metrics, and performance data. For a comprehensive overview of the telemetry architecture, metrics collection, and monitoring capabilities, see -the [observability overview](../concepts/observability.md). +the [observability overview](../concepts/observability.mdx). ## Enable telemetry @@ -281,9 +281,9 @@ Telemetry adds minimal overhead when properly configured: - Tutorial: [Collect telemetry for MCP workloads](../tutorials/opentelemetry.mdx) - Step-by-step guide to set up a local observability stack -- [Telemetry and monitoring concepts](../concepts/observability.md) - Overview +- [Telemetry and monitoring concepts](../concepts/observability.mdx) - Overview of ToolHive's observability architecture - [Kubernetes CRD reference](../reference/crd-spec.mdx) - Reference for the `MCPServer` Custom Resource Definition (CRD) -- [Deploy the operator using Helm](./deploy-operator-helm.md) - Install the +- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the ToolHive operator diff --git a/docs/toolhive/guides-mcp/fetch.mdx b/docs/toolhive/guides-mcp/fetch.mdx index c8c9367d..51c06eb6 100644 --- a/docs/toolhive/guides-mcp/fetch.mdx +++ b/docs/toolhive/guides-mcp/fetch.mdx @@ -107,5 +107,5 @@ Here are some sample prompts you can use to interact with the Fetch MCP server: - Use network isolation to restrict the server's outbound network access to the specific hosts and ports required for your use case. -- Enable [telemetry](../guides-cli/telemetry-and-metrics.md) to monitor tool +- Enable [telemetry](../guides-cli/telemetry-and-metrics.mdx) to monitor tool usage including URL access for security and auditing purposes. diff --git a/docs/toolhive/guides-mcp/filesystem.mdx b/docs/toolhive/guides-mcp/filesystem.mdx index 3b503e17..506a4f44 100644 --- a/docs/toolhive/guides-mcp/filesystem.mdx +++ b/docs/toolhive/guides-mcp/filesystem.mdx @@ -70,8 +70,8 @@ add any hosts or ports to completely restrict its outbound network access. -[Mount a directory](../guides-cli/filesystem-access.md) from the host filesystem -to the MCP server using the default container path: +[Mount a directory](../guides-cli/filesystem-access.mdx) from the host +filesystem to the MCP server using the default container path: ```bash thv run --volume /path/to/host/directory:/projects filesystem diff --git a/docs/toolhive/guides-mcp/k8s.mdx b/docs/toolhive/guides-mcp/k8s.mdx index 42d652ac..532b3bcf 100644 --- a/docs/toolhive/guides-mcp/k8s.mdx +++ b/docs/toolhive/guides-mcp/k8s.mdx @@ -182,7 +182,7 @@ spec: To filter or rename the tools exposed by your MCP server on Kubernetes, use the MCPToolConfig CRD and reference it from your MCPServer with the `toolConfigRef` field. See -[Configure tools for MCP servers on Kubernetes](../guides-k8s/tool-config.mdx). +[Configure tools for MCP servers on Kubernetes](../guides-k8s/customize-tools.mdx). ::: diff --git a/docs/toolhive/guides-mcp/meta-mcp.mdx b/docs/toolhive/guides-mcp/meta-mcp.mdx index 829ae80a..0072bfe2 100644 --- a/docs/toolhive/guides-mcp/meta-mcp.mdx +++ b/docs/toolhive/guides-mcp/meta-mcp.mdx @@ -56,7 +56,7 @@ The meta-mcp workflow: ## Usage The meta-mcp server is specifically designed to work with -[ToolHive groups](../guides-cli/group-management.md). The recommended setup is +[ToolHive groups](../guides-cli/group-management.mdx). The recommended setup is to run meta-mcp in its own dedicated group (e.g., "meta") and have other MCP servers in a separate group (e.g., "default"). This keeps client configurations clean and allows meta-mcp to discover and route to tools across all connected diff --git a/docs/toolhive/guides-ui/install.mdx b/docs/toolhive/guides-ui/install.mdx index 9b1ff513..18073f27 100644 --- a/docs/toolhive/guides-ui/install.mdx +++ b/docs/toolhive/guides-ui/install.mdx @@ -210,7 +210,7 @@ MCP servers. See [Run MCP servers](./run-mcp-servers.mdx) to get started. - Quickstart: [Getting started with the ToolHive UI](../tutorials/quickstart-ui.mdx) - [Client configuration](./client-configuration.mdx) -- [Secrets management](./secrets-management.md) +- [Secrets management](./secrets-management.mdx) ## Troubleshooting diff --git a/docs/toolhive/guides-ui/playground.mdx b/docs/toolhive/guides-ui/playground.mdx index 19b1ddc9..24b4723a 100644 --- a/docs/toolhive/guides-ui/playground.mdx +++ b/docs/toolhive/guides-ui/playground.mdx @@ -1,5 +1,5 @@ --- -title: Test MCP servers with playground +title: Test MCP servers description: Use the playground feature to test and validate MCP servers directly in the ToolHive UI with AI model providers. @@ -226,7 +226,7 @@ If tools are failing to execute: - Learn about [client configuration](./client-configuration.mdx) to connect ToolHive to external AI applications -- Set up [secrets management](./secrets-management.md) for secure handling of +- Set up [secrets management](./secrets-management.mdx) for secure handling of API keys and tokens - Explore [network isolation](./network-isolation.mdx) for enhanced security when testing untrusted MCP servers diff --git a/docs/toolhive/guides-ui/registry.mdx b/docs/toolhive/guides-ui/registry.mdx index 699f4868..eb67404d 100644 --- a/docs/toolhive/guides-ui/registry.mdx +++ b/docs/toolhive/guides-ui/registry.mdx @@ -8,7 +8,7 @@ import ThemedImage from '@theme/ThemedImage'; ToolHive includes a built-in registry of MCP servers with verified configurations that meet a -[minimum quality standard](../concepts/registry-criteria.md), allowing you to +[minimum quality standard](../concepts/registry-criteria.mdx), allowing you to discover and deploy high-quality tools effortlessly. You can browse the registry, select servers, and run them securely through the user interface. @@ -98,5 +98,5 @@ After exploring the registry and finding servers you want to use: registry - [Custom registry tutorial](../tutorials/custom-registry.mdx) - Create your own MCP server registry -- [Registry criteria](../concepts/registry-criteria.md) - Quality standards for +- [Registry criteria](../concepts/registry-criteria.mdx) - Quality standards for built-in registry servers diff --git a/docs/toolhive/guides-ui/run-mcp-servers.mdx b/docs/toolhive/guides-ui/run-mcp-servers.mdx index a7317a73..2497a0f4 100644 --- a/docs/toolhive/guides-ui/run-mcp-servers.mdx +++ b/docs/toolhive/guides-ui/run-mcp-servers.mdx @@ -3,7 +3,8 @@ title: Run MCP servers description: How to install and run MCP servers in the ToolHive UI. --- -import RemoteAuthExamples from '../_partials/_remote-mcp-auth-examples.md'; +import RemoteAuthExamples from '../_partials/_remote-mcp-auth-examples.mdx'; +import Heading from '@theme/Heading'; ToolHive makes it easy to run and manage Model Context Protocol (MCP) servers. This guide walks you through installing MCP servers from the registry, using @@ -12,7 +13,7 @@ Docker images, or from source packages. ## Install from the registry ToolHive includes a built-in registry of MCP servers that meet a -[minimum quality standard](../concepts/registry-criteria.md), allowing you to +[minimum quality standard](../concepts/registry-criteria.mdx), allowing you to discover and deploy high-quality tools effortlessly. Simply select one from the list to run it securely with just a few clicks. @@ -147,7 +148,7 @@ remaining required information and adjust any optional settings as needed: Enter a value to create a new secret or select an existing secret from the provider. Secrets are stored securely and can be used by the MCP server without exposing them in plaintext. See - [Secrets management](./secrets-management.md) for details. [Optional] + [Secrets management](./secrets-management.mdx) for details. [Optional] - **Scopes**: List of permissions your application is requesting. [Optional] - **PKCE**: Enable Proof Key for Code Exchange (RFC 7636) for enhanced security without requiring a client secret. [Optional] @@ -160,7 +161,7 @@ remaining required information and adjust any optional settings as needed: Enter a value to create a new secret or select an existing secret from the provider. Secrets are stored securely and can be used by the MCP server without exposing them in plaintext. See - [Secrets management](./secrets-management.md) for details. [Optional] + [Secrets management](./secrets-management.mdx) for details. [Optional] - **PKCE**: Enable Proof Key for Code Exchange (RFC 7636) for enhanced security without requiring a client secret. [Optional] @@ -224,7 +225,8 @@ server, on the introductory screen. In the **Custom MCP server** dialog, choose [Docker image](#from-a-docker-image) or [Package manager](#from-a-source-package). -

From a Docker image

+{/* prettier-ignore */} +From a Docker image Select the **Docker image** option. This allows you to run any MCP server that is available as a Docker image in a remote registry or locally on your system. @@ -272,7 +274,8 @@ On the configuration form, enter: Click **Install server** to create and start the MCP server container. -

From a source package

+{/* prettier-ignore */} +From a source package Select the **Package manager** option. This allows you to run an MCP server from a source package. @@ -380,7 +383,7 @@ On the configuration form, enter: Enter a value to create a new secret or select an existing secret from the provider. Secrets are stored securely and can be used by the MCP server without exposing them in plaintext. See - [Secrets management](./secrets-management.md) for details. [Optional] + [Secrets management](./secrets-management.mdx) for details. [Optional] - **Scopes**: List of permissions your application is requesting. [Optional] **OIDC authentication options:** @@ -391,7 +394,7 @@ On the configuration form, enter: Enter a value to create a new secret or select an existing secret from the provider. Secrets are stored securely and can be used by the MCP server without exposing them in plaintext. See - [Secrets management](./secrets-management.md) for details. [Optional] + [Secrets management](./secrets-management.mdx) for details. [Optional] - **PKCE**: Enable Proof Key for Code Exchange (RFC 7636) for enhanced security without requiring a client secret. [Optional] @@ -457,7 +460,7 @@ automatically the next time you launch the application. - Connect ToolHive to AI clients like GitHub Copilot or Cursor using the [client configuration guide](./client-configuration.mdx). -- Learn more about [secrets management](./secrets-management.md) to securely +- Learn more about [secrets management](./secrets-management.mdx) to securely manage API tokens and other sensitive data. - Test your MCP servers using the [playground](./playground.mdx) to validate functionality and behavior with different models. diff --git a/docs/toolhive/guides-ui/secrets-management.md b/docs/toolhive/guides-ui/secrets-management.mdx similarity index 100% rename from docs/toolhive/guides-ui/secrets-management.md rename to docs/toolhive/guides-ui/secrets-management.mdx diff --git a/docs/toolhive/index.mdx b/docs/toolhive/index.mdx index f7ed58f5..645fb7b6 100644 --- a/docs/toolhive/index.mdx +++ b/docs/toolhive/index.mdx @@ -31,7 +31,7 @@ import ThemedImage from '@theme/ThemedImage'; }} /> -## What is ToolHive? +# What is ToolHive? ToolHive simplifies the deployment and management of Model Context Protocol (MCP) servers. It ensures ease of use, consistency, and security by running @@ -41,7 +41,7 @@ Follow the [getting started guide](./tutorials/quickstart-ui.mdx) to install ToolHive and run your first MCP server. To learn more about the Model Context Protocol, see our -[MCP primer](./concepts/mcp-primer.md). +[MCP primer](./concepts/mcp-primer.mdx). ToolHive is available in three modes to suit different use cases: diff --git a/docs/toolhive/reference/client-compatibility.mdx b/docs/toolhive/reference/client-compatibility.mdx index 37ddbbe9..5c1c4a97 100644 --- a/docs/toolhive/reference/client-compatibility.mdx +++ b/docs/toolhive/reference/client-compatibility.mdx @@ -4,8 +4,6 @@ description: Overview of supported AI clients and their compatibility with ToolHive. --- -import ClientTable from '../_partials/_client-compat-table.md'; - This page shows which AI clients work with ToolHive and how they connect to MCP servers. @@ -13,7 +11,31 @@ servers. We've tested ToolHive with these clients: - +| Client | Supported | Auto-configuration | Notes | +| -------------------------- | :-------: | :----------------: | ------------------------------------------- | +| GitHub Copilot (VS Code) | ✅ | ✅ | v1.102+ or Insiders version ([see note][3]) | +| Cursor | ✅ | ✅ | v0.50.0+ | +| Roo Code (VS Code) | ✅ | ✅ | v3.19.2+ | +| Cline (VS Code) | ✅ | ✅ | v3.17.10+ | +| Claude Code CLI | ✅ | ✅ | v1.0.27+ | +| Windsurf IDE | ✅ | ✅ | | +| Windsurf (JetBrains) | ✅ | ✅ | | +| Sourcegraph Amp CLI | ✅ | ✅ | | +| Sourcegraph Amp (VS Code) | ✅ | ✅ | | +| Sourcegraph Amp (Cursor) | ✅ | ✅ | | +| Sourcegraph Amp (Windsurf) | ✅ | ✅ | | +| LM Studio | ✅ | ✅ | v0.3.17+ | +| Goose | ✅ | ✅ | | +| ChatGPT Desktop | ✅ | ❌ | See [STDIO-only client configuration][4] | +| Claude Desktop | ✅ | ❌ | See [STDIO-only client configuration][4] | +| Kiro | ✅ | ❌ | See [STDIO-only client configuration][4] | +| GitHub Copilot (JetBrains) | ✅ | ❌ | v1.5.47+ | +| Continue (VS Code) | ✅ | ❌ | v1.0.14+ | +| Continue (JetBrains) | ✅ | ❌ | v1.0.23+ | +| PydanticAI | ✅ | ❌ | v0.2.18+ | + +[3]: #vs-code-with-copilot +[4]: #stdio-only-client-configuration The minimum versions listed are the earliest versions that support the Streamable HTTP transport protocol. diff --git a/docs/toolhive/tutorials/custom-registry.mdx b/docs/toolhive/tutorials/custom-registry.mdx index 27d2bf9a..5709b7ae 100644 --- a/docs/toolhive/tutorials/custom-registry.mdx +++ b/docs/toolhive/tutorials/custom-registry.mdx @@ -7,7 +7,7 @@ description: Learn how to create a custom MCP registry for ToolHive. ToolHive includes a built-in registry of MCP servers with verified configurations that meet a -[minimum quality standard](../concepts/registry-criteria.md). +[minimum quality standard](../concepts/registry-criteria.mdx). But you can also create your own custom registry to include the MCP servers that are relevant to your organization or specific use cases. This allows you to diff --git a/docs/toolhive/tutorials/opentelemetry.mdx b/docs/toolhive/tutorials/opentelemetry.mdx index 7b64f5d3..30d3256a 100644 --- a/docs/toolhive/tutorials/opentelemetry.mdx +++ b/docs/toolhive/tutorials/opentelemetry.mdx @@ -656,7 +656,7 @@ real-time. You can also explore other metrics in Grafana by creating custom panels and queries. See the -[Observability guide](../concepts/observability.md#grafana-dashboard-queries) +[Observability guide](../concepts/observability.mdx#grafana-dashboard-queries) for examples. @@ -723,7 +723,7 @@ real-time. You can also explore other metrics in Grafana by creating custom panels and queries. See the -[Observability guide](../concepts/observability.md#grafana-dashboard-queries) +[Observability guide](../concepts/observability.mdx#grafana-dashboard-queries) for examples. @@ -802,7 +802,7 @@ Congratulations! You've successfully set up comprehensive observability for ToolHive MCP workloads using Jaeger and Prometheus. To learn more about ToolHive's telemetry capabilities and best practices, see -the [Observability concepts guide](../concepts/observability.md). +the [Observability concepts guide](../concepts/observability.mdx). Here are some next steps to explore: @@ -819,14 +819,14 @@ Here are some next steps to explore: ### CLI-specific next steps - **Review the CLI telemetry guide**: Explore - [detailed configuration options](../guides-cli/telemetry-and-metrics.md) + [detailed configuration options](../guides-cli/telemetry-and-metrics.mdx) - **Scale to multiple servers**: Run multiple MCP servers with different configurations - **Production CLI setup**: Learn about [secrets management](../guides-cli/secrets-management.mdx) and [custom permissions](../guides-cli/custom-permissions.mdx) - **Alternative backends**: Try other observability platforms mentioned in the - [CLI telemetry guide](../guides-cli/telemetry-and-metrics.md) + [CLI telemetry guide](../guides-cli/telemetry-and-metrics.mdx) @@ -834,7 +834,7 @@ Here are some next steps to explore: ### Kubernetes-specific next steps - **Review the Kubernetes telemetry guide**: Explore - [detailed configuration options](../guides-k8s/telemetry-and-metrics.md) + [detailed configuration options](../guides-k8s/telemetry-and-metrics.mdx) - **Production deployment**: Set up production-grade [Jaeger](https://www.jaegertracing.io/docs/deployment/) and [Prometheus](https://prometheus.io/docs/prometheus/latest/installation/) with @@ -852,11 +852,11 @@ Here are some next steps to explore: ## Related information -- [Observability concepts](../concepts/observability.md) - Understanding +- [Observability concepts](../concepts/observability.mdx) - Understanding ToolHive's telemetry architecture -- [CLI telemetry guide](../guides-cli/telemetry-and-metrics.md) - Detailed CLI +- [CLI telemetry guide](../guides-cli/telemetry-and-metrics.mdx) - Detailed CLI configuration options -- [Kubernetes telemetry guide](../guides-k8s/telemetry-and-metrics.md) - +- [Kubernetes telemetry guide](../guides-k8s/telemetry-and-metrics.mdx) - Kubernetes operator telemetry features - [OpenTelemetry Collector documentation](https://opentelemetry.io/docs/collector/) - Official OpenTelemetry Collector documentation diff --git a/docs/toolhive/tutorials/quickstart-k8s.mdx b/docs/toolhive/tutorials/quickstart-k8s.mdx index 405e30bb..0decde11 100644 --- a/docs/toolhive/tutorials/quickstart-k8s.mdx +++ b/docs/toolhive/tutorials/quickstart-k8s.mdx @@ -436,7 +436,7 @@ Here are some next steps to explore: [advanced MCP server configurations](../guides-k8s/run-mcp-k8s.mdx) for production deployments - Learn more about - [Helm deployment options](../guides-k8s/deploy-operator-helm.md) and + [Helm deployment options](../guides-k8s/deploy-operator-helm.mdx) and configuration - Integrate MCP servers with your existing Kubernetes applications - Try deploying other MCP servers from the ToolHive registry diff --git a/docs/toolhive/tutorials/quickstart-ui.mdx b/docs/toolhive/tutorials/quickstart-ui.mdx index 522fcf2e..886cdd01 100644 --- a/docs/toolhive/tutorials/quickstart-ui.mdx +++ b/docs/toolhive/tutorials/quickstart-ui.mdx @@ -124,10 +124,10 @@ Congratulations! You've successfully installed ToolHive and run your first MCP server. Here are some next steps to explore: - Learn more about MCP concepts in the - [MCP primer guide](../concepts/mcp-primer.md) + [MCP primer guide](../concepts/mcp-primer.mdx) - Try [running more MCP servers](../guides-ui/run-mcp-servers.mdx) from the registry or from custom sources -- Learn about [secrets management](../guides-ui/secrets-management.md) for MCP +- Learn about [secrets management](../guides-ui/secrets-management.mdx) for MCP servers that require authentication - Learn how to [manually configure clients](../reference/client-compatibility.mdx#manual-configuration) diff --git a/docusaurus.config.ts b/docusaurus.config.ts index 820ac595..74479e6e 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -192,19 +192,19 @@ const config: Config = { href: 'https://github.com/stacklok', className: 'fa-brands fa-github fa-lg', position: 'right', - 'aria-label': 'GitHub', + 'aria-label': 'Stacklok on GitHub', }, { href: 'https://discord.gg/stacklok', className: 'fa-brands fa-discord fa-lg', position: 'right', - 'aria-label': 'Discord', + 'aria-label': 'Join Stacklok on Discord', }, { href: 'https://youtube.com/@stacklok', className: 'fa-brands fa-youtube fa-lg', position: 'right', - 'aria-label': 'YouTube', + 'aria-label': 'Stacklok on YouTube', }, ], }, @@ -221,11 +221,11 @@ const config: Config = { items: [ { html: `
- - - - - + + + + +
`, }, ], diff --git a/sidebars.ts b/sidebars.ts index b0f2e50d..7cd3c87b 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -48,9 +48,21 @@ const sidebars: SidebarsConfig = { items: [ 'toolhive/guides-ui/install', 'toolhive/guides-ui/registry', - 'toolhive/guides-ui/run-mcp-servers', - 'toolhive/guides-ui/network-isolation', - 'toolhive/guides-ui/secrets-management', + { + type: 'category', + label: 'Run MCP servers', + description: 'How to install and run MCP servers in the ToolHive UI', + collapsed: false, + collapsible: false, + link: { + type: 'doc', + id: 'toolhive/guides-ui/run-mcp-servers', + }, + items: [ + 'toolhive/guides-ui/secrets-management', + 'toolhive/guides-ui/network-isolation', + ], + }, 'toolhive/guides-ui/client-configuration', 'toolhive/guides-ui/playground', ], @@ -67,11 +79,22 @@ const sidebars: SidebarsConfig = { items: [ 'toolhive/guides-cli/install', 'toolhive/guides-cli/registry', - 'toolhive/guides-cli/run-mcp-servers', - 'toolhive/guides-cli/build-containers', - 'toolhive/guides-cli/manage-mcp-servers', - 'toolhive/guides-cli/group-management', - 'toolhive/guides-cli/secrets-management', + { + type: 'category', + label: 'Run MCP servers', + description: 'How to run MCP servers with the ToolHive CLI', + collapsed: false, + collapsible: false, + link: { + type: 'doc', + id: 'toolhive/guides-cli/run-mcp-servers', + }, + items: [ + 'toolhive/guides-cli/manage-mcp-servers', + 'toolhive/guides-cli/group-management', + 'toolhive/guides-cli/secrets-management', + ], + }, 'toolhive/guides-cli/client-configuration', { type: 'category', @@ -79,6 +102,7 @@ const sidebars: SidebarsConfig = { description: 'How to configure filesystem and network access for MCP servers', collapsed: false, + collapsible: false, link: { type: 'doc', id: 'toolhive/guides-cli/custom-permissions', @@ -90,6 +114,7 @@ const sidebars: SidebarsConfig = { ], }, 'toolhive/guides-cli/telemetry-and-metrics', + 'toolhive/guides-cli/build-containers', 'toolhive/guides-cli/advanced-cicd', { type: 'category', @@ -123,9 +148,9 @@ const sidebars: SidebarsConfig = { 'toolhive/guides-k8s/intro', 'toolhive/guides-k8s/deploy-operator-helm', 'toolhive/guides-k8s/run-mcp-k8s', - 'toolhive/guides-k8s/tool-config', + 'toolhive/guides-k8s/customize-tools', 'toolhive/guides-k8s/telemetry-and-metrics', - 'toolhive/guides-k8s/logging-infrastructure', + 'toolhive/guides-k8s/logging', 'toolhive/reference/crd-spec', ], }, diff --git a/vercel.json b/vercel.json index f70f2e1e..9d0fe883 100644 --- a/vercel.json +++ b/vercel.json @@ -10,6 +10,16 @@ "source": "/toolhive/tutorials/toolhive-operator", "destination": "/toolhive/tutorials/quickstart-k8s", "permanent": true + }, + { + "source": "/toolhive/guides-k8s/logging-infrastructure", + "destination": "/toolhive/guides-k8s/logging", + "permanent": true + }, + { + "source": "/toolhive/guides-k8s/tool-config", + "destination": "/toolhive/guides-k8s/customize-tools", + "permanent": true } ], "installCommand": "dnf install -q -y jq && npm install",