Playcanvas Mcp Server

A Claude Code plugin marketplace for OnRush Studio. One repo, several plugins, plus a popup-driven manager (/onrush-setup) so you can pick which plugins are active in each project — no terminal commands needed once it's installed.

This README walks you through installing it from a local copy on your own machine (clone it, then point Claude Code at the folder). You stay in control of the source — to update, you git pull your copy. Nothing installs straight off a remote.

What's inside

Plugin	What it does
onrush	The manager. /onrush-setup (alias /ors-setup) opens a popup checklist of the other OnRush plugins and turns them on/off for the current project — the popup is the installer. /onrush-update (alias /ors-update) re-vendors this project's plugin copies from your local clone.
github-commits-manager	End-of-session reminder to commit the files you changed this session (per-session baseline, so only this session's edits are flagged). Configure with /onrush-commits-settings (alias /ors-gcm-settings).
chrome-session-helper	Launches Chrome at session start so browser-based tools are reachable. No-op if Chrome is already running.

Before you start

You'll need:

• Claude Code (CLI, desktop, or IDE extension) — the /plugin commands below run inside a Claude Code session.
• git — to clone this repo and to pull updates later.
• python (python3 or python on PATH) — the manager uses it for the install/update work.
• bash + standard Unix tools (git, awk, sort, comm, grep; jq optional) — the hooks are bash scripts. On Windows, Git Bash / MSYS2 provides these; macOS and Linux have them natively.

Install with an AI (copy-paste prompt)

Don't want to do it by hand? Paste the prompt below to an AI assistant (Claude Code, Cursor, etc.). It clones the repo for you, verifies it, then hands you the short list of interactive Claude Code commands to finish — those /plugin … steps are interactive slash commands you type inside a Claude Code session, so the AI can't run them for you.

Set up the OnRush-Plugins Claude Code marketplace on my machine from a local clone.

CLONE IT INTO THIS FOLDER ⇒ [FILL IN — the folder to clone into, NO spaces, e.g. C:/Users/me/dev]

Do this for me now:
1. cd into the folder above, then clone the repo there:
      git clone https://github.com/MetaHumanREAL/OnRush-Plugins.git
   (this creates an OnRush-Plugins/ subfolder inside it)
2. Verify the clone worked — confirm <that-folder>/OnRush-Plugins/.claude-plugin/marketplace.json exists.
3. Tell me the absolute path to the cloned OnRush-Plugins folder.

Then STOP and give me these steps to run myself. They are interactive Claude Code slash
commands I have to type inside a Claude Code session — they are NOT terminal commands:
   1. Open a Claude Code session (the `claude` CLI, desktop app, or IDE extension).
   2. Register the local marketplace. From inside the cloned folder, run:
         /plugin marketplace add .
      …or from anywhere, using the path you gave me:
         /plugin marketplace add <clone-path>
   3. Install the manager:   /plugin install onrush@onrush-plugins
   4. Reload so it loads:    /reload-plugins
   5. Open whichever project I want OnRush plugins in, and run:   /onrush-setup
      then tick the plugins I want active in that project.

Prefer to do it manually? The same steps, by hand:

Install (from your local copy)

1. Clone this repo to your machine

Put it anywhere you like. A path without spaces is easiest (it avoids quoting headaches later):

git clone https://github.com/MetaHumanREAL/OnRush-Plugins.git

This gives you a local OnRush-Plugins/ folder. That folder — the one containing .claude-plugin/marketplace.json — is what Claude Code will register as a marketplace.

2. Register the folder as a local marketplace

You only do this once per machine; the registration is global and persists across all your projects.

Easiest way — from inside the clone. Open a Claude Code session with the cloned folder as your working directory, then run:

/plugin marketplace add .

From anywhere — give the path. Use forward slashes; quote it if the path has spaces:

# macOS / Linux
/plugin marketplace add ~/OnRush-Plugins

# Windows (forward slashes work fine inside the command)
/plugin marketplace add C:/Users/you/OnRush-Plugins

Claude Code reads .claude-plugin/marketplace.json and registers the marketplace under its name, onrush-plugins. Confirm it's there:

/plugin marketplace list

3. Install and enable the onrush manager

/plugin install onrush@onrush-plugins

(onrush is the plugin name; onrush-plugins is the marketplace name — name@marketplace.) Then reload so its skills load:

/reload-plugins

You now have /onrush-setup available. You do not install the other plugins this way — the manager vendors them into each project for you (next step).

4. Pick plugins for a project

Switch to (or open a Claude Code session in) any project you're working on, and run:

/onrush-setup

A popup lists each OnRush plugin with a tab; tick the ones you want on in this project. The manager copies their files into the project's .claude/onrush/<plugin>/, wires .claude/settings.json, and records everything in .claude/onrush/onrush.lock.json. Reload the session afterward so newly enabled hooks and commands take effect.

Repeat step 4 in every project where you want OnRush plugins — each project keeps its own set.

Updating

Local marketplaces don't auto-update, so you refresh on your own schedule:

1. Pull the latest code into your clone:

   git -C path/to/OnRush-Plugins pull
   

2. Refresh Claude Code's view of the marketplace and reload:

   /plugin marketplace update onrush-plugins
   /reload-plugins
   

3. Re-vendor a project's plugins from the freshened source — run this inside the project:

   /onrush-update
   

   (alias /ors-update)

Two layers of control

There are two independent switches, and it helps to keep them straight:

• Which plugins are on in a project — handled by onrush via /onrush-setup, which vendors the chosen plugins into that project's .claude/.
• Settings inside a single plugin — handled by that plugin's own config command. For example, /onrush-commits-settings chooses how github-commits-manager behaves (auto-commit / prompt first / wait for review).

Removing it

• Turn a plugin off in one project — run /onrush-setup there and disable it.
• Remove the manager — run /plugin, open the Installed tab, select onrush, and disable/uninstall it from there.
• Drop the marketplace entirely — /plugin marketplace remove onrush-plugins (this also uninstalls plugins you installed from it).

Troubleshooting

• /onrush-setup isn't found after install. Run /reload-plugins (or restart the session) so newly installed skills load.
• A hook didn't fire after enabling a plugin. Newly wired hooks load on the next session — reload or restart.
• marketplace.json not found when adding. Point the command at the folder that contains .claude-plugin/marketplace.json (the repo root), not at a subfolder.
• Hooks fail on Windows. The hooks are bash scripts — make sure Git Bash / MSYS2 is installed and bash is on PATH. .gitattributes forces LF line endings on *.sh so they run cleanly cross-platform.

Repo layout

OnRush-Plugins/
├── .claude-plugin/
│   └── marketplace.json          # the marketplace manifest — lists every plugin
├── onrush/                       # the manager plugin
│   ├── .claude-plugin/plugin.json
│   ├── scripts/onrush.py         # deterministic install/update helper
│   └── skills/                   # /onrush-setup, /onrush-update (+ /ors-* aliases)
├── github-commits-manager/
│   ├── .claude-plugin/plugin.json
│   ├── hooks/{hooks.json,snapshot-baseline.sh,check-inscope-commit.sh}
│   └── commands/config.md
└── chrome-session-helper/
    ├── .claude-plugin/plugin.json
    └── hooks/{hooks.json,ensure-chrome.sh}

Contributing a plugin

Adding or maintaining a plugin in this marketplace has its own playbook — see CLAUDE.md for the full checklist (slug rules, the onrush.install.json descriptor, catalog wiring, and how to test an install without touching a real project).