mcp-source

Switch the MCP for Unity package source in Unity project manifests between branches or local checkouts.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/cmitchellVFS/Scrabble --skill mcp-source-cmitchellvfs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-source
Source: https://github.com/cmitchellVFS/Scrabble/tree/main/.claude/skills/mcp-source
Command: npx skills add https://github.com/cmitchellVFS/Scrabble --skill mcp-source-cmitchellvfs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working on the MCP for Unity package need to point Unity projects at different package sources (stable main, beta, a PR branch, or a local checkout) and manually editing each project's Packages/manifest.json is repetitive and error-prone. ## Core Features & Use Cases - Source Switching: Swap 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 (mcpforunity://project/info) or falls back to a filesystem search for Packages/manifest.json files. - Git Context Detection: Reads repo root, current branch, and origin URL (normalizing SSH to HTTPS) to build correct package URLs. - Use Case: You are testing a pull request on the unity-mcp repo and want your connected Unity projects to resolve the package from your branch instead of the stable release. ## Quick Start Run /mcp-source branch to point all connected Unity projects at your current git branch of the unity-mcp repository.

Frequently Asked Questions about mcp-source

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

FAQPage Schema
How do I switch a Unity package to a local development checkout?▼

Run /mcp-source local to replace the com.coplaydev.unity-mcp dependency in each discovered Packages/manifest.json with a file: reference pointing at your local repo's MCPForUnity folder. Unity then re-resolves the package from disk.

How do I test a unity-mcp pull request branch in my Unity project?▼

Use /mcp-source branch while checked out on the PR branch. The skill builds a git URL from your HTTPS-normalized origin and current branch name, then updates the manifest dependency so Unity fetches that branch.

Does this work when no Unity MCP instance is connected?▼

Yes. If no MCP instances are available, the skill falls back to searching the filesystem for Packages/manifest.json files up to three levels deep and updates all manifests it finds, after confirming with you.

Why is my Unity package not updating after the manifest change?▼

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

What package sources can a Unity manifest dependency point to?▼

This skill supports four sources: the upstream main branch, the upstream beta branch, an arbitrary remote branch via git URL with a path query, and a local directory via a file: reference for live development.