What is the purpose of Unity MCP Template?
It is a minimal example that shows how an MCP server can communicate with Unity. You can use it as a base to create your own Unity‑MCP tools.
@dunward
Basic information
Simple template project for controlling Unity via MCP
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"unity-mcp": {
"command": "node",
"args": [
"F:/unity-mcp-template/unity-mcp-server/dist/index.js"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Unity MCP Template is a simple example project that demonstrates interaction between a TypeScript‑based MCP server and Unity. It serves as a starting point for developers to build and configure their own tools that bridge an MCP client (e.g., Claude Desktop) with the Unity editor.
Clone the repository, navigate to unity-mcp-server, run npm install and npm run build. Then add the built server to Claude Desktop via its Developer‑Edit Config, pointing to the generated index.js file. Open the Unity project and manage the MCP through the “UnityMCP‑ShowWindow” menu item at the top.
It is a minimal example that shows how an MCP server can communicate with Unity. You can use it as a base to create your own Unity‑MCP tools.
Open Claude Desktop Settings, go to Developer‑Edit Config, and add a JSON entry with the command `node` and the full path to the compiled `index.js` file.
In Unity, reference the existing `CreateObjectTools` class. In TypeScript, reference the `createObject` function. Both sides must use the same input data structure.
Node.js and npm are required to build and run the TypeScript MCP server. Unity (any version, no NewtonsoftJSON needed) is needed for the example project.
The current implementation uses TCP (with roles reversed due to a TypeScript SDK issue). The TODO list indicates a planned change to a standard client‑server TCP structure.
MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

Give your coding agent access to production. Search your logs in plain language, look up issues and investigate errors from Claude Code, Cursor, Codex or ChatGPT. Requires a Sazabi account; sign in with OAuth.
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.
Comments