Skip to content

Conversation

@Scriptwonder
Copy link
Collaborator

@Scriptwonder Scriptwonder commented Jan 27, 2026

Description

Type of Change

Save your change type

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)
  • Test update

Changes Made

Testing/Screenshots/Recordings

Documentation Updates

  • I have added/removed/modified tools or resources
  • If yes, I have updated all documentation files using:
    • The LLM prompt at tools/UPDATE_DOCS_PROMPT.md (recommended)
    • Manual updates following the guide at tools/UPDATE_DOCS.md

Related Issues

Additional Notes

Summary by Sourcery

Update MCP for Unity documentation to use the new uvx-based server invocation instead of legacy uv commands.

Documentation:

  • Refresh MCP client configuration examples across English and Chinese docs to show uvx-based stdio setup for macOS, Linux, and Windows.
  • Clarify the Unity MCP window documentation to reference the local Server folder as a dev-only option when using uvx.

Summary by CodeRabbit

  • Documentation
    • Updated MCP server configuration guidance and setup instructions across multiple documentation sources.
    • Clarified server folder setup requirements with added development environment notes.
    • Revised configuration examples and command syntax structure across English and localized documentation versions.
    • Enhanced consistency of setup instructions and examples for all supported platforms and configurations.

✏️ Tip: You can customize this high-level summary in your review settings.

Copilot AI review requested due to automatic review settings January 27, 2026 04:32
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jan 27, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates documentation to reflect the new uvx-based command for running the MCP for Unity server, replacing legacy direct uv/uv.exe invocations and clarifying when local server folders are needed.

Flow diagram for platform-specific uvx stdio configuration

flowchart TD
  A["Need manual MCP for Unity setup"] --> B["Determine platform"]
  B --> C["macOS or Linux"]
  B --> D["Windows"]

  C --> E["Set mcpServers.unityMCP.command to uvx"]
  C --> F["Set mcpServers.unityMCP.args to [--from, mcpforunityserver, mcp-for-unity, --transport, stdio]"]

  D --> G["Set mcpServers.unityMCP.command to C:/Users/YOUR_USERNAME/AppData/Local/Microsoft/WinGet/Links/uvx.exe"]
  D --> H["Set mcpServers.unityMCP.args to [--from, mcpforunityserver, mcp-for-unity, --transport, stdio]"]

  E --> I["Save MCP client config"]
  F --> I
  G --> I
  H --> I

  I --> J["Optionally run uvx command manually to verify server"]
  J --> K["Restart MCP client and check connection"]
Loading

File-Level Changes

Change Details Files
Update Cursor help docs to use uvx tool invocation instead of direct uv path and server.py execution.
  • Change Windows mcpServers configuration example to call uvx.exe instead of uv.exe.
  • Replace previous uv run --directory ... server.py arguments with uvx --from mcpforunityserver mcp-for-unity --transport stdio.
  • Update the example PowerShell verification command to match the new uvx-based invocation.
  • Remove trailing blank line at end of file.
docs/guides/CURSOR_HELP.md
Update main README examples to show uvx-based stdio configuration for macOS/Linux and Windows.
  • Change configuration section title from legacy wording to indicate uvx usage.
  • Update macOS/Linux JSON example to use command "uvx" and uvx-style args instead of uv run server.py in a local directory.
  • Update Windows JSON example to use uvx.exe path and uvx-style args instead of uv.exe with run --directory server.py.
README.md
Update Chinese README examples to mirror uvx-based stdio configuration examples in the main README.
  • Adjust summary description to indicate uvx-based configuration instead of legacy.
  • Update macOS/Linux JSON example to use uvx and new argument style.
  • Update Windows JSON example to use uvx.exe path and new argument style.
docs/i18n/README-zh.md
Clarify MCPForUnity README instructions around selecting the server folder when using uvx.
  • Update the description of the "Select server folder…" action to indicate it is for choosing the local Server folder for development only and usually not needed with uvx.
  • Ensure file ends with a newline instead of a trailing horizontal rule.
MCPForUnity/README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@Scriptwonder Scriptwonder merged commit feb9e3b into CoplayDev:beta Jan 27, 2026
5 of 6 checks passed
@Scriptwonder Scriptwonder deleted the manual-01 branch January 27, 2026 04:32
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 27, 2026

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes update documentation across multiple files to shift the MCP server invocation from using uv with directory/server.py arguments to using uvx with --from mcpforunityserver and mcp-for-unity arguments, affecting configuration guides and README files.

Changes

Cohort / File(s) Summary
Core README files
MCPForUnity/README.md, README.md
Updated server folder guidance and stdio configuration from uv to uvx command; replaced argument pattern from --directory <path> run server.py to --from mcpforunityserver mcp-for-unity --transport stdio
Documentation guides
docs/guides/CURSOR_HELP.md, docs/i18n/README-zh.md
Updated MCP Unity configuration examples and manual PowerShell invocations from uv.exe/uv to uvx.exe/uvx with corresponding argument structure changes; removed trailing blank line

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested reviewers

  • msanatan

Poem

🐰 From uv to uvx we hop and bound,
With --from mcpforunityserver calls so sound,
Docs updated, configs aligned,
A cleaner path for users to find! ✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • In the updated stdio examples, macOS/Linux now use bare uvx while Windows uses a hardcoded WinGet path; consider adding a brief note that the Windows path may differ if uvx is installed another way and that users can call uvx directly if it’s on PATH to avoid confusion.
  • The description for “Select server folder…” now mentions the local Server folder but doesn’t specify a concrete path or example; adding a short example path (e.g., relative to the project) would make it clearer for developers where this folder typically lives.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In the updated stdio examples, macOS/Linux now use bare `uvx` while Windows uses a hardcoded WinGet path; consider adding a brief note that the Windows path may differ if uvx is installed another way and that users can call `uvx` directly if it’s on PATH to avoid confusion.
- The description for “Select server folder…” now mentions the local `Server` folder but doesn’t specify a concrete path or example; adding a short example path (e.g., relative to the project) would make it clearer for developers where this folder typically lives.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

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 updates the manual MCP server configuration commands from the legacy uv run --directory approach to the modern uvx --from mcpforunityserver mcp-for-unity approach across all documentation files.

Changes:

  • Updated stdio configuration examples from uv to uvx with package-based installation
  • Changed section label from "Stdio configuration (legacy)" to "Stdio configuration (uvx)"
  • Clarified that the "Select server folder" option is for development only when using uvx

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
README.md Updated stdio configuration examples to use uvx with package-based installation for macOS/Linux and Windows
docs/i18n/README-zh.md Updated Chinese translation of stdio configuration examples to match README.md changes
docs/guides/CURSOR_HELP.md Updated Windows troubleshooting examples to use uvx command syntax
MCPForUnity/README.md Clarified that server folder selection is dev-only and usually not needed with uvx

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

1 participant