Can an AI agent use Composio?

Composio connects AI agents to hundreds of apps such as email and Hacker News.

composio.devMCP gateways

Driven 3 Nov 2026

Evidence sha256 e6f1dcb2JSONMarkdownFeedCite

L3

Does the work

  1. L0
  2. L1
  3. L2
  4. L3
  5. L4
  6. L5

Rank among the 246 products we drove

Core work done
tied #1
100%
10 of 10 core tasks
Holds up
tied #50
78/ 100
Reliability under errors
Steps on its own
tied #35
3/ 5
Find to Leave, no person
Time to get in
tied #83
8minutes
Getting in on its own

Yes. Our agent signed up for Composio on its own in a browser with a code sent to its inbox, got an API key and used its API, MCP server and CLI. It offers agents a way to pay: Stripe Projects.

The record

Level confirmed

Not yet

Level from one drive; a second must agree.

Got in by
Sign-up in a browser8 minutes
Got as far as
Pay: reaches the checkoutA card form for $29 a month

Connects by

MCP, API, CLI, SDK

Agent payments

Stripe Projects; our agent didn't try it

  1. Find

    On its own · 468 doc pages read

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

  2. Get in

    On its own · 8 minutes

    Sign-up in a browser. Sign-up by API: stopped by a bot check.

  3. Use

    On its own · 10 of 10 core tasks

    Did: run code in a remote sandbox and move files in and out of it; create, pause and delete triggers, register webhooks and create MCP server URLs.

  4. PayFirst stop

    Partly · 1 way for agents to pay

    Reaches the checkout. A card form for $29 a month.

  5. Leave

    Partly

    Nothing to cancel. It deletes its data, but the login stays.

  • On its own
  • Partly

To reach L4: Delete its account, so its keys and login stop working.

Checked 18 Nov 2026: MCP server asks for a sign-in, llms.txt and OpenAPI unchanged since the check before.

Find

How an agent connects

MCP, API, OpenAPI, CLI, SDK, agent payments and llms.txt, all found.

  • MCP server

    4 of 12 tested

    Official server. Composio Connect, streamable HTTP, OAuth DCR, 12 tools when driven, the 25 Nov 2025 MCP spec. Sign‑in needed to see its tools.

    connect.composio.dev/mcp

    GitHub lists it as a Copilot connector. GitHub Docs, 16 Nov 2026

    12 tools mapped in our drive

  • API

    49 of 102 tested

    REST v3.1, OpenAPI 3.0.0, 102 operations.

    102 operations mapped in our drive

  • OpenAPI

    Yes

    A machine-readable description of the API.

  • CLI

    12 of 43 tested

    composio CLI 0.6.0 (GitHub release, checksummed).

    43 commands mapped in our drive

  • SDK

    Yes
  • llms.txt

    Yes
  • Agent payments

    Listed, not tested

    Stripe Projects.

    Reached the card form and stopped: Pro, $29 a month. It checks out through Stripe Checkout. No CAPTCHA at checkout.

    Stripe Directory lists it as @composio, with Stripe Projects. Stripe Docs, 10 Nov 2026

  • Docs

    In part

    Covers getting started, auth, error codes and code examples.

    Describes each operation only in part: completeness 58 of 100.

    18 of 20 documented ways to do the core work were tried, and 15 of them worked.

    docs.composio.dev/docs

    468 of 2,471 pages read

Get in

Getting in

Our agent tried 2 of 7 ways in; 1 worked without a person.

The way that worked

Sign-up in a browser8 minutes

  • An inboxNeeded
  • A browserNeeded
  • A personNot needed
  • Agent on a serverAPI, MCP, CLINoSigning up needs a person: it asks for a bot check.
  • Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does all of the core work, then stops: deletes its data, but the login stays.
  • Signed agentKnown to CloudflareYesOur signed agent got through Cloudflare at sign-up.

Every way in

Every way in and what happened
Way inWhat happenedWhy
Sign-up in a browserWorked
Sign-up by APIStopped by a bot check
CLI code loginNot reached
Sign-in for apps (OAuth)Not reached
Company single sign-onNot triedNot part of this drive
Added by an adminNot triedNot part of this drive
A key from a personNot triedNeeds a person's account
  • Bot checkCloudflare let our agent through at sign-up. Our agent signs every request (Web Bot Auth).

Use

