codebase-memory-mcp vs MCP for Unity
Side-by-side comparison of two AI agent tools
Short answer
- codebase-memory-mcp is growing faster: +1,470 GitHub stars in the last 30 days vs +210 for MCP for Unity.
- Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick MCP for Unity for: connects AI assistants to the Unity Editor to manage assets, scenes, C scripts, tests, and workflows.
From GitHub data refreshed daily.
c
codebase-memory-mcpopen-source
MCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP
M
MCP for Unityopen-source
Connects AI assistants to the Unity Editor to manage assets, scenes, C# scripts, tests, and workflows
Metrics
| codebase-memory-mcp | MCP for Unity | |
|---|---|---|
| Stars | 45.6k | 14.6k |
| Star velocity /mo | 1.5k | 210 |
| Commits (90d) | 2.1k | 238 |
| Releases (6m) | 10 | 10 |
| Overall score | 0.9054235547012244 | 0.7484236592572197 |
FAQ
- Which is more popular, codebase-memory-mcp or MCP for Unity?
- codebase-memory-mcp has more GitHub stars (45,600 vs 14,632).
- Which is more actively developed, codebase-memory-mcp or MCP for Unity?
- codebase-memory-mcp had more commits in the last 90 days (2,148 vs 238).
- Should I use codebase-memory-mcp or MCP for Unity?
- Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.