diff --git a/.agents/skills b/.agents/skills new file mode 120000 index 00000000..454b8427 --- /dev/null +++ b/.agents/skills @@ -0,0 +1 @@ +../.claude/skills \ No newline at end of file diff --git a/docs/toolhive/guides-cli/index.mdx b/docs/toolhive/guides-cli/index.mdx index ddbcade7..5286053f 100644 --- a/docs/toolhive/guides-cli/index.mdx +++ b/docs/toolhive/guides-cli/index.mdx @@ -9,13 +9,19 @@ import DocCardList from '@theme/DocCardList'; ## Introduction -The ToolHive CLI (`thv`) is a command-line tool that allows you to deploy and -manage MCP servers on your local machine or in development environments. It -provides quick deployment of MCP servers and supports advanced features like -custom permissions, network access filtering, and telemetry. +The ToolHive CLI (`thv`) gives you a fast, repeatable way to run and manage MCP +servers from the terminal. Use it when you want to script server setup, control +permissions precisely, work in development environments, or automate ToolHive +workflows in shell scripts and CI. -It's designed for developers who prefer working in a terminal or need to -integrate MCP server management into scripts or automation workflows. +Within the ToolHive platform, the CLI gives you direct access to the same local +runtime, built-in registry, and client-configuration workflows that power the +UI. If you want a terminal-first way to run ToolHive locally or embed it in +automation, start here. + +The CLI can also connect your local workflows and AI clients to the broader +ToolHive platform. You can use it with MCP servers or gateways managed by the +Kubernetes Operator, and point local workflows at a ToolHive Registry Server. :::info[Using ToolHive UI?] @@ -32,6 +38,8 @@ both installed. `thv` and run your first MCP server in minutes. - **Already installed?** Jump to [Run MCP servers](./run-mcp-servers.mdx) to start managing servers from the command line. +- **Want to browse the default catalog?** See + [Use the registry](./registry.mdx). - **Managing agent skills?** See [Manage agent skills](./skills-management.mdx) to install and publish reusable skills. - **Building or automating?** See advanced workflows for [auth](./auth.mdx), diff --git a/docs/toolhive/guides-cli/install.mdx b/docs/toolhive/guides-cli/install.mdx index dd09b767..85d1518b 100644 --- a/docs/toolhive/guides-cli/install.mdx +++ b/docs/toolhive/guides-cli/install.mdx @@ -389,7 +389,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.mdx) and +MCP servers. See [Use the registry](./registry.mdx) and [Run MCP servers](./run-mcp-servers.mdx) to get started. ## Related information diff --git a/docs/toolhive/guides-cli/quickstart.mdx b/docs/toolhive/guides-cli/quickstart.mdx index 0af0e6aa..236267a1 100644 --- a/docs/toolhive/guides-cli/quickstart.mdx +++ b/docs/toolhive/guides-cli/quickstart.mdx @@ -25,8 +25,9 @@ Before starting this tutorial, make sure you have: - [Docker](https://docs.docker.com/get-docker/) or [Podman](https://podman-desktop.io/downloads) or [Colima](https://github.com/abiosoft/colima) installed and running -- A [supported MCP client](../reference/client-compatibility.mdx) like GitHub - Copilot in VS Code, Cursor, Claude Code, and more +- _(Optional)_ A [supported MCP client](../reference/client-compatibility.mdx) + such as GitHub Copilot in VS Code, Cursor, or Claude Code. Needed only if you + want to test end-to-end client integration. ## Step 1: Install ToolHive @@ -92,44 +93,7 @@ Platform: darwin/arm64 This confirms ToolHive is installed and ready to use. -## Step 2: Register your client - -Next, run the ToolHive client setup command to register your MCP client: - -```bash -thv client setup -``` - -Select one or more clients from the list using the spacebar to toggle selection. -Press Enter to confirm your selection. - -:::info[What's happening?] - -When you run the setup command, ToolHive automatically finds -[supported clients](../reference/client-compatibility.mdx) on your system. When -you register a client, ToolHive automatically configures it to use MCP servers -that you run. This means you don't have to manually configure the client to -connect to the MCP server. - -::: - -Confirm that your client is registered successfully: - -```bash -thv client status -``` - -You should see output similar to this: - -```text -┌────────────────┬───────────┬────────────┐ -│ CLIENT TYPE │ INSTALLED │ REGISTERED │ -├────────────────┼───────────┼────────────┤ -│ vscode │ ✅ Yes │ ❌ No │ -└────────────────┴───────────┴────────────┘ -``` - -## Step 3: Find an MCP server to run +## Step 2: Find an MCP server to run See what MCP servers are available in the registry: @@ -153,8 +117,8 @@ This shows all the MCP servers available in the ToolHive registry. :::info[What's happening?] ToolHive maintains a curated registry of MCP servers that have been verified to -work correctly. The registry includes information about what each server does -and how to use it. +work correctly. This built-in registry is the default catalog that the CLI uses +to help you find and launch servers. ::: @@ -169,7 +133,7 @@ thv registry info fetch This shows you detailed information about the server, including what tools it provides and any configuration options. -## Step 4: Run the Fetch MCP server +## Step 3: Run the Fetch MCP server Now, run the Fetch server: @@ -208,7 +172,7 @@ When you run an MCP server, ToolHive: ::: -## Step 5: Verify the server is running +## Step 4: Verify the server is running Check that the server is running: @@ -233,9 +197,46 @@ running and how they're configured. ::: +## Step 5: Connect an AI client + +To see the full payoff of the tutorial, have ToolHive configure a supported MCP +client for you now: + +```bash +thv client setup +``` + +Select one or more clients from the list using the spacebar to toggle selection. +Press Enter to confirm your selection. + +Confirm that your client is registered successfully: + +```bash +thv client status +``` + +You should see output similar to this: + +```text +┌────────────────┬───────────┬────────────┐ +│ CLIENT TYPE │ INSTALLED │ REGISTERED │ +├────────────────┼───────────┼────────────┤ +│ vscode │ ✅ Yes │ ✅ Yes │ +└────────────────┴───────────┴────────────┘ +``` + +:::info[What's happening?] + +When you run the setup command, ToolHive automatically finds +[supported clients](../reference/client-compatibility.mdx) on your system. When +you register a client, ToolHive automatically configures it to use MCP servers +that you run. + +::: + ## Step 6: Use the MCP server with your AI client -Now that your MCP server is running, you can use it with your AI client +If you completed Step 5, you can now use the MCP server with your AI client application. Open your supported client (VS Code, Cursor, etc.) and ask the AI to fetch content from a website. Note that you might need to restart your client for the changes to take effect. @@ -279,12 +280,12 @@ the container, freeing up resources. ::: -## What's next? +## Next steps Congratulations! You've successfully installed ToolHive and run your first MCP server. Here are some next steps to explore: -- Try running other MCP servers from the registry with +- Try running other MCP servers from the built-in registry with [`thv registry list`](../reference/cli/thv_registry_list.md) and [`thv run`](../reference/cli/thv_run.md) - Learn about [secrets management](../guides-cli/secrets-management.mdx) for MCP @@ -309,6 +310,11 @@ production-ready MCP servers, that's where Stacklok Enterprise comes in. ::: +## Related information + +- [Use the registry](../guides-cli/registry.mdx) +- [Client compatibility](../reference/client-compatibility.mdx) + ## Troubleshooting
@@ -333,7 +339,7 @@ thv run --proxy-port 8081 fetch If your AI client application can't use the server: -- Make sure your client is registered with ToolHive (see Step 2) +- Make sure your client is registered with ToolHive (see Step 5) - Check that your client is supported - Restart your client to pick up the new configuration - Verify the server is running with [`thv list`](../reference/cli/thv_list.md) diff --git a/docs/toolhive/guides-cli/registry.mdx b/docs/toolhive/guides-cli/registry.mdx index b85bdf38..2713512b 100644 --- a/docs/toolhive/guides-cli/registry.mdx +++ b/docs/toolhive/guides-cli/registry.mdx @@ -1,5 +1,5 @@ --- -title: Explore the registry +title: Use the registry description: Search the built-in registry to find, inspect, and run MCP servers with one command. diff --git a/docs/toolhive/guides-k8s/index.mdx b/docs/toolhive/guides-k8s/index.mdx index d8aea8db..a740ec44 100644 --- a/docs/toolhive/guides-k8s/index.mdx +++ b/docs/toolhive/guides-k8s/index.mdx @@ -9,8 +9,16 @@ import DocCardList from '@theme/DocCardList'; ## Introduction -The ToolHive Kubernetes Operator manages MCP servers in Kubernetes clusters. You -define MCP servers as Kubernetes custom resources and the operator automates +The ToolHive Kubernetes Operator brings MCP servers into a shared, governable +Kubernetes environment. It solves the gap between trying MCP locally and running +it for teams, with standard deployment workflows, centralized policy control, +and platform-managed connectivity. + +Within the ToolHive platform, the operator is the foundation for multi-user and +production-style deployments. It runs MCP workloads in the cluster and unlocks +capabilities like Virtual MCP Server (vMCP) and Registry Server integrations. + +You define MCP servers as Kubernetes custom resources and the operator automates their deployment, proxying, and lifecycle management. The operator supports several primary resource types: @@ -21,10 +29,8 @@ several primary resource types: - **VirtualMCPServer**: aggregate and optimize multiple servers behind a single endpoint -Beyond managing MCP servers, the operator can deploy -[ToolHive Registry Server](../guides-registry/index.mdx) instances via -MCPRegistry resources, enabling automatic discovery of cluster-hosted MCP -servers. +This is the best starting point when you need ToolHive in a shared, multi-user, +or production-style Kubernetes environment. ## Where to start diff --git a/docs/toolhive/guides-k8s/quickstart.mdx b/docs/toolhive/guides-k8s/quickstart.mdx index e137401e..631df6ab 100644 --- a/docs/toolhive/guides-k8s/quickstart.mdx +++ b/docs/toolhive/guides-k8s/quickstart.mdx @@ -426,7 +426,7 @@ This will fully remove the kind cluster and clean up all associated resources. ::: -## What's next? +## Next steps Congratulations! You've successfully deployed the ToolHive operator and created your first MCP server using Kubernetes resources. You now have a working @@ -454,6 +454,11 @@ support - built for teams taking MCP from proof of concept to production. ::: +## Related information + +- [Connect clients to MCP servers](../guides-k8s/connect-clients.mdx) +- [Run MCP servers in Kubernetes](../guides-k8s/run-mcp-k8s.mdx) + ## Troubleshooting
diff --git a/docs/toolhive/guides-registry/index.mdx b/docs/toolhive/guides-registry/index.mdx index b25506e3..3209da8d 100644 --- a/docs/toolhive/guides-registry/index.mdx +++ b/docs/toolhive/guides-registry/index.mdx @@ -9,21 +9,28 @@ import DocCardList from '@theme/DocCardList'; ## Introduction -The ToolHive Registry Server is an implementation of the official -[Model Context Protocol (MCP) Registry API specification](https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/api/generic-registry-api.md). -It provides a standardized REST API for discovering and accessing MCP servers -from multiple backend sources, including Kubernetes clusters, Git repositories, -API endpoints, and local files. +The ToolHive Registry Server helps you publish and govern a catalog of MCP +servers or skills for your team. Use it when you want a trusted catalog that +improves discoverability, supports publishing workflows, and gives you more +control over what different users can access. + +It can aggregate entries from Kubernetes clusters, Git repositories, API +endpoints, and local files, then expose them through a standard MCP Registry API +for ToolHive and other clients. :::note This section covers the **Registry Server**, a standalone service you deploy yourself. Looking for the built-in registry instead? See -[Explore the registry](../guides-cli/registry.mdx) (CLI) or -[Explore the registry](../guides-ui/registry.mdx) (UI). +[Use the registry](../guides-cli/registry.mdx) (CLI) or +[Use the registry](../guides-ui/registry.mdx) (UI). ::: +If you want to host and operate your own catalog, use the Registry Server. If +you only need to browse the default ToolHive catalog from the UI or CLI, you do +not need to deploy it. + ## Where to start - **New to the Registry Server?** Follow the diff --git a/docs/toolhive/guides-registry/intro.mdx b/docs/toolhive/guides-registry/intro.mdx index 6a65173b..d9d815fa 100644 --- a/docs/toolhive/guides-registry/intro.mdx +++ b/docs/toolhive/guides-registry/intro.mdx @@ -5,22 +5,37 @@ description: Server --- -The ToolHive Registry Server is a standards-compliant implementation of the MCP -Registry API specification. It provides a REST API for discovering and accessing -MCP servers from multiple backend sources. +The ToolHive Registry Server gives you a way to publish, curate, and control a +catalog of MCP servers and skills for your organization. Use it when you want a +trusted catalog for discoverability, team-scoped access, publishing, or +multi-source aggregation. + +It pulls entries from multiple sources, stores them centrally, and exposes them +through a standard MCP Registry API that ToolHive and other clients can consume. :::note[Registry Server vs. built-in registry] -This section covers the **Registry Server**, a standalone service you deploy -yourself for hosting and curating your own MCP server catalog. +This section covers the **Registry Server** for hosting and curating your own +MCP server and skills catalog. ToolHive also ships with a **built-in registry** for browsing and discovering MCP servers from the default catalog. That's a different feature: see -[Explore the registry](../guides-cli/registry.mdx) (CLI) or -[Explore the registry](../guides-ui/registry.mdx) (UI). +[Use the registry](../guides-cli/registry.mdx) (CLI) or +[Use the registry](../guides-ui/registry.mdx) (UI). ::: +## Why use the Registry Server? + +Use the Registry Server when you need to: + +- Curate a private or team-specific catalog instead of relying only on the + default public catalog +- Publish MCP servers or [skills](../concepts/skills.mdx) for internal use +- Aggregate entries from multiple sources behind one registry API +- Apply authentication and authorization policies to registry access +- Surface cluster-hosted workloads to users through a managed catalog + ## Key concepts The Registry Server is built around three core concepts: @@ -38,8 +53,9 @@ The Registry Server is built around three core concepts: ## How the Registry Server works -The Registry server aggregates MCP server metadata from various sources and -exposes it through a standardized API. When you start the server, it: +The Registry Server aggregates MCP server and skills metadata from various +sources and exposes it through a standardized API. When you start the server, +it: 1. Loads configuration from a YAML file 2. Runs database migrations automatically @@ -129,9 +145,9 @@ The server supports five source types: ## Registry Server and the rest of ToolHive -The Registry Server is a standalone service. It is separate from the built-in -catalog that the ToolHive CLI and UI ship with for browsing public MCP servers. -The pieces work together: +The Registry Server is one part of the broader ToolHive platform. It is +different from the built-in catalog that the ToolHive CLI and UI ship with for +browsing public MCP servers, but the pieces work together: - The CLI's [`thv search`](../reference/cli/thv_search.md) and [`thv registry`](../guides-cli/registry.mdx) commands query the built-in diff --git a/docs/toolhive/guides-ui/index.mdx b/docs/toolhive/guides-ui/index.mdx index a61dcc47..dd6bc274 100644 --- a/docs/toolhive/guides-ui/index.mdx +++ b/docs/toolhive/guides-ui/index.mdx @@ -11,15 +11,18 @@ import ThemedImage from '@theme/ThemedImage'; ## Introduction -The ToolHive UI is a desktop application that makes it easy to run and manage -Model Context Protocol (MCP) servers on your local machine. It provides a -user-friendly interface to discover, deploy, and manage MCP servers with -security and ease of use built in. +The ToolHive UI is the fastest way to get from zero to a working MCP setup on +your local machine. It helps you discover servers, run them securely, and +connect your AI clients without juggling Docker commands, config files, or +manual client setup. -It's designed for anyone who wants to run MCP servers without needing to -understand the complexities of Docker or command-line tools. Whether you're a -developer, researcher, or just curious about MCP servers, ToolHive provides a -simple way to get started. +Within the ToolHive platform, the UI gives you a desktop portal for the same +local runtime and built-in registry that the CLI uses. If you want the +lowest-friction first run with ToolHive, start here. + +The UI can also connect your local AI clients to the broader ToolHive platform. +You can use it with MCP servers or gateways managed by the Kubernetes Operator, +and browse catalogs served by a ToolHive Registry Server. diff --git a/docs/toolhive/guides-ui/registry.mdx b/docs/toolhive/guides-ui/registry.mdx index f21b0341..ff685939 100644 --- a/docs/toolhive/guides-ui/registry.mdx +++ b/docs/toolhive/guides-ui/registry.mdx @@ -1,5 +1,5 @@ --- -title: Explore the registry +title: Use the registry description: Search built-in or custom registries to find and install MCP servers in the ToolHive desktop app. diff --git a/docs/toolhive/guides-vmcp/index.mdx b/docs/toolhive/guides-vmcp/index.mdx index 176294b9..35fb90e5 100644 --- a/docs/toolhive/guides-vmcp/index.mdx +++ b/docs/toolhive/guides-vmcp/index.mdx @@ -7,10 +7,18 @@ import DocCardList from '@theme/DocCardList'; ## Introduction -Virtual MCP Server (vMCP) is ToolHive's MCP gateway. It aggregates multiple -backend MCP servers into a single endpoint, giving clients unified tool access, -centralized authentication, and multi-step workflows, all through one -connection. +Virtual MCP Server (vMCP) helps when one MCP server is no longer enough. It lets +you combine multiple backend servers behind one endpoint so clients can use one +connection instead of juggling separate URLs, authentication settings, and +overlapping tool surfaces. + +Within the ToolHive platform, vMCP is the gateway layer. It gives you unified +tool access, centralized authentication, and multi-step workflows across +multiple MCP backends. + +For cluster deployments, vMCP runs as part of the ToolHive Kubernetes Operator. +If you only want to evaluate aggregation locally, see +[run vMCP locally with the CLI](./local-cli.mdx). ## Where to start @@ -18,7 +26,7 @@ connection. [Understanding Virtual MCP Server](../concepts/vmcp.mdx) for the full picture of what it does and when it's the right fit. - **Ready to deploy?** Follow the [Quickstart](./quickstart.mdx) to deploy your - first vMCP through the Kubernetes operator. + first vMCP through the Kubernetes Operator. - **Already running vMCP?** Jump to [Configuration](./configuration.mdx) or [Authentication](./authentication.mdx). - **Local testing only?** Run [vMCP locally with the CLI](./local-cli.mdx) to diff --git a/docs/toolhive/guides-vmcp/quickstart.mdx b/docs/toolhive/guides-vmcp/quickstart.mdx index 2a441d3a..a471363a 100644 --- a/docs/toolhive/guides-vmcp/quickstart.mdx +++ b/docs/toolhive/guides-vmcp/quickstart.mdx @@ -25,7 +25,8 @@ Before starting this tutorial, make sure you have: - A Kubernetes cluster with the ToolHive operator installed (see [Quickstart: Kubernetes Operator](../guides-k8s/quickstart.mdx)) - `kubectl` configured to communicate with your cluster -- An MCP client (Visual Studio Code with Copilot is used in this tutorial) +- An MCP client. Visual Studio Code with GitHub Copilot is used in this + tutorial, but any client that supports remote HTTP MCP servers will work. ## Step 1: Create an MCPGroup @@ -209,7 +210,8 @@ curl http://localhost:4483/health You should see `{"status":"ok"}`. -Add the port-forwarded vMCP endpoint as a remote server in ToolHive: +To have ToolHive manage the vMCP connection and configure your clients for you, +add the port-forwarded endpoint as a remote server with the ToolHive CLI: ```bash thv run http://localhost:4483/mcp --name demo-vmcp @@ -220,6 +222,10 @@ automatically configures your registered MCP clients to connect to it. :::tip +If you're using the ToolHive UI instead, add the same endpoint as a remote MCP +server from the app. For more details, see +[Run MCP servers](../guides-ui/run-mcp-servers.mdx). + If you haven't set up client configuration yet, run `thv client setup` to register your MCP clients. See [Client configuration](../guides-cli/client-configuration.mdx) for more details. @@ -241,18 +247,21 @@ kubectl delete mcpserver fetch osv -n toolhive-system kubectl delete mcpgroup demo-tools -n toolhive-system ``` -## What's next? +## Next steps Congratulations! You've successfully deployed vMCP and aggregated multiple backends into a single endpoint. -Next steps: - - [Configure authentication](../guides-vmcp/authentication.mdx) for production - [Customize tool aggregation](../guides-vmcp/tool-aggregation.mdx) with filtering and overrides - [Understanding Virtual MCP Server](../concepts/vmcp.mdx) +## Related information + +- [Run vMCP locally with the CLI](../guides-vmcp/local-cli.mdx) +- [Client compatibility](../reference/client-compatibility.mdx) + ## Troubleshooting
diff --git a/docs/toolhive/index.mdx b/docs/toolhive/index.mdx index 1de61de2..1c4d74b3 100644 --- a/docs/toolhive/index.mdx +++ b/docs/toolhive/index.mdx @@ -2,8 +2,8 @@ title: Introduction hide_title: true description: - ToolHive runs and manages MCP servers with built-in security, available as a - desktop app, CLI, or Kubernetes operator. + ToolHive helps you run, govern, and connect MCP servers across the desktop + app, CLI, Kubernetes Operator, vMCP, and Registry Server. --- import useBaseUrl from '@docusaurus/useBaseUrl'; @@ -22,21 +22,6 @@ import ThemedImage from '@theme/ThemedImage'; --- - - # What is ToolHive? ToolHive is an enterprise-grade open source (Apache 2.0) platform for running @@ -80,11 +65,51 @@ ToolHive Operator. -## ToolHive components +## ToolHive platform overview + +ToolHive is a platform for running, discovering, securing, and operating MCP +servers. The docs are organized by the part of the platform you're working with, +not just by deployment target. + +- [**ToolHive UI**](./guides-ui/index.mdx), + [**ToolHive CLI**](./guides-cli/index.mdx), and the + [**ToolHive Kubernetes Operator**](./guides-k8s/index.mdx) are the main ways + to run ToolHive. Choose the UI for the lowest-friction local start, the CLI + for terminal-first workflows and automation, or Kubernetes for shared, + multi-user environments. +- [**Virtual MCP Server (vMCP)**](./guides-vmcp/index.mdx) is ToolHive's MCP + gateway. It runs as part of the Kubernetes Operator for cluster deployments, + with a separate local CLI path for testing and evaluation. +- [**ToolHive Registry Server**](./guides-registry/index.mdx) is ToolHive's + registry component for hosting and curating your own catalog of MCP servers or + skills, with its own API, discoverability workflows, and access controls. It + can be deployed standalone or as part of a broader ToolHive platform + deployment. +- The **built-in registry** is the default catalog used by the ToolHive UI and + CLI to browse and install MCP servers. It is different from the Registry + Server that you deploy yourself. -ToolHive includes everything you need to use MCP servers in production. It's -made up of four key components: the Runtime, Registry Server, Gateway, and -Portal. +**Choose vMCP if** you need one endpoint that aggregates multiple backend MCP +servers with centralized authentication, routing, or tool optimization. + +**Choose Registry Server if** you want to build a trusted catalog for +discoverability, governance, publishing, or team-specific access. + +:::enterprise + +Stacklok Enterprise builds on ToolHive with centralized management, identity +provider integrations, hardened images, and platform capabilities for teams +running MCP in production. + +[Learn more about Stacklok Enterprise](./enterprise.mdx) + +::: + +## ToolHive architecture + +The platform overview above is the best place to choose where to start. This +section explains how those product surfaces map to the underlying ToolHive +architecture. + + diff --git a/docusaurus.config.ts b/docusaurus.config.ts index 0387efdb..323c8284 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -241,7 +241,7 @@ const config: Config = { docs: { sidebar: { hideable: false, - autoCollapseCategories: false, + autoCollapseCategories: true, }, }, navbar: { @@ -260,10 +260,6 @@ const config: Config = { label: 'Home', href: '/toolhive', }, - { - label: 'Integrations', - to: 'toolhive/integrations', - }, { label: 'ToolHive UI', to: 'toolhive/guides-ui', diff --git a/sidebars.ts b/sidebars.ts index 089d8ee7..6881a878 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -21,6 +21,12 @@ const crdSidebar = crdSidebarJson as SidebarItemConfig; const sidebars: SidebarsConfig = { toolhiveSidebar: [ 'toolhive/index', + { + type: 'html', + value: 'Run ToolHive', + className: 'sidebar-title', + defaultStyle: false, + }, { type: 'category', @@ -168,6 +174,13 @@ const sidebars: SidebarsConfig = { ], }, + { + type: 'html', + value: 'Platform capabilities', + className: 'sidebar-title', + defaultStyle: false, + }, + { type: 'category', label: 'Virtual MCP Server', @@ -233,6 +246,13 @@ const sidebars: SidebarsConfig = { ], }, + { + type: 'html', + value: 'Shared guides', + className: 'sidebar-title', + defaultStyle: false, + }, + { type: 'category', label: 'Concepts', @@ -308,9 +328,36 @@ const sidebars: SidebarsConfig = { items: [{ type: 'autogenerated', dirName: 'toolhive/guides-mcp' }], }, - 'toolhive/reference/client-compatibility', - 'toolhive/reference/index', - 'toolhive/reference/authz-policy-reference', + { + type: 'html', + value: 'Reference', + className: 'sidebar-title', + defaultStyle: false, + }, + { + type: 'category', + label: 'Technical reference', + link: { + type: 'doc', + id: 'toolhive/reference/index', + }, + collapsible: false, + collapsed: false, + items: [ + 'toolhive/reference/client-compatibility', + { + type: 'doc', + id: 'toolhive/reference/authz-policy-reference', + label: 'Authorization policies', + }, + ], + }, + { + type: 'html', + value: 'Help', + className: 'sidebar-title', + defaultStyle: false, + }, 'toolhive/faq', 'toolhive/enterprise', 'toolhive/support', diff --git a/src/css/custom.css b/src/css/custom.css index 151fab84..2cbb2de0 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -201,6 +201,21 @@ thead th { color: var(--stacklok-cookie); } +.theme-doc-sidebar-menu .sidebar-title { + margin: 1.35rem 0 0.4rem; + padding: 0 0.75rem; + color: var(--stacklok-sunset); + font-size: 0.72rem; + font-weight: 700; + letter-spacing: 0.08em; + text-transform: uppercase; + pointer-events: none; +} + +html[data-theme='dark'] .theme-doc-sidebar-menu .sidebar-title { + color: var(--stacklok-green-grass); +} + [data-theme='dark'] .pagination-nav__link { background-color: rgba(255, 255, 255, 0.08); }