Model Context Protocol (MCP) Server for Unity

Created By
folkward99a year ago
Overview

what is Model Context Protocol (MCP) Server for Unity?

The MCP Server is a Unity package that connects Unity with various AI assistants (Claude, Cursor AI, and Windsurf) through the Model Context Protocol, enabling seamless integration of AI services into Unity projects.

how to use MCP Server?

To use the MCP Server, install it via the Unity Package Manager or manually by cloning the repository. Configure your AI service credentials, start the server, and connect your AI assistant to the provided endpoint.

key features of MCP Server?

  • Connects Unity with multiple AI services: Claude AI, Cursor AI, Windsurf.
  • Provides access to Unity Console, Project Browser, Scene Hierarchy, and Inspector for AI services.
  • Customizable server settings including port number and update frequency.

use cases of MCP Server?

  1. Integrating AI-driven features into Unity games.
  2. Utilizing AI for real-time error logging and asset management.
  3. Enhancing game development workflows with AI assistance.

FAQ from MCP Server?

  • What AI services can I connect to MCP Server?

You can connect Claude AI, Cursor AI, and Windsurf.

  • How do I install the MCP Server?

You can install it using the Unity Package Manager or by manually cloning the repository.

  • Is there documentation available?

Yes, detailed documentation is provided in the Documentation folder of the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
folkward99
Star
0
Language
C#
License
MIT 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
Crevio

2 days ago