coplaydev/unity-mcp
Grade a repo

83

/ 100

GradeB

Well engineered. The main gap is linting.

Top 20% of 5,156 graded repos

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.

Documentation92
Engineering76
Health100
C#13,143MIT5d ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

92

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

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/compile-check.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 health signals

Activity, community, and responsiveness at scan time

Activity

  • 50 / 259
    Commits (30d / 90d)
  • 1,392
    Forks
  • 66
    Releaseslatest 9mo ago

Community

  • 87% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 13,143
    Watchers

Responsiveness

  • 5h
    Median issue response
  • <1h
    Median PR merge time
  • 78
    Open issues
Repository files24 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/compile-check.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
  • .gitattributes
  • .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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/coplaydev/unity-mcp)](https://www.repo-grade.com/report/coplaydev/unity-mcp)

More graded C# repos