mcp-source
Skill16 starsChanged 4 months agoMITView on GitHub
Switch MCP for Unity package source in connected Unity projects. Use /mcp-source [main|beta|branch|local] to swap between upstream releases, your remote branch, or local dev checkout.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- CoplayDev/unity-mcpword for word, first seen Jan 7, 2026
Other versions1 project uses a version of this.
Word for word · 1
- CoplayDev/unity-mcp★ 16k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- animation-vocabularySkill
- blender-to-unitySkill
- emil-design-engSkill
- gsap-coreSkill
- gsap-frameworksSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-reactSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- higgsfield-generateSkill
- higgsfield-marketplace-cardsSkill
- higgsfield-product-photoshootSkill
- higgsfield-soul-idSkill
- higgsfield-websitesSkill
- kernel-chat-art-directionSkill
- kernel-chat-design-qaSkill
- kernel-chat-web-designSkill
- micro-interactionsSkill
- microinteractionsSkill
- motion-designSkill
- review-animationsSkill
- unity-mcp-orchestratorSkill
- motion-prompt-languageSkill
- kernel-chat-designSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If empty or not one of the four valid values, ask the user to choose:
- Distinctive: line 30
Run these git commands from the current working directory to find the unity-mcp repo:
- Very specific: line 45
Read mcpforunity://project/info for each connected Unity instance (use ListMcpResourcesTool to find available instances).
- Very specific: line 48
If no MCP instances are connected, search upward from the current working directory for Packages/manifest.json files using Bash:
- Distinctive: line 53
If multiple manifests are found, update all of them (confirming with the user first).
- Distinctive: line 73
Read the file with the Read tool
- Distinctive: line 75
Use the Edit tool to replace the old value with the new URL
- Distinctive: line 80
After updating, tell the user:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Switch MCP for Unity Package Source
You are switching the com.coplaydev.unity-mcp package source in one or more Unity projects.
allowed-tools
Bash, Read, Edit, ReadMcpResourceTool, ListMcpResourcesTool
Instructions
1. Parse arguments
The user's argument is: $ARGUMENTS
Valid values: main, beta, branch, local, or empty.
If empty or not one of the four valid values, ask the user to choose:
- main — upstream main branch (stable releases)
- beta — upstream beta branch (pre-release)
- branch — your current remote branch (for testing a PR)
- local — local file reference to your checkout (for live dev iteration)
2. Detect repo context
Run these git commands from the current working directory to find the unity-mcp repo:
git rev-parse --show-toplevel # → repo_root
git rev-parse --abbrev-ref HEAD # → branch_name
git remote get-url origin # → origin_urlConvert SSH origins to HTTPS: if origin_url starts with git@github.com:, transform it to https://github.com/{owner}/{repo}.git.
3. Discover target Unity projects
Try two approaches to find Packages/manifest.json files to update:
Approach A — MCP resources (preferred):
Read mcpforunity://project/info for each connected Unity instance (use ListMcpResourcesTool to find available instances). Extract projectRoot and use {projectRoot}/Packages/manifest.json.
Approach B — filesystem fallback:
If no MCP instances are connected, search upward from the current working directory for Packages/manifest.json files using Bash:
find "$(pwd)" -maxdepth 3 -name "manifest.json" -path "*/Packages/manifest.json" 2>/dev/nullIf multiple manifests are found, update all of them (confirming with the user first).
4. Build the package URL
Based on the user's selection, construct the dependency value:
| Selection | URL |
main | https://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#main |
beta | https://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#beta |
branch | {origin_https}?path=/MCPForUnity#{branch_name} |
local | file:{repo_root}/MCPForUnity |
For branch: use the HTTPS-normalized origin URL and current git branch name.
For local: use the absolute path to the repo root with file: prefix (no //), e.g. file:/Users/davidsarno/unity-mcp/MCPForUnity.
5. Update each manifest
For each discovered manifest.json:
- Read the file with the Read tool
- Find the
"com.coplaydev.unity-mcp"dependency line - Use the Edit tool to replace the old value with the new URL
- Report what was changed: old value → new value, file path
6. Report results
After updating, tell the user:
- Which manifests were updated
- The old and new package source values
- Remind them: "Unity will re-resolve the package automatically. If it doesn't, open Package Manager and click Refresh."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

