Unity MCP Server

Created By
MizoTakea year ago
Overview

what is Unity MCP Server?

Unity MCP Server is a Model Context Protocol (MCP) server designed for integration with the Unity game engine, enabling AI assistants to interact with Unity projects and providing tools for building, testing, profiling, and managing Unity applications.

how to use Unity MCP Server?

To use Unity MCP Server, clone the repository, install dependencies, and start the server in production or development mode. You can then execute various commands to manage your Unity projects.

key features of Unity MCP Server?

  • Execute Unity command-line operations
  • Build Unity projects for multiple platforms
  • Run Unity tests (EditMode/PlayMode)
  • Retrieve project information including Unity version and details
  • Compile Unity scripts and manage assets
  • Capture performance data using Unity Profiler

use cases of Unity MCP Server?

  1. Automating Unity project builds for different platforms.
  2. Running automated tests for Unity applications.
  3. Analyzing performance metrics to optimize game performance.
  4. Managing Unity assets and project settings programmatically.

FAQ from Unity MCP Server?

  • What platforms does Unity MCP Server support?

It supports multiple platforms including StandaloneWindows64, StandaloneOSX, StandaloneLinux64, Android, iOS, and WebGL.

  • Is there a specific version of Unity required?

Yes, Unity MCP Server requires Unity version 2019.4 or higher.

  • Can I run this server in a WSL environment?

Yes, the server fully supports WSL (Windows Subsystem for Linux) and can automatically detect Unity installations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MizoTake
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
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