OOMOL is a complete open-source app integration solution for one reliable connection layer across AI agents and product backends.
GitHub, Gmail, Notion, Slack, Supabase, Airtable: you should not have to rebuild auth and calls for each one. Connect them through OOMOL and use one connection layer in your product.
Browse AppsOOMOL brings authorization, credentials, parameters, calls, and records into one managed connection layer for your product.
Connect the apps your users already know, and spend your time on product experience instead of pagination, parameters, errors, and scopes.
API keys, OAuth tokens, and connection settings stay in OOMOL. Your backend calls with connection names and parameters.
TypeScript backends, MCP tools, and HTTP calls can use the same accounts without asking users to authorize again.
Create a project and configure an App in OOMOL Console, then use the SDK in your backend to authorize users and call actions.
Create a project in OOMOL Console and store its project ID and API key in your backend.
Add a provider config, enter the App's OAuth details, and choose the scopes your product needs.
Use the SDK to create an authorization link and handle the callback in your product.
Select a connected account, execute an action from your backend, and check its status and logs in OOMOL.
The TypeScript SDK, oo CLI, MCP, and HTTP can call the same connected accounts. Choose the calling method for each use case without repeating authorization or credential work.
Access connected apps from TypeScript backends and embed integrations in your product.
View SDKOpen-source command-line tool for checking connections, reading parameters, and verifying calls from your terminal.
Install oo CLIUse OOMOL's MCP support to give MCP hosts access to connected apps while accounts and permissions remain managed in OOMOL.
Install MCPUse plain HTTP, or read the OpenAPI description when you need generated clients.
Read docsUse OOMOL hosting to handle authorization, credentials, and calls when you want to add integrations sooner. Deploy on Cloudflare or self-host OpenConnector when your team needs control over code, data, and operations.
Let OOMOL handle authorization, credentials, and calls to reduce operations work and launch sooner.
Use Workers, D1, R2, and Static Assets for a lightweight service managed by your team.
Keep the connection service, web console, and data in your own environment when you need full control.
Answers about hosting, credential storage, access paths, permissions, and connection status.
Credentials stay in OOMOL. Your backend calls allowed interfaces through SDK, MCP, or HTTP using connection names and parameters.
SDK, oo CLI, MCP, HTTP, and OpenAPI can all use the same connections. Choose the entry point that fits your product.
Yes. The same connection service can serve agent workflows through oo CLI or MCP and product backends through SDK or HTTP. Access still depends on the account, scopes, and actions you expose for each use case.
Use the SDK from a trusted backend. Browser pages can start user-facing authorization flows, but execution calls that involve project credentials, admin tokens, or sensitive connection identifiers should stay on the server side.
No. OOMOL supports OAuth, API keys, custom credentials, and no-auth providers when the provider action supports that connection type. OAuth flows can wait for authorization, while API key and custom credential connections can return an account synchronously.
Yes. Review provider scopes, action schemas, and connection labels before exposing an action to agents or product features. In self-hosted deployments, your team also controls deployment policy, storage, logs, and the interfaces you publish.
Use hosted OOMOL when your team wants fewer operations tasks around OAuth apps, credential storage, and service uptime.
When self-hosting, your team manages OAuth apps, API keys, the runtime database, encryption key, deployment, updates, logs, and access controls. This path gives you more operational control over code and data.
Connected accounts report status such as active, reauthorization required, error, or disconnected. Your product can check the account status before calling an action and guide users to reconnect when authorization expires.
No. These logos are examples. OOMOL can connect to 1000+ apps and services across SaaS, developer tools, productivity apps, data systems, and AI services.
Contact OOMOL Support for help choosing between the SDK, OOMOL hosting, Cloudflare deployment, or self-hosting.
Contact support&color=rgb(255%2C%20255%2C%20255%2C%200))
&color=rgb(0%2C0%2C0%2C0))
