| 1 | <div align="center"> |
| 2 | |
| 3 | <img src="assets/openconnector-readme-banner.png" alt="OpenConnector - Connect Once. Use Everywhere." width="100%" /> |
| 4 | |
| 5 | [English](README.md) | [简体中文](docs/README.zh-CN.md) | [繁體中文](docs/README.zh-TW.md) | [日本語](docs/README.ja.md) | [Русский](docs/README.ru.md) | [Français](docs/README.fr.md) |
| 6 | |
| 7 | [](LICENSE.txt) |
| 8 |  |
| 9 |  |
| 10 |  |
| 11 |  |
| 12 | |
| 13 | [](https://oomol.com/apps) |
| 14 | [](https://oomol.com/apps) |
| 15 | |
| 16 | </div> |
| 17 | |
| 18 | OpenConnector is an open-source connector gateway for AI agents and an alternative to Composio. |
| 19 | Connect user app accounts once, then expose a shared catalog of 1,000+ providers and 10,000+ |
| 20 | prebuilt Actions to agents and applications. |
| 21 | |
| 22 | Use the [Connector SDK](https://github.com/oomol-lab/connector-sdk) from app code, |
| 23 | [oo CLI](https://github.com/oomol-lab/oo-cli) as the local-agent relay, MCP from agent hosts, |
| 24 | HTTP/OpenAPI from custom clients, and the Web Console for administration and debugging. |
| 25 | |
| 26 | - Keep credentials, scopes, schemas, policies, and run logs inside an inspectable runtime. |
| 27 | - Run locally, on Fly.io, on Cloudflare-compatible infrastructure, or through OOMOL's hosted |
| 28 | runtime. |
| 29 | - Use the same provider ids, Action ids, schemas, and contracts across open-source and commercial |
| 30 | SaaS deployments. |
| 31 | |
| 32 | ## What It Provides |
| 33 | |
| 34 | - A working connector catalog across products such as GitHub, Gmail, Notion, BigQuery, Google |
| 35 | Analytics, Supabase, Airtable, Slack, and more. |
| 36 | - Credential handling for API keys, OAuth2, custom credentials, and no-auth providers. |
| 37 | - Inspectable Action contracts: request/response schemas, required scopes, and lazy-loaded executor |
| 38 | source. |
| 39 | - Runtime controls for connection identity, scopes, runtime tokens, action allow/block policies, |
| 40 | temporary file transit, and redacted run logs. |
| 41 | - Deployment options for local Docker or Node.js, Fly.io with persistent SQLite storage, |
| 42 | Cloudflare Workers with D1/R2/Static Assets, and OOMOL's hosted runtime. |
| 43 | |
| 44 | ## Where It Fits |
| 45 | |
| 46 | OpenConnector fits products where agents need durable access to the tools users already use, without |
| 47 | handing provider credentials to the agent process. |
| 48 | |
| 49 | - Agent products that need reusable access across work apps, developer tools, data systems, |
| 50 | communication platforms, and AI services. |
| 51 | - Products adding agent workflows that need stable, inspectable Action contracts for user app |
| 52 | access. |
| 53 | - Teams that want hosted auth for speed while keeping a path to private or self-hosted runtime |
| 54 | control. |
| 55 | |
| 56 | ## Developer Tools |
| 57 | |
| 58 | | Tool | Purpose | |
| 59 | | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 60 | | [Connector SDK](https://github.com/oomol-lab/connector-sdk) | Thin TypeScript HTTP client. Use `OpenConnector` for self-hosted runtimes, or `Connector` / `ProjectConnector` for OOMOL-hosted personal and SaaS end-user connections. | |
| 61 | | [oo CLI](https://github.com/oomol-lab/oo-cli) | Local agent relay for connector Actions. `oo connector` can search, inspect, and run Actions against OOMOL-hosted or self-hosted OpenConnector r |