open-connector
OpenConnector is an open-source connector gateway for AI agents, offered as an alternative to Composio. You connect user app accounts once, and the runtime exposes a shared catalogue of 1,000+ providers and 10,000+ prebuilt Actions (GitHub, Gmail, Notion, BigQuery, Google Analytics, Supabase, Airtable, Slack and more) to agents and applications. The idea is that agents get durable access to tools users already use without provider credentials being handed to the agent process.
It handles API keys, OAuth2, custom credentials and no-auth providers, with inspectable Action contracts (request and response schemas, required scopes, lazy-loaded executor source) and runtime controls for connection identity, scopes, runtime tokens, allow and block policies, temporary file transit and redacted run logs. You can use the Connector SDK, the oo CLI as a local-agent relay, an MCP endpoint (http://localhost:3000/mcp), HTTP and OpenAPI, or the web console. Run it locally with `docker compose up`, on Fly.io with persistent SQLite, on Cloudflare Workers with D1 and R2, or through OOMOL's hosted runtime. The code is Apache-2.0 licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-27
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 19
- Latest release
- v1.9.4 (2026-10-27)
- Open issues
- 3
- Recent issues with at least one comment
- 3/4
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #669 Multi-tenant connections2 comments · 2026-10-07
- #649 Integration idea: external source-rights evidence before tool/data admission1 comments · 2026-10-04
- #675 Discussion: Product scope of external credentials and impact on the SDK and Open Flow0 comments · 2026-10-08
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want your agents to use 1,000+ app integrations without handing provider credentials to the agent process.
- You want a self-hostable alternative to Composio, runnable with Docker, on Fly.io or on Cloudflare Workers.
- You want inspectable Action contracts (schemas, required scopes, executor source) with scopes, runtime tokens and allow and block policies.
- You need deep coverage of one service: integration depth varies across 1,000+ providers.
- You want no vendor path at all: hosted authentication and the commercial runtime come from OOMOL, and self-hosting means you run the runtime yourself.
- You do not want to connect and manage each provider's account, credentials and scopes.
How it differs
vs aci★ 4.9kBoth offer a catalogue of integrations with built-in OAuth for agents. OpenConnector lists 1,000+ providers and 10,000+ Actions and keeps credentials out of the agent. ACI lists 600+ integrations with dynamic tool discovery.
vs klavis★ 5.8kKlavis bundles Strata tool routing, 100+ MCP integrations and an MCP sandbox for RL training. OpenConnector is a connector gateway with a far larger catalogue.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!