What an agent can do with Composio

All 10 core tasks done, and 14 of 19 others.

Core tasks

  • done there
  • offered, not tried
Core tasks of Composio: the result and the surfaces they went through
TaskResultThrough
Connect an app account for a userDoneAPI: done thereMCP: done thereCLI: offered, not tried
Find the right tools for a taskDoneAPI: done thereMCP: offered, not triedCLI: offered, not tried
Run an app action on a connected accountDoneAPI: done thereMCP: done thereCLI: done there
Create an agent session scoped to a user and toolkitsDoneAPI: done there
Set up a trigger on a connected appDoneAPI: done thereCLI: offered, not tried
Run code in a remote sandboxDoneAPI: done thereMCP: done there
Send an authenticated request to an app APIDoneAPI: done thereCLI: done there
Use an Instant tool without connecting an accountDoneAPI: done there
Remove a connected accountDoneAPI: done there
Create an auth config for a toolkitDoneAPI: done thereCLI: offered, not tried

Surface audit: 166 documented operations: 65 run, 7 left out because they spend money or reach real people and 94 not reached in the drive's time. Of the 65 run, 61 passed and 4 didn't. By surface, 49 on the API, 12 in the CLI and 4 on the MCP server.

  • Holds up

    78of 100

    • Reliability92
    • Handles mistakes63

    The mean of the two, 77.5, with a half rounded to the even number.

  • Docs match

    87of 100

    • Docs accuracy100
    • Docs completeness58

    Docs accuracy counts 70%, completeness 30%.

  • Surface tested

    38of 100

    61 of 159 passed: the 166 documented operations less the 7 that spend money or reach real people

  • What it can't do, and why

    • Sign up with the documented agent-only signup The signup service answered HTTP 503 on every try.
    • Create the first organization token without a browser Only the dashboard offers it; no API or CLI route is documented.
    • Use firewall hooks on the free plan The API says firewall hooks require a paid plan.
    • Pay for the Pro plan on its own Only a Stripe card checkout is offered, with no agent payment rail.
    • Receive a trigger or webhook event in this test Our test setup could not send mail or receive webhooks.

14 of 19 other tasks done

  • Register a webhook for trigger eventsDone
  • Pause, change or delete a triggerDone
  • Read tool execution logsDone
  • Browse the toolkit catalogDone
  • Restrict which tools a session may useDone
  • Upload and download files in a session sandboxDone
  • Add a custom toolkit of your own toolsDone
  • Generate a server URL for chosen toolkitsDone
  • Generate typed tool code for a projectDone
  • Create a projectDone
  • Read usage and quotasDone
  • Invite a memberDone
  • Set a member's roleDone
  • Set spend controlsDone
  • Block risky tool calls with a firewall policyPaid plan
  • Listen to trigger events locallyBlocked
  • Brand the connection page with your logoNot tried
  • Restrict API access by IP addressNot tried
  • Configure SSO and SCIMNot tried
  • Encrypt credentials with your own keysNot tried

The plans they need

  • Configure SSO and SCIM
  • Encrypt credentials with your own keys

The drive used the free plan.

Tips for agent builders

From this drive

6 tips
  • If composio login --agent fails, use the login page's 'Continue with email' then 'Email sign-in code' instead of the 'Sign up' link.
  • Use composio login --no-wait, open the printed URL in your signed-in browser, approve, then composio login --poll.
  • Create projects and scoped keys with POST /api/v3.1/org/owner/project/new and api_key_permissions using an x-org-api-key.
  • With project 2FA on, pass user_id together with connected_account_id on proxy and execute calls.
  • For Instant tools, enable Instant in project Settings and omit the account parameter.
  • Proxy endpoints must be relative or on the toolkit base URL's domain; Composio hosts are refused.

Pay

Paying

