Unity MCP Server

Created By
nikolausma year ago
MCP (Model Context Protocol) server for Unity Engine integration with Claude
Overview

what is Unity MCP Server?

Unity MCP Server is a Model Context Protocol (MCP) server designed for integrating Unity Engine with Claude, enabling seamless project management and script creation within Unity.

how to use Unity MCP Server?

To use Unity MCP Server, install the necessary dependencies, configure it in Claude Desktop, and utilize the provided commands to manage Unity projects.

key features of Unity MCP Server?

  • unity_list_projects: Lists all Unity projects in a directory.
  • unity_create_project: Creates a new Unity project.
  • unity_open_project: Opens an existing Unity project.
  • unity_list_installed_versions: Displays all installed Unity versions.
  • unity_create_script: Creates C# scripts in Unity projects.
  • unity_build_project: Builds Unity projects.

use cases of Unity MCP Server?

  1. Managing multiple Unity projects efficiently.
  2. Automating the creation and opening of Unity projects.
  3. Streamlining the script creation process for Unity developers.
  4. Facilitating project builds directly from the command line.

FAQ from Unity MCP Server?

  • What are the prerequisites for using Unity MCP Server?

You need to have Unity Hub installed and at least one version of Unity.

  • Is Unity MCP Server compatible with all operating systems?

Currently, it is designed for macOS, and paths may need to be adjusted for other platforms.

  • What programming language is used in Unity MCP Server?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nikolausm
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago