Authorize once, reuse across agents
Connect and authorize in OOMOL once. Codex, Claude Code, Qode, OpenCrawl, and terminal workflows can keep calling those capabilities through oo-cli.
Your agent thinks and decides. OOMOL handles the rest.
Start by connecting agents through oo-cli to third-party services like Gmail and Notion, plus your own systems. When packaged capabilities are not enough, use OOMOL Studio to build and extend your own tools.
Click to copy the oo-cli install command for your system.
One connection path for every agent
Connect accounts, apps, and tool capabilities to OOMOL once, then let Codex, Claude Code, Qode, and terminal workflows call them through the same oo-cli path.
Build custom tools in Studio
When packaged tools are not enough, compose third-party blocks, cloud functions, APIs, and business logic in OOMOL Studio, then deliver and reuse them through OOMOL.
Step 1: Start with connected services and tools
Let agents run common work first
If a published tool or connected service already solves the job, OOMOL's first layer of value is simple: connect it, run it, and skip building your own tool at the start.
GitHubSlack
Summarize a GitHub PR and send it to Slack
Useful when you want to turn PR review into a team update without manual summarizing.
Say this
Summarize the key points in this PR and send them to a Slack channel.
The agent does
Read the diff, extract key points, and post to the target channel.
NotionLinear
Turn a Notion spec into Linear tasks
Useful when you want to turn a spec page into trackable work without manual breakdown.
Say this
Read this Notion page, break it into tasks, and sync them to Linear.
The agent does
Extract requirements, shape tasks, and write them back to Linear.
GmailYour API
Read a Gmail attachment, then call your API
Useful when you want to pipe email inputs straight into your own service.
Say this
Read the Gmail attachment, call our PDF API, and return the result.
The agent does
Download the attachment, call your API, and return the output.
Behind those capabilities are connected apps and tools
OOMOL comes with support for 239 apps and 3,385 packaged tools. They are not scattered APIs, but work entries agents can call directly through oo-cli. After common work is running, decide what is worth orchestrating further, extending, or turning into your own tool.
239
appsCovering common services across collaboration, development, marketing, and payments.
3,385
packaged toolsNot raw APIs, but ready-to-use actions.
Common apps are already available
GitHub
Slack
Notion
Gmail
Linear
Vercel
Supabase
Twilio
Developer path 01Build in Studio
When packaged tools are not enough, generate, compose, and validate in OOMOL Studio
Use the agent to get started, then keep editing code, dependencies, parameters, and workflows yourself. This is the developer path: Studio is for building tools, not replacing oo-cli for day-to-day calls.
Developer path 02Deliver through Cloud
Once validation is done, let Cloud handle delivery and runtime
Cloud takes over runtime, configuration, secrets, access, and delivery so you do not need to build another backend around the same implementation.
Handle delivery and hosted runtime in one place
Keep the same implementation as you deliver the tool to yourself, your team, or customers.
Keep config, access, and usage in one backend
Manage secrets, access, releases, runtime settings, and usage data in one place.
Start delivery with included usageFree users get 200 Cloud Task minutes refreshed every month, so first delivery does not require buying servers or reserving capacity.
Developer path 03Return to oo-cli
After delivery, make it ready for agents
Once the tool is built and delivered, agents in Codex, OpenClaw, and Claude Code keep using the same oo-cli path to search for it, inspect it, and call it. For users, published tools and custom tools end up at the same entry point.
GUI extension of oo-cli
You can keep using the same tools through OOMOL AI
Once you have tools connected through oo-cli, OOMOL AI gives you the official GUI for using those same capabilities across web, desktop, and iOS.
WebDesktopiOS
Start with published tools, then enter the developer path when they are not enough
Use oo-cli to get connected services and published tools working first. Only when you need to produce, combine, and deliver your own tools do you move into Studio and Cloud.