OpenConnector overview
OpenConnector is a source-available project by OOMOL. Browse the connector catalog for available integrations. This guide covers deployment and runtime operation.
OOMOL OpenConnector is a source-available, self-hostable connection runtime. Use it when your organization needs to operate credential storage, provider connections, network access, action policy, logs, and upgrades inside its own environment.
The runtime exposes provider actions through MCP, HTTP, OpenAPI, and a web console. Agents and clients work with schemas, connection labels, scopes, and results while raw provider credentials remain inside your deployment boundary.
License and commercial use
OpenConnector uses the OpenConnector License, a modified Apache 2.0 license with additional conditions.
The license permits commercial use, modification, use within your organization, and deployments for a client to use within that client’s organization. You may also embed OpenConnector in a product whose primary value lies elsewhere, with users connecting their accounts as part of using that product.
Providing OpenConnector or a modified version to third parties as a hosted or managed service whose primary value is OpenConnector’s functionality requires a commercial license from OOMOL. This includes connector gateways, integration platforms, and APIs for connecting accounts and running OpenConnector Actions.
Releases up to and including v1.9.4 remain under the unmodified Apache 2.0 license. Third-party API terms and authorization requirements still apply.
Choose a deployment target
| Target | Use it when |
|---|---|
| Docker Compose | You want the shortest path to a local or single-server runtime |
| Source runtime | You are developing OpenConnector or provider executors |
| Cloudflare Workers | You want runtime records in D1 and temporary transit files in R2 |
The self-hosting guide covers all three targets.
What you operate
Your team is responsible for:
- Admin and runtime access tokens.
- Credential encryption keys and sensitive runtime storage.
- The public origin used by OAuth callback URLs.
- Provider OAuth clients or API key configurations.
- Action allowlists and blocklists.
- Backups, network controls, monitoring, and upgrades.
Connect providers
OpenConnector supports API key, custom credential, OAuth2, and no-auth provider connections. Start with the general OAuth app configuration guide, then open a provider-specific guide when the provider requires its own setup:
Start with a protected runtime
Set an admin token and credential encryption key before exposing the runtime outside your own shell. Create separate runtime tokens for Agents and clients, and limit available actions to the operations they require.
Follow the OOMOL OpenConnector self-hosting guide to deploy the runtime. Then call your self-hosted runtime with the OpenConnector SDK from TypeScript.