&color=rgb(255%2C%20255%2C%20255%2C%200))
&color=rgb(0%2C0%2C0%2C0))
npm i @oomol-lab/connector Use ready-made integrations
Connect the apps your users already know, and spend your time on product experience instead of pagination, parameters, errors, and scopes.
One SDK1000+ app integrations
OOMOL is a complete open-source app integration solution for one reliable connection layer across AI agents and product backends.
- 1000+
- app integrations
- 10000+
- callable tools
- 1
- open-source SDK
Let users connect the apps they already use
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 Apps GitHub
Gmail
Notion
Slack
Supabase
Airtable
Google Sheets
HubSpot
Zoom
Figma
Stripe
Cloudflare
Stop rebuilding the same API work
OOMOL brings authorization, credentials, parameters, calls, and records into one managed connection layer for your product.
Keep credentials out of your app code
API keys, OAuth tokens, and connection settings stay in OOMOL. Your backend calls with connection names and parameters.
Connect once, use everywhere
TypeScript backends, MCP tools, and HTTP calls can use the same accounts without asking users to authorize again.
Set up your first integration with less work
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
Create a project in OOMOL Console and store its project ID and API key in your backend.
-
Configure the App
Add a provider config, enter the App's OAuth details, and choose the scopes your product needs.
-
Start user authorization
Use the SDK to create an authorization link and handle the callback in your product.
-
Call and monitor actions
Select a connected account, execute an action from your backend, and check its status and logs in OOMOL.
One set of connections, multiple ways to call
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.
TypeScript
Connector SDK
Access connected apps from TypeScript backends and embed integrations in your product.
Terminal
oo CLI
Open-source command-line tool for checking connections, reading parameters, and verifying calls from your terminal.
oo login MCP
MCP
Use OOMOL's MCP support to give MCP hosts access to connected apps while accounts and permissions remain managed in OOMOL.
connector.oomol.com/v1/mcp REST
HTTP and OpenAPI
Use plain HTTP, or read the OpenAPI description when you need generated clients.
GET /v1/catalog Launch faster with hosting, keep control with self-hosting
Use 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.
Hosted option
OOMOL hosting
Let OOMOL handle authorization, credentials, and calls to reduce operations work and launch sooner.
Edge deployment
Deploy on Cloudflare
Use Workers, D1, R2, and Static Assets for a lightweight service managed by your team.
Open-source self-hosting
Self-host OpenConnector
Keep the connection service, web console, and data in your own environment when you need full control.
FAQ
Answers about hosting, credential storage, access paths, permissions, and connection status.
Where do account credentials live?
Credentials stay in OOMOL. Your backend calls allowed interfaces through SDK, MCP, or HTTP using connection names and parameters.
Which entry points can use these connections?
SDK, oo CLI, MCP, HTTP, and OpenAPI can all use the same connections. Choose the entry point that fits your product.
Can agents and my product backend share the same connections?
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.
Should I call the SDK from the browser or from my backend?
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.
Does it support OAuth only?
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.
Can I limit which actions are exposed?
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.
When does OOMOL hosting fit?
Use hosted OOMOL when your team wants fewer operations tasks around OAuth apps, credential storage, and service uptime.
What do we manage when self-hosting?
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.
How do I know whether a connection is usable?
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.
Does it only support the apps shown here?
No. These logos are examples. OOMOL can connect to 1000+ apps and services across SaaS, developer tools, productivity apps, data systems, and AI services.
Still have SDK questions?
Contact OOMOL Support for help choosing between the SDK, OOMOL hosting, Cloudflare deployment, or self-hosting.
Contact support