Accurate Unity API docs (2022/2023/6) for AI agents. Prevents hallucinated signatures.
Connect Unity API Documentation to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Accurate Unity API docs (2022/2023/6) for AI agents. Prevents hallucinated signatures. The unity api documentation mcp server is what makes that connection.
Supports Unity 6 (one database per minor stream), Unity 2023, and Unity 2022 LTS. Works with Claude Code, Cursor, Windsurf, or any MCP-compatible AI tool. No Unity installation required. See the supported versions. New Unity releases are detected and built automatically every week.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Covers — all UnityEngine/UnityEditor modules, Input System, Addressables, uGUI/TextMeshPro, AI Navigation, Netcodesearch_unity_api — Find APIs by keywordget_method_signature — Exact signatures with all overloadsget_namespace — Resolve using directivesget_class_reference — Full class reference cardget_deprecation_warnings — Check if an API is obsoleteWhen — Toolunity-api-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: UNITY_VERSION, UNITY_PROJECT_PATH, UNITY_INSTALL_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory 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 API Documentation's toolset — Covers, search_unity_api, get_method_signature and 4 more — is a fair guide to whether it matches your workflow. It is maintained by Codeturion; 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.
| Tool | What it does |
|---|---|
| Covers | all UnityEngine/UnityEditor modules, Input System, Addressables, uGUI/TextMeshPro, AI Navigation, Netcode |
| search_unity_api | Find APIs by keyword |
| get_method_signature | Exact signatures with all overloads |
| get_namespace | Resolve using directives |
| get_class_reference | Full class reference card |
| get_deprecation_warnings | Check if an API is obsolete |
| When | Tool |
{
"mcpServers": {
"unity-api": {
"command": "uvx",
"args": ["unity-api-mcp"],
"env": {
"UNITY_VERSION": "6000.3"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UNITY_VERSION | Configuration value read at startup. | Optional |
| UNITY_PROJECT_PATH | Filesystem location the server is allowed to use. | Optional |
| UNITY_INSTALL_PATH | Filesystem location the server is allowed to use. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.