Category
Tool Integration Platforms
Platforms that give agents authenticated access to apps and APIs through one integration layer.
How to read this category
These platforms sell reach: one authenticated connection layer between your agent and hundreds of apps and APIs, so you do not hand-roll OAuth and pagination for every service the agent touches.
Composio, Arcade, and Toolhouse all live here, with different centers of gravity. Composio leans on managed auth and per-session hosted MCP endpoints. Arcade treats MCP as the product shape itself. Toolhouse routes tool calls across a catalog. All three replace glue code you would otherwise maintain.
The tradeoff is dependence. Your agent inherits the platform uptime, pricing, and permission model, so the permission story deserves as much reading as the integration list.
The verified profiles
Side by side on sourced facts
| Tool | Pricing model | License | Deployment | MCP support | Checked |
|---|---|---|---|---|---|
| Composio | Freemium (hosted paid tiers) | MIT | Managed cloud, Hosted MCP endpoint per session | Hosted MCP per session | 2026-10-07 |
| Arcade | Freemium (hosted paid tiers) | MIT | Arcade Cloud, VPC on Enterprise, Air-gapped on Enterprise, Local MCP server | MCP is the core product | 2026-10-07 |
| Toolhouse | Usage based | Not open source | Managed cloud, Private cloud on Business | See profile | 2026-10-07 |
Every cell traces to the tool profile, which traces to the official repository, package page, and documentation checked on the date shown. Pricing cells name the model, not a price: vendor prices change, so check the profile for the sourced pricing summary and the official pricing link.
What actually decides the choice
- Count integrations second; read the auth model first. Per-user OAuth, managed credentials, and bring-your-own keys fail differently.
- Check what a tool call costs at your volume. Per-call pricing is invisible at demo scale and decisive at production scale.
- Ask what happens when the platform is down or sunsets a connector. An exit path to direct APIs is worth having in writing before you need it.
- MCP shape differs: hosted endpoint per session, native MCP servers, or routing. Match it to your client.
How this archive is ordered, and why it is short
Profiles appear in the order they passed the AgentsUse review gate, not in a tested quality ranking. AgentsUse has not run head-to-head benchmarks for this category, so this page does not claim a winner. The comparison table is the ranking tool: sort by the dimension your job cannot compromise on, then read the full profiles for limitations.
This archive currently lists 3 verified profiles. AgentsUse normally asks for eight published profiles before opening a category archive. This one opens early, on the record, because every listed profile passed the full tool gate and readers comparing real choices need the side-by-side surface now, not a longer unvetted list later. The archive grows as more tools pass review. See how verification works.
Read before you give these tools real work
Guide
Agent Tool Permissions Done Right
Every tool you grant an AI agent is risk you accept. How to think in blast radius, tier permissions, gate irreversible actions, and audit what agents actually did.
2026-09-29
Guide
Agent Security Risks You Must Handle
Agents read untrusted content, run code, and call APIs - a new attack surface. The risks that actually materialize, explained plainly, with working mitigations.
2026-09-29
Back to the tools directory, the category index, or the guides.