head to head · open source
codebase-memory-mcp vs composio
codebase-memory-mcp has 48,309 GitHub stars, 3,992 forks, 561 open issues and last shipped 2 days ago. composio has 30,972 stars, 4,933 forks, 88 open issues and last shipped yesterday. codebase-memory-mcp leads on adoption by 56% (48,309 vs 30,972 stars). codebase-memory-mcp is written in C under MIT; composio is written in TypeScript under MIT. codebase-memory-mcp has attracted 8% as many forks as stars, composio 16%. composio 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 | composio | |
|---|---|---|
| GitHub stars | ★ 48K | ★ 31K |
| License | MIT | MIT |
| Written in | C | TypeScript |
| Last push | 2026-11-07 | 2026-11-08 |
| Forks | ⑂ 4.0K | ⑂ 4.9K |
| 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 composio if
- You want the composio feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and composio 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 composio
composio.dev • Documentation • Quickstart • Changelog Composio Composio gives your AI agents 1000+ pre authenticated toolkits, per user sessions, authentication, triggers, and a sandbox, so you can ship agents that turn intent into action. This is the Composio SDK monorepo. It contains: @composio/core : TypeScript SDK composio : Python SDK composio CLI : search, execute, and script tools from your shell Provider adapters for OpenAI Agents, Claude Agent SDK, Vercel AI SDK, LangChain, and more Quickstart Create a session for a user, hand its tools to your agent, and let the agent take action across 1000+ apps…
read the full composio 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 composio more popular?
codebase-memory-mcp has 48,309 GitHub stars and composio has 30,972. codebase-memory-mcp has the larger community by that measure.
Are codebase-memory-mcp and composio free?
Both are open source. codebase-memory-mcp is licensed under MIT and composio under MIT. Neither carries a licence fee.
What is the difference between codebase-memory-mcp and composio?
codebase-memory-mcp is written in C and composio 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 composio?
Choose codebase-memory-mcp if you want the larger community (48,309 stars) or its MIT licence terms. Choose composio if its feature set, stack or MIT licence fits better. Both are self-hostable.