Popular and well-maintained. A little polish away from elite status.

Unity MCP acts as a bridge between AI assistants and your Unity Editor. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.

Documentation

83

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

76

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Tests18pt80

Test files detected (MCPForUnity/Editor/Resources/Tests).

Reproducibility6pt80

Lockfile present (Server/uv.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/e2e-bridge.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (MCPForUnity/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files23 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/e2e-bridge.yml).
    Good: Issue or PR templates present.
  • CustomTools
  • docs
  • MCPForUnity
    Good: Test files detected (MCPForUnity/Editor/Resources/Tests).
    Good: Dependency manifest found (MCPForUnity/package.json).
  • scripts
  • Server
    Good: Lockfile present (Server/uv.lock). Installs are reproducible.
    Good: Environment pinned via Server/Dockerfile.
  • TestProjects
  • tools
  • unity-mcp-skill
  • website
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .mcpbignore
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
  • LICENSE
    Good: Licensed under MIT.
  • manifest.json
  • mcp_source.py
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.