Skip to content

Add Windows compatibility guidance for MCP stdio connections #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 23, 2025

Conversation

DennisTraub
Copy link
Contributor

Problem

The current MCP stdio documentation only shows the Unix/Linux variant of the uvx command, causing Windows users to encounter MCPClientInitializationError: background thread did not start in 30 seconds when following the examples.

Solution

  • Added platform-specific examples showing the correct uvx command syntax for both Windows and macOS/Linux
  • Used multi-line array formatting for better readability across different screen sizes
  • Added explanatory comments to clarify platform differences

Changes

  • Windows: Requires --from flag and .exe extension: ["--from", "package@version", "package.exe"]
  • macOS/Linux: Uses simple format: ["package@version"]

Testing

  • Verified Windows example resolves the reported timeout issue
  • Confirmed macOS/Linux example maintains backward compatibility

Related to strands-agents/sdk-python#71 (provides workaround until framework fix is implemented)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

- Add platform-specific uvx command examples for Windows vs macOS/Linux
- Use multi-line array formatting for better readability on narrow screens
- Addresses Windows MCP client initialization timeout issues
Copy link
Member

@zastrowm zastrowm left a comment

Choose a reason for hiding this comment

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

Really appreciate the details and deep dive that went into this

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