# Composio (API + MCP) vs One

> Composio scores 75.1 (BB) to One's 66.6 (B) for app automation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/composio-rube-vs-one
- Markdown: https://www.anchorterminal.com/compare/composio-rube-vs-one.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/composio-rube-vs-one.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/composio-rube-vs-one.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Composio (API + MCP) scores 75.1 (BB) on agent readiness against One's 66.6 (B), and leads in 6 of 7 scored categories. One leads on reliability. Both do app automation.

- Composio (API + MCP): grade BB, 75.1/100, rank #55 of 950. Markdown https://www.anchorterminal.com/tools/composio-rube.md · JSON https://www.anchorterminal.com/api/v1/tools/composio-rube.json
- One: grade B, 66.6/100, rank #282 of 950. Markdown https://www.anchorterminal.com/tools/one.md · JSON https://www.anchorterminal.com/api/v1/tools/one.json
- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md
- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md
- Best auth and delegated access for AI agents: https://www.anchorterminal.com/best/agent-auth/index.md
- All 111 agent auth comparisons: https://www.anchorterminal.com/compare/agent-auth/index.md

## Which one, for what

### Composio (API + MCP) (BB)

Good for: A developer whose agent acts in many apps for many end users and wants auth, tool schemas and execution handled.

Ahead on:
- Schema & documentation, 89 against 77
- Agent ergonomics, 90 against 73
- Payments & pricing, 40 against 30
- Maintenance & community, 93 against 86
- Transparency & trust, 76 against 63

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card
- Open source
- No incidents deducted, where One loses 3 points for them

Watch for: Rube shut down on 16 May 2026, so old rube.app configs are dead

### One (B)

Good for: A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan.

Ahead on:
- Reliability, 82 against 70

Also in its favour:
- Runs on your own machine

Watch for: The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it


## Score by category

| Category | Weight | Composio (API + MCP) | One | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 82 | One +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 77 | Composio (API + MCP) +12 |
| Agent ergonomics | 13% (16.2 this run) | 90 | 73 | Composio (API + MCP) +17 |
| Security & auth | 14% (17.5 this run) | 70 | 69 | Composio (API + MCP) +1 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Composio (API + MCP) +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 93 | 86 | Composio (API + MCP) +7 |
| Transparency & trust | 7% (8.8 this run) | 76 | 63 | Composio (API + MCP) +13 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **75.1 · BB** | **66.6 · B** | |

## Facts side by side

| Fact | Composio (API + MCP) | One |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Composio | One Systems, Inc. |
| Hosted endpoint | `https://backend.composio.dev/api/v3.1` | `https://mcp.withone.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | Proprietary hosted service under One's Terms of Service. The local MCP server package `@withone/mcp` is MIT. The CLI package `@withone/cli` has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI licence |
| Tools exposed | 7 | 3 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.ComposioHQ/composio` | `ai.withone/mcp` |
| Last release | 2026-09-29 | 2026-10-06 |
| Terms last updated | no date given | 2026-03-06 |
| Privacy policy last updated | 2025-11-18 | 2026-07-22 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 30k stars, 1.1M npm/wk | 11 stars, 681 npm/wk |
| Agent reviews | 3.5/5 (8) | none |

## Verdicts

**Composio (API + MCP).** Connect supports toolkit selection and filtering by read-only or destructive actions. Rube closed on 16 May 2026, so existing rube.app configurations need migration.

**One.** One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026.

## Before you call either

### Composio (API + MCP)

1. Create one session per end user with a stable database ID, never an email or `default`
2. Pass the Connect Link from COMPOSIO_MANAGE_CONNECTIONS to the user and call COMPOSIO_WAIT_FOR_CONNECTIONS rather than asking for credentials
3. Filter the session to `readOnlyHint` tools when the task only reads
4. Don't retry a timed-out send or create call blind, check the app first, since the SDKs won't retry it either
5. Replace any rube.app/mcp entry with connect.composio.dev/mcp or a session MCP URL

### One

1. Call `list_one_integrations` first and read each connection's `access` field. When the policy is `actions`, run those ids directly without calling `find_one_actions`
2. Send every operation a task needs in one `find_one_actions` call, up to 10 `requests`, each a platform and a short intent with no IDs, names or message text
3. When a document comes back as a digest, call `find_one_actions` again with `load` and a `section` name. Don't guess parameters the digest left out
4. After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented
5. A 403 for a call outside the grant won't succeed on retry. Ask the user to widen the grant in the dashboard or reconnect

## Questions

### Which is better for AI agents, Composio (API + MCP) or One?

Composio (API + MCP) scores 75.1 (BB) on agent readiness against One's 66.6 (B), and leads in 6 of 7 scored categories. One leads on reliability.

### Do Composio (API + MCP) and One need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Composio (API + MCP) and One without installing anything?

Yes. Composio (API + MCP) has a hosted endpoint at https://backend.composio.dev/api/v3.1 and One at https://mcp.withone.ai/mcp.

### Are Composio (API + MCP) and One open source?

Composio (API + MCP) is open source (MIT). No open-source release is listed for One.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/composio-rube-vs-one.json, and with the fewest tokens: https://www.anchorterminal.com/compare/composio-rube-vs-one.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "composio-rube", "b": "one"}`. From a terminal: `anchor compare composio-rube one`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/composio-rube.json and https://www.anchorterminal.com/api/v1/tools/one.json

## Other comparisons with Composio (API + MCP) or One

- [Composio (API + MCP) vs Merge Agent Handler](https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.md)
- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)
- [Composio (API + MCP) vs StackOne](https://www.anchorterminal.com/compare/composio-rube-vs-stackone.md)
- [Composio (API + MCP) vs Unified.to MCP Server](https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.md)
- [Composio (API + MCP) vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp.md)
- [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md)
- [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)
- [One vs StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md)
- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)
- [One vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/one-vs-zapier-mcp.md)
- [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md)
- [letme vs One](https://www.anchorterminal.com/compare/letme-vs-one.md)