Ways to pay checked 3 Nov 2026.

  • ResultPartly. Reaches the checkout. A card form for $29 a month.
  • CheckoutReached the card form and stopped: Pro, $29 a month. It checks out through Stripe Checkout. No CAPTCHA at checkout.
  • Ways to pay
    • Stripe Projects (through Stripe's catalog)
  • TrialNo card needed to start.

Leave

Leaving

  • ResultPartly. Nothing to cancel. It deletes its data, but the login stays.
  • Its accountNot all of it: it deletes its data, but the login stays. The agent deleted the organization in the dashboard (typed the name, confirmed). The user key, org token and project key then all answered 401. The sign-in identity the agent's inbox at login.composio.dev may remain, since no user-level delete was offered. The MCP OAuth grant was not revoked by an API, and the AgentMail organization stays (its inbox was deleted).

Daily checks

Checked every day

What our agent finds on the product's own site each day, without an account.

  • Sign-up page,

    No sign-up page on the newest check; 14 of 14 days

  • llms.txt,

    Found on the newest check; 14 of 14 days

  • MCP server,

    Asks for a sign-in on the newest check; 14 of 14 days

  • OpenAPI,

    Found on the newest check; 14 of 14 days

Compare

How Composio compares

In MCP gateways

None of the 3 products we drove in MCP gateways is higher; 2 others share L3. As of 7 Nov 2026.

The products we drove in MCP gateways, in the directory's order, with Composio
ProductLevelFind to leave
ArcadeL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
NangoL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
Composio (this page)L3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.

For the team behind Composio

Agents get stuck at Pay

6 things to fix for agents: 3 small and 3 medium

Not every fix clears a blocker: some make a step that works easier for agents.

Agent blockers: 5 foundAgent surfaces: no issues found

Get your findings, freeWhat a drive covers

We mail a private link to an address at composio.dev.

  1. FindClear
  2. Get inClear
  3. UseClear
  4. PayBlocks agents
  5. LeavePartly

Or claim Composio to see where each issue is, read your safety findings with their fixes and ask for a free drive after a fix.

Want Composio driven every month? See Watch

On our standard

Best or ahead on 9 of 37 criteria, behind on 3. Each against every product we measured on it.

All 37 criteria
How each criterion is graded

Where Composio fits

Wall
Vendors
Standards
Steps
Topics
Rivals

History

Level by drive

One drive so far, on 3 Nov 2026.

Source: our drives of Composio. As of 3 Nov 2026.
  1. 11 Nov 2026Level L4 → L3Re-scored under method v47, drive of 3 Nov 2026

Read more on this step

Pay is where our agent stopped at Composio.

Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.

Found an error? or read how corrections work.

Questions people ask about Composio

Can an AI agent create a Composio account on its own?
Yes, in a browser, without a person. The documented agent signup (composio login --agent) failed with HTTP 503 from agents.composio.dev on every try. The 'Sign up' link raised a visible Cloudflare checkbox. The email one-time-code sign-up from the login form worked in the agent's browser with no challenge and no onboarding questions.
Does Composio have an MCP server, and can an agent connect to it?
Yes. Composio has an official MCP server. The server lists 12 tools, signs an agent in with OAuth and speaks the 25 Nov 2025 MCP spec. A new agent can get in on its own: in the drive of 3 Nov 2026, our agent signed up, verified and got its key without a person. Through the MCP server, our agent tried 3 tasks and did 3.
How does an AI agent get a Composio API key?
In the drive of 3 Nov 2026, our agent got its Composio API key in a browser, without a person. The organization access token can only be created in the dashboard; the agent generated it in its own browser.
Can an AI agent delete its Composio account?
Not all of it: it deletes its data, but the login stays. The agent deleted the organization in the dashboard (typed the name, confirmed). The user key, org token and project key then all answered 401. The sign-in identity the agent's inbox at login.composio.dev may remain, since no user-level delete was offered. The MCP OAuth grant was not revoked by an API, and the AgentMail organization stays (its inbox was deleted).
Can an AI agent pay for Composio?
Partly. Our agent reached a card form for $29 a month. No card needed to start. Composio offers agents a way to pay: Stripe Projects.

Cite this page

The page as a reference, in plain text, APA and BibTeX.

Cite this
Plain
AgentDrives, “Composio: AI agent test drive”, 3 November 2026, https://agentdrives.com/tools/composio. CC BY 4.0.
APA
AgentDrives. (2026, November 3). Composio: AI agent test drive. https://agentdrives.com/tools/composio
BibTeX
@misc{agentdrives_composio_2026,
  author = {{AgentDrives}},
  title = {Composio: AI agent test drive},
  year = {2026},
  month = nov,
  url = {https://agentdrives.com/tools/composio},
  note = {Agent test drive, CC BY 4.0},
}

Something wrong on this page?

We check it against the drive and correct the page, with the date.