mcp-source

Switches the MCP for Unity package source in Unity project manifests between branches and local checkouts.

13.8k|1.5k|Updated Mar 18, 2025
One-click install
npx skills add https://github.com/CoplayDev/unity-mcp --skill mcp-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-source
Source: https://github.com/CoplayDev/unity-mcp/tree/main/.claude/skills/mcp-source
Command: npx skills add https://github.com/CoplayDev/unity-mcp --skill mcp-source

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mcp-source

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch the MCP for Unity package to a different branch?

Run /mcp-source with the branch argument to point your Unity project's manifest.json at your current remote branch. The skill detects your git branch and origin URL, then rewrites the com.coplaydev.unity-mcp dependency to use that branch reference.

How do I test a local checkout of unity-mcp in my Unity project?

Use /mcp-source local to replace the package dependency with a file: reference pointing to your local repository's MCPForUnity folder. Unity then loads the package directly from disk so edits take effect on re-resolve.

Does the skill update multiple Unity projects at once?

Yes, it discovers all connected Unity instances via MCP resources or searches the filesystem for Packages/manifest.json files. When multiple manifests are found, it updates all of them after confirming with the user.

What happens if my git remote uses SSH instead of HTTPS?

The skill automatically converts SSH origins like [email protected]: into HTTPS URLs before building the package reference. This ensures the resulting git URL works with Unity Package Manager resolution.

Why does Unity not pick up the new package source after switching?

Unity usually re-resolves the package automatically after manifest.json changes. If it does not, open the Package Manager window and click Refresh to force re-resolution of the updated dependency.