Good shape overall. A few tweaks would push it into the top tier.
Godot-MCP — Model Context Protocol (MCP) integration for the Godot Engine. AI tools for the Godot Editor in C#, with cloud connection to ai-game.dev. Apache-2.0.
Documentation
82
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
62
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (cli/package-lock.json). Installs are reproducible.
Test files detected (Godot-MCP.Tests/AgentSessionViewTests.cs).
CI is configured (.github/workflows/ci.yml).
Project health
100
Dependency manifest found (Godot-MCP.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 12Forks
- 16Releaseslatest 4d ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 131Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 1Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- addons
- cliGood: Lockfile present (cli/package-lock.json). Installs are reproducible.
- docs
- Godot-MCP.TestsGood: Test files detected (Godot-MCP.Tests/AgentSessionViewTests.cs).
- Godot-Tests
- scripts
- .gitattributes
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- Godot-MCP.csprojGood: Dependency manifest found (Godot-MCP.csproj).
- Godot-MCP.sln
- LICENSEGood: Licensed under Apache-2.0.
- README.mdGood: 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.Good: README documents how to run the project.