What is OpenConnector?
OpenConnector, from the Chinese workflow company OOMOL, is a connector gateway for AI agents in the mould of Composio or Pipedream Connect. You connect a user's GitHub, Gmail, Notion, Slack or BigQuery account once; the gateway holds the credentials and exposes prebuilt Actions, with request and response schemas and required scopes, to agents over MCP, HTTP and OpenAPI, a TypeScript SDK or OOMOL's oo CLI. The agent process never sees the provider token.
The README counts more than 1,000 providers and 10,000 Actions. It runs from a Docker image or Node.js with SQLite or PostgreSQL state, on Kubernetes with a Helm chart, or on Cloudflare Workers and Fly.io, with a web console for credentials, runtime tokens, allow and block policies and redacted run logs. OOMOL also runs it as a hosted service with its own OAuth apps.
The repository was created on 29 June 2026 and has about 6,200 GitHub stars; v1.9.4 shipped on 27 October 2026. Releases up to v1.9.4 are Apache 2.0; later code is under a modified Apache 2.0 licence that requires a commercial licence to offer it to third parties as a hosted connector service.
Is OpenConnector worth it?
OpenConnector's value is architectural: agents get Action names, schemas and safe account labels, while API keys and OAuth tokens stay in the runtime. That is the right boundary for an agent that reads untrusted content, because a prompt injection cannot exfiltrate a token the process never held. Runtime tokens, per-connection identities, scopes and allow or block policies on Actions add a second layer, and run logs are redacted. A GitHub App installation can mint one-hour tokens on demand instead of storing a long-lived personal token.
The catalogue is the reason to choose it over writing connectors yourself, and the deployment options are generous: SQLite for a laptop, PostgreSQL 15+ with explicit migrations for production, a hardened Helm chart with NetworkPolicy toggles, or Cloudflare Workers with D1 and R2. The same provider and Action IDs work across self-hosted and OOMOL-hosted deployments, so a team can start hosted and move in-house without rewriting agent code.
Two things need reading before adopting it. Self-hosted OAuth providers require OAuth client credentials from apps you register with each provider, which for Google or Microsoft means verification work; the hosted service removes that by using OOMOL's apps, at the cost of OOMOL holding the tokens. And the licence changed: code after v1.9.4 forbids offering OpenConnector to third parties as a hosted connector service without a commercial licence from OOMOL, which matters to any agent platform that planned to resell it. GitHub reports the licence as unrecognised for that reason.
The quickstart's curl calls to localhost carry no runtime token, and the README points to a security baseline before deploying, so treat the defaults as development settings. A catalogue this large, built in four months, will have uneven Actions; the provider count in the repository description (1,500+) and the README (1,000+) do not even agree. Against Composio the trade is control and self-hosting for a younger catalogue and a much smaller company behind it.
Where it earns its place
A platform engineer at a 200-person SaaS company building an internal agent
Give the agent access to GitHub, Notion and Google Workspace without putting tokens in its environment
Deploy the Helm chart with PostgreSQL, register OAuth apps with each provider, issue the agent a runtime token, and block write Actions it should not call. Free to self-host; the work is OAuth app registration and verification.
A two-person start-up shipping an agent that acts in its customers' tools
Let end users connect their own accounts on day one
Use OOMOL-hosted connectors so users authorise through OOMOL's OAuth apps, within 20,000 free App tool calls a month. Check the commercial licence before planning to self-host and resell later.
A developer using Claude Code on a laptop
Call Hacker News, GitHub and BigQuery Actions from the agent through one MCP server
Run docker compose up, add a GitHub personal access token in the console, and point the agent at localhost:3000/mcp. Add a runtime token before exposing it beyond the machine.
Before you commit
- Setup
- docker compose up pulls ghcr.io/oomol-lab/open-connector:latest; the console and API reference open on localhost:3000 and a no-auth Hacker News Action verifies it. Building from source needs Node.js 22.23.4+, 24.22.1+ or 26.12.1+.
- Integrations
- More than 1,000 providers including GitHub, Gmail, Notion, BigQuery, Google Analytics, Supabase, Airtable, Slack and Microsoft Teams; MCP at /mcp, /v1/actions HTTP, OpenAPI 3.1, the Connector SDK and oo CLI.
- Data and privacy
- Credentials, connections and redacted run logs stay in your SQLite or PostgreSQL store when self-hosted; OOMOL-hosted connectors keep tokens with OOMOL. Optional credential encryption. Releases to v1.9.4 Apache 2.0; later code adds a hosted-service restriction.
- Cost at scale
- Self-hosting costs only your infrastructure. OOMOL hosted includes 20,000 App tool calls a month, then 0.0003 credits per call, with credits bought in the OOMOL console at a price not shown on the pricing page.
- Limits
- About ten open issues; OAuth providers need your own registered apps when self-hosted; PostgreSQL migrations must be run explicitly before upgrades; v1.9.4 required patched Node and Bun runtimes for a CVE.
What’s good
- Provider credentials never reach the agent process
- MCP, HTTP, OpenAPI, SDK and CLI from one runtime
- SQLite, PostgreSQL, Helm and Cloudflare Workers deployments
- Same Action IDs hosted or self-hosted
What’s not
- Post-v1.9.4 licence bars resale as a hosted service
- Self-hosted OAuth needs your own registered apps
- Hosted credit price not published
- Four-month-old catalogue of uneven depth
Best for
Teams building agent products who want a self-hosted credential boundary and a large connector catalogue without adopting a closed integration platform.
OpenConnector alternatives
OpenConnector: common questions
- Is OpenConnector worth it?
- OpenConnector is a credible self-hosted answer to Composio, with credentials kept behind a gateway, but its licence has just tightened and OAuth providers still mean registering your own apps. We rate it 3.8 out of 5.
- How much does OpenConnector cost?
- Self-hosting is free under the OpenConnector License (modified Apache 2.0). OOMOL hosted: 20,000 free App tool calls a month, then 0.0003 credits per call; the price of a credit is not published.
- What are the downsides of OpenConnector?
- Post-v1.9.4 licence bars resale as a hosted service; self-hosted OAuth needs your own registered apps; hosted credit price not published; four-month-old catalogue of uneven depth.
- Who is OpenConnector best for?
- Teams building agent products who want a self-hosted credential boundary and a large connector catalogue without adopting a closed integration platform.
- How much does OpenConnector cost for a team or in production?
- Self-hosting costs only your infrastructure. OOMOL hosted includes 20,000 App tool calls a month, then 0.0003 credits per call, with credits bought in the OOMOL console at a price not shown on the pricing page.
- Is OpenConnector safe for company data?
- Credentials, connections and redacted run logs stay in your SQLite or PostgreSQL store when self-hosted; OOMOL-hosted connectors keep tokens with OOMOL. Optional credential encryption. Releases to v1.9.4 Apache 2.0; later code adds a hosted-service restriction.
- What are the best OpenConnector alternatives?
- The closest alternatives we have reviewed are Activepieces, ToolHive and n8n.
Answers checked Oct 31, 2026.