Unity MCP 統合フレームワーク

Created By
isuzu-shiranuia year ago
Unity Editor integration with Model Context Protocol (MCP) enabling AI assistants like Claude to interact with Unity projects. Features a TypeScript MCP server and C# Unity plugin with extensible command handler architecture, TCP/IP communication, and dynamic plugin discovery.
Overview

What is Unity MCP?

Unity MCP is an integration framework that allows AI assistants, such as Claude, to interact with Unity projects through the Model Context Protocol (MCP). It features a TypeScript MCP server and a C# Unity plugin with an extensible command handler architecture.

How to use Unity MCP?

To use Unity MCP, install it via the Unity Package Manager, configure the connection settings, and start the server to enable communication between Unity and external AI services.

Key features of Unity MCP?

  • Extensible plugin architecture for custom command handlers
  • Seamless integration with AI models using MCP
  • Support for TypeScript and C# components
  • Editor tool functionality with customizable settings
  • Automatic discovery and registration of command handlers
  • TCP/IP communication between Unity and external AI services

Use cases of Unity MCP?

  1. Enabling AI-driven interactions within Unity projects.
  2. Creating custom command handlers for specific functionalities.
  3. Facilitating communication between Unity and AI models for enhanced game development.

FAQ from Unity MCP?

  • What are the system requirements for Unity MCP?

Unity 2023.2.19f1 or higher, .NET/C# 9.0, and Node.js 18.0.0 or higher are required.

  • Is Unity MCP free to use?

Yes! Unity MCP is open-source and available under the MIT license.

  • Can I create custom command handlers?

Yes! Unity MCP allows you to create and register custom command handlers easily.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
isuzu-shiranui
Star
49
Language
C#
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago