head to head · open source
codebase-memory-mcp vs Hexabot
codebase-memory-mcp has 48,082 GitHub stars, 3,959 forks, 552 open issues and last shipped 2 days ago. Hexabot has 1,151 stars, 235 forks, 26 open issues and last shipped 2 days ago. codebase-memory-mcp leads on adoption by 4,077% (48,082 vs 1,151 stars). codebase-memory-mcp is written in C under MIT; Hexabot is written in TypeScript under a custom or non-standard licence. codebase-memory-mcp has attracted 8% as many forks as stars, Hexabot 20%. codebase-memory-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee.
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 | Hexabot | |
|---|---|---|
| GitHub stars | ★ 48K | ★ 1.2K |
| License | MIT | Custom / other |
| Written in | C | TypeScript |
| Last push | 2026-11-03 | 2026-11-03 |
| Forks | ⑂ 4.0K | ⑂ 235 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick codebase-memory-mcp if
- You weight community size — 48K stars and counting
- You want the MIT license terms
- Your stack matches C
- You value the larger contributor base for long-term maintenance
pick Hexabot if
- You want the Hexabot feature set and don't need the biggest community
- You prefer the Custom / other license terms
- Your stack matches TypeScript
- You evaluated both and Hexabot 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 Hexabot
Automate the Boring, Keep the Magic Build and run agentic workflows across channels with YAML, tools, MCP, memory and RAG. Website · Documentation · Extensions · Discord Hexabot v3 is an automation platform with first class AI capabilities, combining workflows, actions, and conversational channels in one runtime. Quick Start Prerequisites Node.js ^24.17.0 One package manager ( npm , pnpm , yarn , or bun ) Docker (optional, for Docker based services) This Quick Start targets projects generated with the CLI. If you are contributing to the Hexabot monorepo itself, use PNPM (see CONTRIBUTING.md). 1) Install the CLI…
read the full Hexabot 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 Hexabot more popular?
codebase-memory-mcp has 48,082 GitHub stars and Hexabot has 1,151. codebase-memory-mcp has the larger community by that measure.
Are codebase-memory-mcp and Hexabot free?
Both are open source. codebase-memory-mcp is licensed under MIT, and Hexabot has no licence declared in this registry. Both are free to self-host.
What is the difference between codebase-memory-mcp and Hexabot?
codebase-memory-mcp is written in C and Hexabot 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 Hexabot?
Choose codebase-memory-mcp if you want the larger community (48,082 stars) or its MIT licence terms. Choose Hexabot if its feature set, stack or Custom / other licence fits better. Both are self-hostable.