Skip to content

Conversation

eleftherias
Copy link
Member

Description

Added a note that STDIO servers on kubernetes aren't intended to work with multiple users or multiple MCP clients. This was not explicitly stated before.

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

@Copilot Copilot AI review requested due to automatic review settings October 15, 2025 14:23
@vercel
Copy link

vercel bot commented Oct 15, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs-website Ready Ready Preview Comment Oct 15, 2025 2:25pm

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds documentation clarifying a limitation of STDIO transport for MCP servers in Kubernetes environments. The change emphasizes that STDIO servers only support single client connections and recommends alternative transports for multi-user scenarios.

  • Added an informational callout explaining STDIO transport's single-client limitation
  • Provided guidance to use SSE or Streamable HTTP transport for multi-user/concurrent scenarios

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@eleftherias eleftherias merged commit 76881a4 into main Oct 16, 2025
6 checks passed
@eleftherias eleftherias deleted the stdio-limitation branch October 16, 2025 12:52
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.

2 participants