add guide for proxy stdio to integrate with claude desktop

[yrobla]

Description

Added a new guide for Claude desktop integration with proxy stdio command

Related issues/PRs

Screenshots

Merge checklist

Content

• 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
• 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	Oct 8, 2025 7:52am

[Copilot]

Pull Request Overview

This PR adds a comprehensive guide for using the thv proxy stdio command to enable Claude Desktop and other stdio-only MCP clients to connect to servers using SSE or HTTP transport protocols. The guide explains how ToolHive's proxy feature bridges the compatibility gap between different transport methods.

Key changes:

• Added new proxy stdio guide with practical examples and step-by-step instructions
• Updated Claude Desktop compatibility status from unsupported to fully supported
• Integrated the new guide into the documentation sidebar structure

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
sidebars.ts	Added the new proxy stdio guide to the CLI guides section
docs/toolhive/guides-cli/proxy-stdio.mdx	New comprehensive guide explaining proxy stdio functionality with Claude Desktop integration example
docs/toolhive/_partials/_client-compat-table.md	Updated Claude Desktop compatibility from unsupported to fully supported with version requirement

[danbarr]

@yrobla I was assuming this would just replace the current workaround in the "STDIO-only client configuration" section of the client compatibility guide, is that not right?

[yrobla]

@yrobla I was assuming this would just replace the current workaround in the "STDIO-only client configuration" section of the client compatibility guide, is that not right?

ah ok, let me move the documentation there