Composio pricing: plans, metered usage and costs for a small team

Composio has three plans as of October 2026: Hobby is free and capped at 100,000 tool calls a month, Pro is $29 a month with a $29 usage credit and pay-as-you-go rates after the free amounts, and Enterprise is a custom contract. Most of what you pay on Pro depends on tool calls and trigger events, plus a few add-ons that apply only when a call uses them.

Everything below comes from Composio's pricing page and documentation, checked on 30 October 2026. We make Toolstile, an MCP gateway that sometimes comes up in the same evaluations, so the last section says where it fits and where it doesn't. Composio's rates change; check the pricing page before you budget.

Composio plans at a glance

The Pro credit "expires at the end of each billing month and does not roll over," according to the pricing page. All plans include the 1,500+ toolkit catalog, OAuth management, triggers, sessions, custom tools and MCP, and unlimited connected accounts when you use your own OAuth app or API keys. Pro adds a read-only dashboard role, a self-serve DPA and access to the paid add-ons. Enterprise adds annual invoicing, committed-volume discounts, an MSA, DPA and BAA, and dedicated support with an SLA.

Composio changed its pricing for new accounts in August 2026. The page says "New pricing applies to signups on or after August 15, 2026. Existing customers stay on their current plan through December 31, 2026." If you signed up earlier, your bill may not match this page until January.

What Composio meters

Tool calls

A tool call is one tool execution. The pricing page says "Each tool execution counts once. Meta tools such as tool search are free," so the discovery steps an agent takes before acting don't use your allowance. The 100,000 free calls and the $0.0003 rate apply to calls made with your own app, an API key or MCP.

Calls that go through a Composio-managed app are counted differently. A managed app is a shared OAuth application Composio runs so you can skip creating your own. Only 20,000 of your 100,000 free calls can go through managed apps, and after that they cost $0.0005 each, which the FAQ describes as "an extra $0.0002 per tool call on top of the base rate." Composio describes managed apps as "not recommended for scaling."

Trigger events

Triggers deliver events from connected apps, such as a new email, to your webhook. They're "billed per event delivered to your webhook, not per poll." You get 50,000 a month free, then $0.003 each on Pro. Managed apps get 10,000 of those, then $0.005 each.

Connected accounts

A connected account is one authorized login, such as one person's Gmail. With your own app they're unlimited and free. With managed apps the first 1,000 are free, and on paid plans each additional one costs $0.10 once.

Usage-based add-ons

These are charged on top of the tool-call rate, only for calls that use them. The free amounts below are listed in the Hobby column of Composio's table, and the page says allowances vary by plan; it doesn't say whether Pro keeps them. Rates on Pro:

Two other meters are separate. Sandbox LLM tokens, the model calls Composio runs for you in its sandbox, have 1M free a month and then cost $3.75 per million. Instant Tools run on Composio's provider accounts, so you don't need your own API key for that provider. They bill the provider's published rate from your Composio balance "with 0% markup," and regular tool-call charges still apply.

Rate limits

Rate limits are separate from the monthly allowance. The rate limits reference says Composio enforces them "per organization over a fixed one-minute window," and every authenticated endpoint draws from the same budget, including tool execution, connected accounts and triggers. A connected app's own API quota can still reject a call even when your Composio allowance has room.

How Composio costs scale for a small team

Two details drive the bill for a team. Hobby allows 3 team members, so a team of four or more needs Pro. And on Pro the $29 fee comes back as usage credit, so the monthly total is $29 or your metered usage, whichever is higher, as long as the credit covers the meters you use.

These examples assume your own OAuth apps, tools run inside sessions (Composio's recommended path, so no direct-execution add-on), and no compliance add-ons.

Five people, light use. 60,000 tool calls and 5,000 trigger events a month, each person on their own accounts. Everything fits in the free amounts, but five members rules out Hobby. Cost: $29.

Five people, heavier use. 300,000 tool calls and 20,000 trigger events. The 200,000 calls beyond the free 100,000 cost 200,000 × $0.0003 = $60. Triggers stay free. Metered usage is $60, so the bill is $60.

The same team sharing accounts. Say 100,000 of those 300,000 calls go through one connected account that the whole team shares, such as a team GitHub login. The shared-connection add-on adds 100,000 × $0.0003 = $30, so the bill becomes $90. If Pro also keeps the 1,000 free shared calls listed for Hobby, which the page doesn't confirm, the add-on is 99,000 × $0.0003 = $29.70 and the bill about $89.70.

The same team on managed apps. If the 300,000 calls and 20,000 trigger events all went through Composio-managed apps instead, only 20,000 calls and 10,000 trigger events would be free. The other 280,000 calls would cost $0.0005 each, or $140, and the other 10,000 trigger events $0.005 each, or $50. Metered usage is $190, so the bill is $190. That's why Composio suggests your own OAuth app once usage grows.

At these volumes, triggers matter more per event than tool calls: 100,000 trigger events in a month, 50,000 of them beyond the free allowance, would add 50,000 × $0.003 = $150. Set per-meter spend caps on Pro if you need a ceiling, since Pro keeps running past the free amounts rather than pausing like Hobby.

What Composio pricing doesn't cover

Composio's plans cover Composio. The connected apps keep their own subscriptions, API charges and quotas, and your AI client or model provider bills separately. Composio's MCP gateway for enterprise teams, with org, team and user policies, is sold through a demo rather than a listed price. If that's what you're buying, ask which plan it comes with.

If Composio's pricing doesn't fit

Composio prices a platform: a catalog of maintained toolkits, managed OAuth, triggers and an SDK for building agents into your own product. If you use those, the per-call rates are low and the free allowance is large.

If what you need is narrower, the per-call model can be the wrong shape. Some teams already use remote MCP servers that their providers run, such as GitHub's or Linear's, from Claude Code, Codex or Cursor, and only need to share them and decide which tools each AI app may call. For that job you don't need a connector catalog or triggers.

Toolstile is built for that case. It's priced per workspace with a monthly operation allowance and no per-seat fee: Free includes 5,000 operations, Starter is $29 for 50,000, Team is $99 for 250,000 and Scale is $299 for 1,000,000. An operation is a tool call, resource read or prompt request, and listing tools doesn't count. There are no overages; forwarding stops at the allowance. The units differ from Composio's, so compare them against your own workload rather than side by side. The usage and billing guide has the exact meter rules.

Toolstile doesn't replace Composio's toolkit catalog, triggers or end-user authorization SDK, and it only connects to public HTTPS MCP servers. The Composio alternatives comparison covers when to stay with Composio, when Toolstile fits, and other options such as Arcade. For the general question of what a gateway does and when you don't need one, read What is an MCP gateway?. For how sign-in works when an agent connects to a remote server, see the MCP authentication guide.