Unity MCP Integration

Created By
Shahzada year ago
Access real-time information about your Unity project Read/Write Functionality to Unity Project Files Understand your scene hierarchy and game objects Execute C# code directly in the Unity Editor Monitor logs and errors Control the Editor's play mode
Overview

What is Unity MCP Integration?

Unity MCP Integration is a tool that connects the Model Context Protocol (MCP) with the Unity Editor, allowing real-time interaction and information access for AI assistants within Unity projects.

How to use Unity MCP Integration?

To use Unity MCP Integration, install the Unity package via the Package Manager or import it as a custom package, then set up the MCP server to enable communication between the Unity Editor and the MCP protocol.

Key features of Unity MCP Integration?

  • Access real-time information about Unity projects
  • Understand scene hierarchy and game objects
  • Execute C# code directly in the Unity Editor
  • Monitor logs and errors
  • Control the Editor's play mode

Use cases of Unity MCP Integration?

  1. Enhancing AI assistants to interact with Unity projects.
  2. Debugging and monitoring Unity projects in real-time.
  3. Executing commands and retrieving information about game objects and scenes.

FAQ from Unity MCP Integration?

  • What is MCP?
    MCP stands for Model Context Protocol, which connects AI models to tools and context sources.

  • What are the prerequisites for using this integration?
    You need Unity 2021.3 or later and Node.js 18+ to run the MCP server.

  • How can I contribute to this project?
    You can fork the repository, create a feature branch, make changes, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Shahzad
Star
-
Language
-
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)

20 hours ago
Gpt Scrambler

2 days ago