AgentSidekick

Composio vs mcp-use

Composio is a saaS product from Composio (MIT licence, 31k GitHub stars, last push 2026-11-21); mcp-use is a library from Manufact (MIT licence, 11k GitHub stars, last push 2026-11-21). They share 1 of 7 capabilities and integrations identified for either (overlap 0.60); only Composio covers Tool Use & Function Calling, Unified APIs; only mcp-use covers MCP Gateways & Proxies, MCP Testing & Debugging, MCP Clients and 1 more. Figures as of 2026-11-21. DER

Composio profilemcp-use profileOpen in the compare tool

Side-by-side facts

7 of 16 rows differ (marked). Unknown means no source we track states it.

FieldComposiomcp-use
Type · differsSaaS product · hosted CURLibrary · library CUR
Publisher · differsComposio CURManufact CUR
LicenceMIT CURMIT CUR
Open source · differsNo CURYes CUR
Pricing model · differsfreemium CURopen-source CUR
HostingUnknownUnknown
Latest versionUnknownUnknown
Languagespython, typescript CURpython, typescript CUR
GitHub stars · differs31k (31,219) SRC11k (11,001) SRC
Forks · differs5.0k SRC1.6k SRC
Last push2026-11-21 SRC2026-11-21 SRC
ArchivedNo SRCNo SRC
First published · differs2024-02-23 SRC2025-03-28 SRC
Versions recordedUnknownUnknown
VerificationChecked by AgentSidekick against official sources CURChecked by AgentSidekick against official sources CUR
Last verified2026-11-21 CUR2026-11-21 CUR

Shared and unique capabilitiesDER

Capabilities are assigned by keyword rules from each description unless a researcher set them; integrations are services named in the description or package metadata.

Platform compatibility

Status per platform from the evidence we hold. No pairing has been tested by AgentSidekick.

No compatibility evidence

For all 47 platforms on record the status is Unknown or Platform discontinued for both: neither product type implements a standard we can check (MCP, Agent Skills, Claude plugins) and neither publisher names a platform.

Maintenance

Repository activity read from the GitHub API. Activity is not quality.

MeasureComposiomcp-use
StatusActive DERActive DER
Days since last push0 DER0 DER
Open issues84 SRC41 SRC
Latest GitHub release@composio/cli@0.6.3 · 2026-11-20 SRCmcp-use@2.12.9 · 2026-11-19 SRC
Newest registry versionUnknownUnknown

Evaluation dimensions

Separate signals with their evidence; there is no overall score. Hover or focus a status for its evidence.

DimensionComposiomcp-use
Source authorityChecked against official sourcesChecked against official sources
Publisher verificationOrganisation accountOrganisation account
Maintenance activityActiveActive
Licence clarityMITMIT
Installation clarityLinkedLinked
DocumentationDocs linkedDocs linked
Compatibility evidenceUnknownUnknown
Security reviewNot reviewedNot reviewed

Which fits which requirementDER

Derived from the differences above, one rule per line. Nothing here says either product is better; check the requirement against your own needs.

Choose Composio if…

  • you need Tool Use & Function Calling, Unified APIs (classified for Composio only)
  • you weigh adoption: 31k vs 11k GitHub stars (popularity, not quality)

Choose mcp-use if…

  • you need MCP Gateways & Proxies, MCP Testing & Debugging, MCP Clients and 1 more (classified for mcp-use only)

Sources

Report incorrect information

Page data last updated .