One
Agent infrastructure, formerly Pica — managed auth, 50,000+ tools, and a universal MCP server for AI agents.
About
One is the March 2026 rebrand and ground-up rebuild of Pica (v3.0.0, 'Pica is now One'): an infrastructure layer that gives AI agents authenticated access to 250+ platforms and 50,000+ tools through one surface. The pitch is that agents shouldn't each re-solve OAuth, token refresh, rate limits, and API quirks — One handles the connective tissue.
The platform's pieces: managed OAuth and token lifecycle (AuthKit) with an embeddable connect flow; a universal MCP server that exposes every connected app to Cursor, Claude Desktop, Windsurf, and any MCP client; Bridge, which turns any API's documentation into a working MCP server; Flow, a multi-step workflow runtime with stateful pause/resume in a Git-friendly JSON format; Relay, a unified webhook layer with normalized payloads; and a CLI (one) for finding, connecting, and using apps with structured JSON output. Notably, the 50,000+ tool knowledge entries (schemas, edge cases, auth requirements) are open source and free forever, and the CLI repo is public and actively pushed.
What it can do
- Authenticated access to 250+ platforms and 50,000+ tools via one API
- Managed OAuth, token refresh, and embeddable connect flow
- Universal MCP server for Cursor, Claude Desktop, Windsurf, and any MCP client
- Bridge: turn any API documentation into an MCP server
- Flow: multi-step workflows with pause/resume in Git-friendly JSON
- Relay: unified webhooks with normalized payloads and guaranteed delivery
- Open-source tool knowledge base (50,000+ entries, free forever)
Setup
- Sign up at withone.ai and create a project.
- Connect user accounts via the embeddable AuthKit flow (OAuth/API keys handled by One).
- Point your MCP client at the universal MCP server, or install the
oneCLI. - Call actions across 250+ platforms, or build multi-step Flows in JSON.
- (Optional) Use Bridge to convert any API's docs into an MCP server.
Prerequisites
A One account; API credentials for whichever third-party platforms you connect; an MCP client or the CLI for agent use.
Use cases
Works with
Trust score — 7/10
Scored 7/10 (metrics tier, metrics-v1). Evidence: official changelog documents the Pica-to-One rebrand and v3.0.0 platform; CLI repo public with pushes as of Oct 15 2026 (413 stars); rebrand history corroborated by an independent API index. Strengths: active development, genuinely useful open-source knowledge base, clear agent-infrastructure positioning. Docked for: (1) closed SaaS core — auth tokens flow through their infrastructure; (2) '50,000+ tools' is provider-counted; (3) rebranded companies sometimes churn pricing and packaging — verify current terms. License: closed SaaS (CLI and knowledge base open).
★ 413 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 6.0/10
- Maintenance · recency, releases, issue load
- 8.0/10
- Openness · license + docs
- 4.0/10
- Manual review · sanity read + red-flag check
- 7.0/10
- · Rebranded from Pica in Mar 2026 (v3.0.0) — documented in official changelog; agent infrastructure with 250+ platforms and 50,000+ tools (provider-counted)
- · CLI repo public, 413 stars, pushed Oct 15 2026; 50,000+ tool knowledge entries open-sourced free forever; universal MCP server, Bridge, Flow, Relay verified via official changelog
- · manual review: closed SaaS core — auth tokens flow through their infrastructure; rebranded companies sometimes churn pricing/packaging — verify current terms
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.