What problem does it solve?
Developers working on MCP for Unity need to point their Unity projects at different package sources — stable releases, beta branches, PR branches, or a local checkout — and manually editing each project's manifest.json is repetitive and error-prone.
Core Features & Use Cases
- Source Switching: Swaps the com.coplaydev.unity-mcp dependency between upstream main, beta, your current remote branch, or a local file reference.
- Automatic Project Discovery: Finds target Unity projects via connected MCP instances or by searching the filesystem for Packages/manifest.json files.
- Git Context Detection: Reads the repo root, current branch, and origin URL to build correct package URLs, converting SSH remotes to HTTPS.
- Use Case: You are testing a pull request for unity-mcp and want your Unity project to load the package from your feature branch instead of the stable release.
Quick Start
Ask the assistant to run /mcp-source with main, beta, branch, or local to switch the MCP for Unity package source in your connected Unity projects.