AgentSidekick

mcp-use vs Toolhouse

mcp-use is a library from Manufact (MIT licence, 11k GitHub stars, last push 2026-11-21); Toolhouse is a saaS product from Toolhouse (licence unknown, no public repository metrics). They share 1 of 5 capabilities and integrations identified for either (overlap 0.60); only mcp-use covers MCP Gateways & Proxies, MCP Testing & Debugging, MCP Clients and 1 more. Figures as of 2026-11-21. DER

mcp-use profileToolhouse profileOpen in the compare tool

Side-by-side facts

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

Fieldmcp-useToolhouse
Type · differsLibrary · library CURSaaS product · hosted CUR
Publisher · differsManufact CURToolhouse CUR
Licence · differsMIT CURUnknown
Open source · differsYes CURNo CUR
Pricing model · differsopen-source CURfreemium CUR
HostingUnknownUnknown
Latest versionUnknownUnknown
Languages · differspython, typescript CURUnknown
GitHub stars · differs11k (11,001) SRCUnknown
Forks · differs1.6k SRCUnknown
Last push · differs2026-11-21 SRCUnknown
Archived · differsNo SRCUnknown
First published · differs2025-03-28 SRCUnknown
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.

Measuremcp-useToolhouse
StatusActive DERUnknown UNK
Days since last push0 DERUnknown
Open issues41 SRCUnknown
Latest GitHub releasemcp-use@2.12.9 · 2026-11-19 SRCUnknown
Newest registry versionUnknownUnknown

Evaluation dimensions

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

Dimensionmcp-useToolhouse
Source authorityChecked against official sourcesChecked against official sources
Publisher verificationOrganisation accountOrganisation account
Maintenance activity · differsActiveUnknown
Licence clarity · differsMITUnknown
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 mcp-use if…

  • you need an OSI-style open-source licence (mcp-use: MIT; Toolhouse: none on record)
  • you need MCP Gateways & Proxies, MCP Testing & Debugging, MCP Clients and 1 more (classified for mcp-use only)
  • you require a repository pushed to in the last 90 days (mcp-use: 2026-11-21; Toolhouse: no repository metrics)

Choose Toolhouse if…

No measurable difference favours Toolhouse on licence, hosting, pricing model, coverage, maintenance, adoption or install metadata.

Sources

Report incorrect information

Page data last updated .