head to head · open source

composio vs mex

composio has 30,291 GitHub stars, 4,816 forks, 88 open issues and last shipped today. mex has 1,684 stars, 130 forks, 53 open issues and last shipped yesterday. composio leads on adoption by 1,699% (30,291 vs 1,684 stars). composio is written in TypeScript under MIT; mex is written in TypeScript under MIT. composio has attracted 16% as many forks as stars, mex 8%. composio was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (developer-tools, llm), 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.

composio ★ 30K mex ★ 1.7K category Developer Tools

← all 20902 open source comparisons

Side by side

composio mex
GitHub stars ★ 30K ★ 1.7K
License MIT MIT
Written in TypeScript TypeScript
Last push 2026-09-23 2026-09-22
Forks ⑂ 4.8K ⑂ 130
Self-hosting Yes Yes
Data ownership Your server Your server

pick composio if

  • You weight community size — 30K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full composio profile →

pick mex if

  • You want the mex feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and mex fits your workflow better

full mex profile →

About composio

Composio is an MIT licensed agent toolkit platform, distributed as TypeScript and Python SDKs, that gives AI agents more than 1,000 pre authenticated toolkits, per user sessions, authentication, triggers, and a sandbox for turning intent into action across real applications.

read the full composio overview →

About mex

MEX is an MIT licensed, TypeScript based tool that gives engineering teams and their coding agents a shared project memory kept as readable Markdown inside the repository and shared through ordinary Git commits, pushes, and pulls.

read the full mex overview →

More in Developer Tools

ECC ★ 266K react ★ 251K OpenCode ★ 209K vscode ★ 193K Langflow ★ 155K Supabase ★ 111K

Related comparisons

openclaw vs langflow ecc vs react ecc vs langflow react vs langflow ecc vs supabase react vs supabase n8n vs langflow ecc vs puppeteer openclaw vs openhands openclaw vs paperclip hermes-agent vs pi hermes-agent vs openhands hermes-agent vs paperclip opencode vs pi opencode vs openhands opencode vs paperclip react vs vscode react vs neovim react vs zed opencode vs neovim opencode vs zed vscode vs neovim vscode vs zed react vs kilocode

More Frameworks & Platforms projects

Compare either of these against the rest of the Frameworks & Platforms field.

composio vs ECC composio vs react composio vs Langflow composio vs Supabase composio vs puppeteer composio vs archify composio vs PocketBase composio vs i-have-adhd composio vs codebase-memory-mcp composio vs ToolJet composio vs AppSmith composio vs it-tools

Frequently asked questions

Is composio or mex more popular?

composio has 30,291 GitHub stars and mex has 1,684. composio has the larger community by that measure.

Are composio and mex free?

Both are open source. composio is licensed under MIT and mex under MIT. Neither carries a licence fee.

What is the difference between composio and mex?

composio is written in TypeScript and mex 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, composio or mex?

Choose composio if you want the larger community (30,291 stars) or its MIT licence terms. Choose mex if its feature set, stack or MIT licence fits better. Both are self-hostable.