Unity Ollama MCP Server

If you already use Unity Ollama, the unity ollama mcp server is the piece that lets your assistant work with it directly. Automates Unity workflows and manipulates assets using local large language models via Ollama.

What the server does

A Unity MCP (Model Context Protocol) package that enables seamless communication between Unity and local Large Language Models (LLMs) via Ollama. This package extends justinpbarnett/unity-mcp to work with local LLMs, allowing developers to automate workflows, manipulate assets, and control the Unity Editor programmatically without relying on cloud-based LLMs.

The Unity MCP with Ollama Integration provides a bidirectional communication channel between:

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• deepseek-r1 — 14b** - A 14 billion parameter model with strong reasoning capabilities
• gemma3 — 12b** - Google's 12 billion parameter model with good general capabilities
• Host — localhost (default)
• Port — 11434 (default)
• Model — Select either deepseek-r1:14b or gemma3:12b
• Temperature — Adjust as needed (0.0-1.0)
• Green — Connected
• Yellow — Connected but with issues
• Red — Not connected
• Running — Unity is listening for connections
• Stopped — Unity socket server is not active
• Connected — Successfully connected to Ollama server

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

• Unity 2020.3 LTS or newer - Python 3.10 or newer - Ollama installed on your system - The following LLM models pulled in Ollama: - ollama pull deepseek-r1:14b - ollama pull gemma3:12b

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Unity Ollama's toolset — deepseek-r1, gemma3, Host and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ZundamonnoVRChatkaisetu; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Unity Ollama.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.