157
appsCovering common services across collaboration, development, marketing, and payments.
Your agent does the thinking and decision-making. Leave the rest to OOMOL.
Start with oo-cli so agents can connect to ready-made tools, APIs, and internal capabilities and get work moving. When those stop short, move into Studio and Cloud.
Start with how many apps are already connected
OOMOL comes with support for 157 apps and 2,485 wrapped tools. Start by using what already exists through oo-cli, then decide what is worth orchestrating further, extending, or turning into your own tool.
2,485
wrapped toolsPackaged as usable capability entry points instead of raw integration fragments.
Common apps are already available
GitHub
Slack
Notion
Gmail
Linear
Vercel
Supabase
Twilio
Step 1: Use what already exists
Let agents run ready-made work first
If a ready-made tool already solves the job, OOMOL's first layer of value is simple: connect it, run it, and do not start by building your own tool.
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.
Agent will run
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.
Agent will run
Extract requirements, shape tasks, and write them back to Linear.
GmailYour API
Read a Gmail attachment, then call an internal 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.
Agent will run
Download the attachment, call your internal API, and return the output.
Developer entry
When ready-made capabilities stop short, move into OOMOL Studio
In Studio, you can recombine ready-made capabilities, add code, orchestrate workflows, and write new function tools. Once the tool works locally, hand it to Cloud for delivery.
Turn ready-made capabilities into your own tool
Take GitHub, Slack, Notion, Gmail, and other built-in capabilities 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 stop short, write new function tools and bring in your own APIs, internal 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.
01 / Build in Studio
Start in OOMOL Studio to generate, compose, and validate
Use the agent to get started, then keep editing code, dependencies, parameters, and compositions yourself. Studio is for building tools, not for day-to-day tool usage.
Studio demo video
Show the path from prompting to generating a tool and validating it locally.
02 / Deliver through Cloud
Once validation is done, hand delivery and runtime to Cloud
Cloud takes over runtime, configuration, secrets, access, and delivery relationships so you do not need to build another backend around the same implementation.
Handle delivery and hosted runtime in one path
Keep the same implementation as you deliver the tool to yourself, your team, or customers.
Keep config, access, and usage relationships in one backend
Manage secrets, access, releases, runtime settings, and usage data in one place.
Cloud console preview
Bring runtime settings, secrets, and delivery relationships into one backend.
03 / Use from oo-cli
Finally, hand the tool back to oo-cli for agents to use
Once the tool is built and delivered, Agents, Codex, OpenClaw, and Claude Code keep using the same oo-cli path to search, inspect, and call it.
oo-cli invocation demo
Show a delivered tool being searched, inspected, and called in Codex.
GUI extension for oo-cli
The same capability layer also works through OOMOL AI
Once you already understand the oo-cli path, OOMOL AI gives you the official GUI for the same capability layer when you want a visual interface across web, desktop, and iOS.
WebDesktopiOS
Free Tier
Start delivery with the 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
Monthly Included
200 Minutes
Free Cloud Task time
Deliver the tool and start using it
Use the monthly refreshed quota to deliver the tool and confirm it stays searchable and callable in oo-cli.
A good fit for first delivery, lightweight jobs, and everyday trial use.
Usage-based
Time-based billing
By Time
How Cloud Task is billed
Scale with call-duration billing
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 using it first, then decide the scale.
Start with ready-made tools, then take the developer path when needed
Use oo-cli to get ready-made capabilities working first. When you need to produce, combine, and deliver your own tools, move into Studio and Cloud.