Updated
Agent building blocks

Tool Integrations for Agents

Let your agent act in the apps your users already use — Gmail, Slack, GitHub, CRMs — without building each OAuth flow and API client yourself.

For your framework or language:Next.js
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Trends

Nango gained the most ground in package downloads: +57% against the median npm package over a year.

Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.

ToolDownloadsStars
Nango473.6k/wk+57% vs npm★ 12.8k
Arcade132.5k/wk★ 1k
Smithery7.5k/wk−97% vs npm—
Composio—★ 30.5k

The real choice

Agent-first tool layer or general integration platform. Agent-first services package each app as ready tool definitions for models, with per-user auth handled. General integration platforms connect thousands of APIs and also run workflows and triggers, with agent tools as one way in. MCP registries list existing MCP servers and connect your agent to them through one gateway. Running the code an agent writes is a separate decision: see Code Sandboxes for Agents.

What makers chose35 live products, each with a source. Not market share.

Pick by situation

Tap the ones that are you — the tools that fit light up below.
  • Your agent acts on each user's own accounts across several appsComposioArcade
  • You need integrations for both the agent and ordinary background automationsPipedream
  • The app you need already has an MCP server and you'd rather not run or authorize it yourselfSmithery

Compare the tools

Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.

ToolBest for
Agent-first tool layer2
Composioapi · open sourceConnecting an agent to many apps at once, with tool schemas and per-user OAuth ready for the model.26★ 30.5k

Use it whenYour agent acts on each user's own accounts across several apps.

Trade-offAnother service in every tool call's path, billed by tool calls.

Used by Accordio AI, Construct Computer, Crossnode, Entendo, Extra Thursday and 21 more.

Gmail, Calendar, Drive, Stripe and the project tools all speak to our agent through Composio. One SDK instead of nine OAuth apps.
Accordio AI, the makerSep 2026 ↗
Arcadeplatform · self-hostableAgents that act on behalf of each signed-in user, with per-user authorization and prebuilt tools, plus a framework for writing your own tools as MCP servers.1+6 open source132.5k/wk

Use it whenYou need your own custom tools behind the same per-user auth as the prebuilt ones, or a private deployment later.

Trade-offBilled by auth events and tool calls past the free tier; self-hosting is an Enterprise option.

Used by Tradestack · in 6 open-source projects.

Integration platform1
PipedreamplatformManaged auth and prebuilt actions across thousands of APIs, plus event triggers and workflows beyond agent use.8

Use it whenYou need integrations for both your agent and ordinary background automations.

Trade-offClosed source and hosted only; production use moves to paid plans.

Used by Latitude, Spine, viktor.com, Vybe, WorkClaw and 3 more.

Agents need tools. Pipedream makes it easy to connect APIs with thousands of integrations and get workflows running in minutes.
Latitude, the makerSep 2026 ↗
MCP registry1
SmitheryplatformFinding existing MCP servers and connecting an agent to them through one gateway that manages OAuth and sessions.No evidence yet7.5k/wk−97% vs npm

Use it whenThe app you need already has an MCP server and you'd rather not run or authorize it yourself.

Trade-offQuality varies between community-published servers; Smithery proxies to them rather than hosting them.

No maker's product we track shows it for this yet.

Before you choose

How to approach it

Build your first one or two integrations by hand to learn what your agent needs; bring in a platform when you need the fifth app or your users' own accounts. Give the agent the fewest tools that do the job — long tool lists lower accuracy. Scope each user's OAuth permissions narrowly, since the agent acts with them.

Common mistakes
  • Giving the agent write access to a user's accounts on day one, when read-only scopes would cover what it actually does.
  • Handing the model dozens of tools "just in case", which makes it pick the wrong one more often.

Other options

Real choices most makers here won't need to weigh.

Decided alongside

What the 35 makers' products here chose for their other decisions.