Skip to content

Split CLI "Run MCP servers" guide into three pages#981

Open
danbarr wants to merge 9 commits into
mainfrom
split-cli-run-mcp-servers-guide
Open

Split CLI "Run MCP servers" guide into three pages#981
danbarr wants to merge 9 commits into
mainfrom
split-cli-run-mcp-servers-guide

Conversation

@danbarr

@danbarr danbarr commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Description

Splits the CLI Run MCP servers guide, which had grown to ~1,290 lines with five top-level sections covering distinct reader journeys, into three focused pages:

  • Run MCP servers - registry and custom (Docker image / protocol scheme) launch mechanics, plus share and reuse configurations.
  • Run remote MCP servers (new) - connecting to remotely hosted servers by URL, including OAuth, OIDC, and bearer token authentication.
  • Configure MCP servers (new) - shared customization options, grouped into options that apply to all servers and options that only affect container-based servers (the distinction the original undifferentiated list glossed over, where several flags are no-ops for remote servers).

The CLI sidebar gains the two new pages under the "Run MCP servers" category, and inbound anchored links in connect-clients.mdx and tool-optimization.mdx are repointed to the new pages.

No vercel.json redirects are added: the split only moves in-page anchors, and the page paths themselves are unchanged. URL fragments are never sent to the server, so redirects cannot catch them.

A few related fixes are folded in: the audit logging section now documents thv logs --proxy (audit middleware runs in the proxy process, not the container), and the network isolation guidance reflects the new on-by-default behavior from the v0.30.1 update.

Type of change

  • Documentation update
  • Navigation/structure change

Related issues/PRs

Closes #937

Screenshots

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Navigation

  • New pages include a frontmatter section with title and description at a minimum
  • Sidebar navigation (sidebars.ts) updated for added, deleted, reordered, or renamed files

Reviewer checklist

Content

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

danbarr and others added 5 commits June 26, 2026 10:11
The run-mcp-servers guide had grown to ~1,290 lines with five top-level
sections covering distinct reader journeys. Split it into three focused
pages:

- Run MCP servers: registry and custom (Docker/protocol) launch
  mechanics, plus share and reuse configurations
- Run remote MCP servers: remote setup and authentication
- Configure MCP servers: shared options, grouped into cross-cutting
  options and container-based-only options

Update the CLI sidebar and repoint inbound anchored links in
connect-clients and tool-optimization. No vercel redirects are added
because the split only moves in-page anchors, which redirects cannot
catch.

Closes #937

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Audit middleware runs in the ToolHive proxy process, so audit events
are written to the proxy's logs. Viewing them requires the --proxy flag
on thv logs; the default command shows the MCP server container's logs,
which don't include audit events.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The --secret flag injects values into the container environment, so it
has no effect on remote servers. Group it with the other container-based
options next to environment variables instead of listing it as a
cross-cutting option with a caveat.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The box explains the core mechanics of running a registry server, so it
belongs next to the local and remote run examples rather than after the
groups subsection, which is an orthogonal organizational feature.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Use notion-remote in the run example so it demonstrates the suffix
inline, trim the note to the convention itself, and drop the discovery
tip that the registry page already covers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 26, 2026 14:19
@vercel

vercel Bot commented Jun 26, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Jun 26, 2026 5:21pm

Request Review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Splits the previously monolithic CLI “Run MCP servers” guide into smaller, task-focused pages (remote server workflow vs. shared configuration), and updates sidebar/navigation and cross-links so readers can land directly on the right journey without wading through unrelated sections.

Changes:

  • Adds two new CLI guides: Run remote MCP servers and Configure MCP servers.
  • Refactors Run MCP servers to focus on registry + local/custom launch mechanics and link out to the new pages.
  • Updates sidebar structure and repoints inbound links from Kubernetes/concepts docs to the new pages/anchors.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.

Show a summary per file
File Description
sidebars.ts Adds the two new CLI guide pages under the “Run MCP servers” category.
docs/toolhive/guides-k8s/connect-clients.mdx Updates a remote-auth cross-link to point at the new remote guide.
docs/toolhive/guides-cli/run-remote-mcp-servers.mdx New page documenting remote-by-URL workflow and auth options.
docs/toolhive/guides-cli/run-mcp-servers.mdx Trims/reshapes the main run guide and links out to the new pages.
docs/toolhive/guides-cli/configure-mcp-servers.mdx New page extracting shared configuration flags and guidance.
docs/toolhive/concepts/tool-optimization.mdx Repoints “Customize tools (CLI)” to the new canonical section/anchor.

Comment thread docs/toolhive/guides-cli/configure-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/configure-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/configure-mcp-servers.mdx
Comment thread docs/toolhive/guides-cli/configure-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/run-remote-mcp-servers.mdx
Comment thread docs/toolhive/guides-cli/run-remote-mcp-servers.mdx
Comment thread docs/toolhive/guides-cli/run-remote-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/run-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/run-mcp-servers.mdx Outdated
Comment thread docs/toolhive/guides-cli/run-mcp-servers.mdx
- Replace container-centric wording in cross-cutting config options
  (workload name, foreground until server stops, generic proxy target).
- Mark --publish as container-only in the port section.
- Note --remote-auth-client-secret-file for OIDC and OAuth2 setup.
- Reword run page intro bullet so volume mounts don't imply remote
  servers.
- Trim Next steps sections to three forward links per docs guidelines.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Align the configure guide's option grouping with the "local" vs
"remote" terminology used in the UI guide and elsewhere in the CLI
section (the run page already says "local containerized servers"). Keep
the container explanation in the body so the reason these options skip
remote servers stays clear.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Split the CLI "Run MCP servers" guide into run-mode and configuration pages

2 participants