Connect once. Use everywhere.

Connect Gmail, GitHub, Notion, and 400+ apps through OOMOL.
Works instantly in your favorite AI agents.

One connection layer for your agents, Apps, and Skills

Use it in the agents you already know

Whether you work in Codex, Claude Code, Cursor, or a local agent, OOMOL can bring the same connected Apps, Tools, and Skills into that environment.

$ooSummarize today's Gmail to Notion

I'll call the $oo connector skill to read the user's authorized Gmail messages, then write a Notion note.

Thought 8s

Found 2 Apps

Called gmail.fetch_emails
Called notion.create_page

Result returned through oo without exposing account credentials.

A rich toolkit, ready to use

OOMOL connects to many popular Apps and includes built-in AI services like image, video, and voice generation. Authorize Tools once in OOMOL, then use them across agents without setting up each environment again.

Turn useful workflows into shareable Skills

After connecting accounts, tasks that once needed a workflow builder can run as Skills, with agents calling OOMOL tools. OOMOL lets you install those Skills in other agents or share them.

Agents only use Tools you approve

Manage App authorizations and Tool permissions in OOMOL. Agents never handle passwords or raw tokens. OOMOL keeps usage, results, and run records easy to review.

Work your agents can take on with OOMOL

Pexels to Google Photos

OOMOL lets agents search public media sources, choose an image that matches the brief, and save it into connected personal apps such as Google Photos without manual download and upload steps.

Prompt

/oo find a mac-style gray gradient wallpaper on Pexel and uploaded it to my Google Photos.

OOMOL execution plan
  1. Search Pexels for a mac-style gray gradient wallpaper
  2. Review matching wallpaper options
  3. Download the selected image
  4. Upload it to Google Photos

FAQ

What is OOMOL? Is it another AI Agent?

No. OOMOL is not a new chat agent, and it does not replace Codex, Claude Code, Cursor, or local agents. You keep working in the agent you already use; OOMOL connects third-party service accounts, provides callable Tools, and lets Skills be installed, published, and shared across agents.

What does “connect once, use everywhere” mean?

After you connect services such as Gmail, GitHub, Notion, and Slack in OOMOL, those capabilities can be used by different agents that connect to OOMOL. It does not mean every agent or every service is automatically available, and it does not skip authorization; account-based services still need your approval first, and available actions depend on the currently supported Tools.

Will agents receive my account passwords or raw tokens?

No. OOMOL does not hand account passwords or raw tokens to agents. You authorize third-party service accounts in OOMOL, and agents call OOMOL-provided Tools within approved scopes instead of reading your credentials directly or writing tokens into prompts or project files.

What data and actions can agents access? Can I view, revoke, or limit them?

What an agent can do depends on which accounts you connect, which scopes you authorize, and which Tools OOMOL currently provides. OOMOL App acts as the management surface for connections, permissions, usage, results, and execution records; revocation and limits follow the controls available in the current product interface.

Which agents can use OOMOL? Do I need to switch to an OOMOL chat interface?

No. You do not need to move to an OOMOL chat interface. OOMOL is for agent environments that can work through `oo-cli`; installing OOMOL App also installs `oo-cli`, and the App and CLI use the same account data. You can keep starting tasks in your own agent and let it call available Tools and Skills through OOMOL.

Which apps and Tools does OOMOL support? What if I need something missing?

OOMOL currently targets 400+ connected services, including real work systems such as Gmail, GitHub, Notion, and Slack, and can also provide third-party capabilities for image, video, voice, transcription, files, and more. Specific services and actions depend on current connection and Tool support. If a required service, private API, or custom capability is missing, extension paths such as Studio can fill the gap.

What is the difference between a Tool and a Skill? Why does OOMOL manage Skills?

A Tool is a concrete action an agent can call, such as reading a GitHub PR, writing to Google Sheets, or sending a Slack message. A Skill is reusable execution knowledge for an agent: which oo tools to call, how to pass parameters, and how to check results. OOMOL does not execute the Skill itself, but it lets Skills describe oo tools directly and supports cross-agent installation, publishing, and sharing.

Use OOMOL with any agent

Get started