Meta tags:
description=Use the OOMOL SDK to connect your product or AI agents to apps through one managed connection layer.;

Headings (most frequently used words):

app, the, use, your, with, hosting, one, integrations, connect, work, set, of, call, keep, self, preferences, and, sdk, sdk1000, let, users, apps, they, already, stop, rebuilding, same, api, up, first, integration, less, connections, multiple, ways, to, launch, faster, control, faq, explore, support, company, choose, cookie, privacy, ready, made, credentials, out, code, once, everywhere, create, project, configure, start, user, authorization, monitor, actions, connector, oo, cli, mcp, http, openapi, oomol, deploy, on, cloudflare, host, openconnector, still, have, questions,

Text of the page (most frequently used words):
and (49), the (33), your (25), oomol (22), use (19), sdk (17), can (15), #hosting (15), apps (13), connection (13), self (12), product (12), for (11), when (10), authorization (9), calls (9), mcp (9), you (8), #credentials (8), backend (8), app (8), storage (7), from (7), support (7), oauth (7), connections (7), cli (7), http (7), api (6), same (6), open (6), integrations (6), one (6), preferences (5), site (5), service (5), cloudflare (5), connect (5), connected (5), account (5), action (5), users (5), team (5), access (5), project (5), call (5), parameters (5), read (5), cookie (4), optional (4), these (4), keep (4), choose (4), deployment (4), data (4), accounts (4), status (4), logs (4), control (4), credential (4), scopes (4), actions (4), through (4), backends (4), source (4), work (4), with (4), create (4), all (3), which (3), settings (3), pricing (3), skills (3), github (3), 1000 (3), tools (3), does (3), guide (3), keys (3), key (3), code (3), hosted (3), operations (3), provider (3), agents (3), that (3), should (3), stay (3), each (3), openapi (3), console (3), managed (3), handle (3), view (3), typescript (3), layer (3), get (3), started (3), accept (2), choices (2), reject (2), understand (2), aggregate (2), usage (2), experience (2), such (2), required (2), manage (2), time (2), privacy (2), policy (2), about (2), assets (2), docs (2), english (2), auto (2), contact (2), still (2), have (2), are (2), services (2), across (2), only (2), check (2), before (2), calling (2), know (2), controls (2), over (2), yes (2), interfaces (2), supports (2), custom (2), auth (2), flows (2), while (2), browser (2), start (2), user (2), tokens (2), case (2), entry (2), names (2), permissions (2), need (2), host (2), openconnector (2), deploy (2), let (2), launch (2), sooner (2), add (2), needs (2), install (2), without (2), set (2), its (2), configure (2), authorize (2), integration (2), already (2), airtable (2), supabase (2), slack (2), notion (2), gmail (2), close, save, helps, improve, content, performance, analytics, remembers, selected, appearance, mode, functional, core, behavior, consent, cannot, turned, off, necessary, change, footer, any, customize, essential, working, remember, terms, company, brand, explore, français, русский, 日本語, dark, light, copyright, 2026, contributors, youtube, discord, help, choosing, between, questions, logos, examples, saas, developer, productivity, systems, shown, here, report, active, reauthorization, error, disconnected, reconnect, expires, how, whether, usable, manages, runtime, database, encryption, updates, this, path, gives, more, operational, what, wants, fewer, tasks, around, uptime, fit, review, schemas, labels, exposing, features, deployments, also, publish, limit, exposed, providers, type, wait, return, synchronously, trusted, pages, facing, but, execution, involve, admin, sensitive, identifiers, server, side, serve, agent, workflows, depends, expose, share, point, fits, points, allowed, using, where, live, answers, paths, faq, web, own, environment, full, setup, workers, static, lightweight, edge, reduce, option, want, faster, plain, description, generated, clients, give, hosts, remain, checking, reading, verifying, terminal, command, line, tool, embed, connector, method, repeating, multiple, ways, select, execute, monitor, link, callback, config, enter, details, projects, store, then, first, less, asking, again, once, everywhere, out, spend, instead, pagination, errors, ready, made, brings, records, into, stop, rebuilding, stripe, figma, zoom, hubspot, google, sheets, browse, not, rebuild, them, they, callable, 10000, complete, solution, reliable,

Text of the page (random words):
oomol sdk for app integrations self hosting cli skills apps pricing get started self hosting cli skills apps pricing get started one sdk 1000 app integrations oomol is a complete open source app integration solution for one reliable connection layer across ai agents and product backends get started self hosting guide 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 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 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 01 create a project create a project in oomol console and store its project id and api key in your backend open projects 02 configure the app add a provider config enter the app s oauth details and choose the scopes your product needs open connections 03 start user authorization use the sdk to create an authorization link and handle the callback in your product view sdk 04 call and monitor actions select a connected account execute an action from your backend and check its status and logs in oomol view logs 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 connector sdk access connected apps from typescript backends and embed integrations in your product view sdk oo cli open source command line tool for checking connections reading parameters and verifying calls from your terminal install oo cli mcp use oomol s mcp support to give mcp hosts access to connected apps while accounts and permissions remain managed in oomol install mcp http and openapi use plain http or read the openapi description when you need generated clients read docs 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 read sdk guide edge deployment deploy on cloudflare use workers d1 r2 and static assets for a lightweight service managed by your team read cloudflare setup open source self hosting self host openconnector keep the connection service web console and data in your own environment when you need full control read self hosting 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 x discord youtube github copyright 2026 oomol contributors cookie settings auto auto light dark english english 中文 日本語 русский français explore apps skills pricing support support docs brand assets company about terms of service privacy policy choose your cookie preferences we use essential storage to keep the site working and optional storage to remember preferences and understand aggregate site usage customize reject optional accept all cookie settings privacy preferences manage which optional storage oomol can use you can change these choices from the footer at any time necessary required for core site behavior and consent storage these cannot be turned off functional remembers site preferences such as your selected appearance mode analytics helps us understand aggregate site usage so we can improve the experience content and performance reject optional save choices accept all close cookie preferences