Document volume mounts using the UI

[kantord]

Description

Add documentation for the volume mounting feature in the UI.

Related issues/PRs

Feature PR: stacklok/toolhive-studio#701

Closes #111

Merge checklist

Content

• (N/A) New pages include a frontmatter section with title and description at a minimum
• (N/A) Sidebar navigation (sidebars.ts) updated for added, deleted, reordered, or renamed files
• (N/A) Redirects added to vercel.json for moved, renamed, or deleted pages (i.e., if the URL slug changed)

Reviews

• Content has been reviewed for technical accuracy
• Content has been reviewed for spelling, grammar, and style

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs-website	✅ Ready	Preview	Comment	Aug 14, 2025 5:58pm

[Copilot]

Pull Request Overview

This PR adds documentation for mounting host files and folders (volumes) through the ToolHive UI, addressing issue #111. The documentation explains how users can configure volume mounts when installing MCP servers to provide access to local files and directories.

Key changes:

• Added a new section explaining volume mounting functionality in the UI
• Documented the step-by-step process for configuring storage volumes
• Clarified that volume mounts work for both registry-installed and custom servers

[danbarr]

Since this is part of the install steps / configuration form, it would be good to note it as a step in those sections so users find it in context.

Could add a step to each process above (for example in the registry flow it would be between steps 2 and 3) and link to the anchor (one is created automatically for every heading, or you can make a shorter anchor name by adding something like {#volumes} on the heading line)

[kantord]

Since this is part of the install steps / configuration form, it would be good to note it as a step in those sections so users find it in context.

Could add a step to each process above (for example in the registry flow it would be between steps 2 and 3) and link to the anchor (one is created automatically for every heading, or you can make a shorter anchor name by adding something like {#volumes} on the heading line)

good point! thanks for the tip about the short anchor names as well!