Back to Gap Map Product / UX / Agent tools & connectors

OpenConnector

open source / Overall score: 3.2

Open-source connector gateway: connect a user's app accounts once, then expose a shared catalogue of over a thousand providers and their prebuilt actions to agents over SDK, CLI, MCP, HTTP or OpenAPI, with credential encryption and token refresh behind the runtime boundary.

The licence file is `LICENSE.txt` - a citation of `LICENSE` 404s, which is the kind of dead link a corpus should not carry. The npm package reads zero downloads for the window because the primary distribution is a GHCR Docker image, so adoption is read from stars. The provider count differs between the repository description (1500+) and the README body (1,000+) because the badges read a live catalogue endpoint; neither number is pinned here.

Openness

5 high confidence

5.0

license: Apache-2.0(OSI)
source: public(the gateway, its catalogue and its credential handling)
self-host: yes(docker compose, Helm, Fly.io or a single binary)
service: optional(the vendor also runs a hosted tier)
core features withheld: no — nothing withheld from the published tree

Apache-2.0 covers the gateway itself, unusual for this category since the hosted alternatives are typically closed and do not publish the part that holds credentials. The README documents a separate hosted offering without holding back any part of the published platform, so the core is ungated.

https://api.github.com/repos/oomol-lab/open-connector recorded 2026-09-17
Repository metadata: spdx_id Apache-2.0, 5,794 stars, not archived, not a fork, last pushed 2026-09-17, description "Open-source auth gateway connecting 1500+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI."
https://raw.githubusercontent.com/oomol-lab/open-connector/main/LICENSE.txt recorded 2026-09-17
The LICENSE.txt body: the verbatim Apache License 2.0 text. Note the path - the repository has no file named `LICENSE`, and a citation of that name returns 404.
https://raw.githubusercontent.com/oomol-lab/open-connector/main/README.md recorded 2026-09-17
The README's deployment table names the hosted offering as a separate product and says exactly what it adds, which is what the `ungated` acceptance standard asks for: hosted gives "Managed OAuth and hosted runtime, ready to use. No deployment or OAuth app setup", self-hosted is "Run locally or on your own infrastructure with Docker or Node.js. You manage storage and OAuth apps." The gateway, its catalogue and its credential handling are in the published tree either way; what the hosted tier supplies is OAuth client registrations, not code.

Adoption

2 low confidence

2.0

The npm package @oomol-lab/open-connector shows zero downloads for the trailing month, but that is not a sign of disuse: the README distributes the runtime primarily as a GHCR Docker image and lists npm only as an embeddable option. Container registries publish no download count this map can read, leaving GitHub stars as the only usable signal.

https://api.github.com/repos/oomol-lab/open-connector recorded 2026-09-17
Repository metadata for oomol-lab/open-connector: 5,794 stargazers.

Capability

5 medium confidence

5.0

Open-connector covers many providers and holds and refreshes their credentials itself, with a runtime the caller can self-host or run hosted. Either way the gateway performs the OAuth flow and stores the grant; only who registers the OAuth application changes, matching Composio, the closed-source product built the same way.

https://raw.githubusercontent.com/oomol-lab/open-connector/main/README.md recorded 2026-09-17
The README: "an open-source connector gateway for AI agents and an alternative to Pipedream/Composio. Connect user app accounts once, then expose a shared catalog of 1,000+ providers and 10,000+ prebuilt Actions", with "Credential handling for API keys, OAuth2, custom credentials, and no-auth providers", "Provider secrets stay behind the runtime boundary" and "named connections, credential encryption, token refresh, and action policies". The deployment table: hosted gives "Managed OAuth and hosted runtime... No deployment or OAuth app setup"; self-hosted means "You manage storage and OAuth apps".

Verified 2026-09-17