head to head · open source
codebase-memory-mcp vs gitdiagram
codebase-memory-mcp has 48,651 GitHub stars, 4,032 forks, 556 open issues and last shipped yesterday. gitdiagram has 18,931 stars, 1,445 forks, 43 open issues and last shipped 4 days ago. codebase-memory-mcp leads on adoption by 157% (48,651 vs 18,931 stars). codebase-memory-mcp is written in C under MIT; gitdiagram is written in TypeScript under MIT. codebase-memory-mcp has attracted 8% as many forks as stars, gitdiagram 8%. codebase-memory-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (developer-tools), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| codebase-memory-mcp | gitdiagram | |
|---|---|---|
| GitHub stars | ★ 49K | ★ 19K |
| License | MIT | MIT |
| Written in | C | TypeScript |
| Last push | 2026-11-14 | 2026-11-11 |
| Forks | ⑂ 4.0K | ⑂ 1.4K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick codebase-memory-mcp if
- You weight community size — 49K stars and counting
- You want the MIT license terms
- Your stack matches C
- You value the larger contributor base for long-term maintenance
pick gitdiagram if
- You want the gitdiagram feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and gitdiagram fits your workflow better
About codebase-memory-mcp
codebase memory mcp: local code intelligence for AI agents via MCP Understand your repository, from source code to the systems around it. codebase memory mcp is an MCP server that connects code, documentation, configuration, and infrastructure in a persistent local knowledge graph. Use it to find an unfamiliar feature, follow a call across services, trace a deployment back to its source, or assess which parts of a project a change could affect. Give your coding agent structural context through Model Context Protocol (MCP), or query the graph directly from the CLI. The MCP server is the core of the project. Its…
read the full codebase-memory-mcp overview →
About gitdiagram
GitDiagram Visualize any codebase: turn any public or private GitHub repository into an interactive architecture diagram, or watch it explained in a one minute narrated video. AI agents can use it too, through the MCP server or the Markdown version of any diagram ( gitdiagram.com/owner/repo.md ). Try GitDiagram → · Or replace hub with diagram in any GitHub repository URL. Sponsored SMS, WhatsApp, and RCS through one API. Try Sent → New: explainer videos GitDiagram can now turn a repository into a narrated video of about a minute. The video starts with what the project is for and what people do with it, then…
read the full gitdiagram overview →
More in Developer Tools
Related comparisons
More Frameworks & Platforms projects
Compare either of these against the rest of the Frameworks & Platforms field.
Frequently asked questions
Is codebase-memory-mcp or gitdiagram more popular?
codebase-memory-mcp has 48,651 GitHub stars and gitdiagram has 18,931. codebase-memory-mcp has the larger community by that measure.
Are codebase-memory-mcp and gitdiagram free?
Both are open source. codebase-memory-mcp is licensed under MIT and gitdiagram under MIT. Neither carries a licence fee.
What is the difference between codebase-memory-mcp and gitdiagram?
codebase-memory-mcp is written in C and gitdiagram in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, codebase-memory-mcp or gitdiagram?
Choose codebase-memory-mcp if you want the larger community (48,651 stars) or its MIT licence terms. Choose gitdiagram if its feature set, stack or MIT licence fits better. Both are self-hostable.