npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

unity-open-mcp

v0.5.0

Published

MCP server (stdio) routing tool calls to the live Unity Open MCP Bridge or batch Unity processes.

Readme

unity-open-mcp

npm version license

MCP server (stdio) that routes Model Context Protocol tool calls to a live Unity Editor via the Unity Open MCP Bridge, with batch (headless Unity) and offline (disk-parse) fallbacks. Works with Cursor, Claude Desktop, Claude Code, OpenCode, ZCode, and any MCP stdio client.

Install

Node.js 18+ is required (the server is a Node process spawned by your MCP client).

You do not need to install this package yourself — your MCP client spawns it via npx. The sections below show both the zero-install npx path and the optional global install.

Configure your MCP client

Pick your client and merge the matching config. Replace /path/to/your/unity/project with the absolute path to your Unity project root.

Cursor or Claude Desktop

Edit ~/.cursor/mcp.json (Cursor) or your Claude Desktop MCP config file:

{
  "mcpServers": {
    "unity-open-mcp": {
      "command": "npx",
      "args": ["-y", "[email protected]"],
      "env": {
        "UNITY_PROJECT_PATH": "/path/to/your/unity/project"
      }
    }
  }
}

OpenCode (global)

Edit ~/.config/opencode/opencode.json:

{
  "mcp": {
    "unity-open-mcp": {
      "type": "local",
      "command": ["npx", "-y", "[email protected]"],
      "enabled": true,
      "environment": {
        "UNITY_PROJECT_PATH": "/path/to/your/unity/project"
      }
    }
  }
}

For a project-scoped config, put the same mcp.unity-open-mcp block in opencode.json at your Unity project root.

Claude Code (CLI)

claude mcp add unity-open-mcp \
  --env UNITY_PROJECT_PATH=/path/to/your/unity/project \
  -- npx -y [email protected]

Bridge port. The bridge HTTP port is derived from the project path (20000 + sha256(path) % 10000, so two projects never collide), and the server discovers it via the bridge's lock file — so you usually do not need to set a port at all. The Unity Hub Pro wizard computes it for you. Set UNITY_OPEN_MCP_BRIDGE_PORT only when you want to pin a specific port.

Optional: global install

If you prefer a one-time install over npx re-resolving on each spawn:

npm install -g unity-open-mcp

Then use "command": "unity-open-mcp", "args": [] (Cursor / Claude Desktop) or "command": ["unity-open-mcp"] (OpenCode) in your client config. Update with npm update -g unity-open-mcp.

Environment variables

| Variable | Required | Purpose | |---|---|---| | UNITY_PROJECT_PATH | yes | Absolute path to your Unity project root. | | UNITY_OPEN_MCP_BRIDGE_PORT | no | Bridge HTTP port override. When unset, the port is derived deterministically from the project path (20000 + sha256(path) % 10000) and discovered via the bridge's lock file. Set only to pin a specific port. | | UNITY_PATH | no | Unity Editor executable for batch-only (headless) tools. |

How it works

  1. The Unity Open MCP Bridge package runs inside the Unity Editor and exposes an HTTP listener on 127.0.0.1.
  2. This MCP server connects to that bridge, routes tool calls to it, and returns the results over MCP stdio to your AI client.
  3. When the live Editor is unavailable, supported tools fall back to headless Unity (batch) or offline disk parsing.

The bridge package must be installed in your Unity project. See the manual setup guide for the Packages/manifest.json entries.

CLI

The same binary is a thin CLI for scripting and CI:

npx unity-open-mcp wait-for-ready --project /path/to/MyGame
npx unity-open-mcp ping --project /path/to/MyGame --json
npx unity-open-mcp status --project /path/to/MyGame --json
npx unity-open-mcp run-tool unity_open_mcp_capabilities \
  --project /path/to/MyGame --json --arg include_planned=false

Commands: ping, wait-for-ready, status, run-tool, --help, --version. All accept --json for machine-readable output. See the manual setup guide for the full option reference.

Version pinning

The snippets above pin the server to [email protected] so it stays in lockstep with the bridge and verify packages, which share the same version number. To move to a newer release, bump the version in your client config and your Unity manifest.json together — see Versioning. If you prefer to always run the newest published server, replace the pinned version with @latest.

Documentation

License

MIT