Authorize once, then keep using it across agents
Many users switch between Codex, Claude Code, Qode, OpenCrawl, and other agents. Once connection and authorization are set up in OOMOL, those capabilities stay available through oo-cli.
Your agent thinks and decides. OOMOL handles the rest.
Connect agents through oo-cli to third-party services like Gmail and Notion, as well as your own systems. Use OOMOL Studio to build and extend your own tools.
Why you need oo-cli
Account access and tool capabilities should not be locked to a single agent platform. With oo-cli, they can be managed independently and called from different agents or terminal environments.
Custom capabilities travel with you like tools
When ready-made tools are not enough, you can combine third-party blocks, add cloud functions, and connect your own APIs and business logic, then keep reusing them through oo-cli across environments. Over time, that becomes your own portable toolbox.
Through oo-cli, users can connect to a mature SaaS ecosystem and call custom function tools.
Start with the apps OOMOL already connects
OOMOL comes with support for 229 apps and 3,286 packaged tools. Start with connected services and published tools through oo-cli, then decide what is worth orchestrating further, extending, or turning into your own tool.
229
appsCovering common services across collaboration, development, marketing, and payments.
3,286
packaged toolsNot raw APIs, but ready-to-use actions.
Common apps are already available
GitHub
Slack
Notion
Gmail
Linear
Vercel
Supabase
Twilio
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.
Developer entry
When connected services are not enough, move into OOMOL Studio
In Studio, you can recombine connected services, add code, orchestrate workflows, and write new function tools. Once the tool works locally, hand it to Cloud for delivery.
Turn connected services into your own tool
Take GitHub, Slack, Notion, Gmail, and other connected services and reorganize them into your own execution chain instead of stopping at one-off use.
Turn multi-step logic into a workflow
Turn branching, retries, coordination, and multi-step logic into repeatable workflows instead of rebuilding them ad hoc.
Write new function tools directly
When existing wrappers are not enough, write new function tools and bring in your own APIs, business systems, and business logic.
Move the new tool into the delivery path
Studio is not the endpoint. Once local validation is done, the next step is Cloud, then mainly back into oo-cli so agents can keep using the same path.
01Build in Studio
Start in OOMOL Studio to generate, compose, and validate
Use the agent to get started, then keep editing code, dependencies, parameters, and workflows yourself. Studio is for building tools, not day-to-day tool use.
Studio demo video
Show the path from prompting to generating a tool and validating it locally.
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.
Cloud console preview
Bring runtime settings, secrets, and delivery into one backend.
03Use from oo-cli
Finally, hand the tool back to oo-cli so agents can use it
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.
oo-cli invocation demo
Shows a delivered tool being searched, inspected, and called in Codex.
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
Included Usage
Start delivery with the included free quota
Free users get 200 Cloud Task minutes refreshed every month. Use them to deliver the tool through Cloud first, then top up or upgrade when the quota is not enough.
Free quota
Included Monthly
200 min
Included Cloud Task time
Deliver the tool and start using it
Use the monthly refreshed quota to deliver the tool, confirm it keeps running, and make sure it is searchable and callable in oo-cli.
A good fit for first delivery, lightweight jobs, and everyday trial use.
Usage-based
Time-based billing
By runtime
How Cloud Task is billed
Pay by runtime as usage grows
You do not need to buy servers or reserve fixed capacity up front. Pay for actual call time only after the included quota runs out, and expand only when demand grows.
Start with the included quota, then scale only when you need to.
Start with published tools, then take the developer path when needed
Use oo-cli to get connected services and published tools working first. When you need to produce, combine, and deliver your own tools, move into Studio and Cloud.