112
appsCovering common services across collaboration, development, marketing, and payments.
One CLI lets agents use the apps you already use
Let Codex, OpenClaw, Claude Code, and other agents use your apps, APIs, and internal tools. Then use OOMOL Studio to compose and extend your own tools.
Start with how many apps are already built in
OOMOL comes with support for 112 apps and 2,101 wrapped tools. Start with what already exists, then decide where deeper orchestration or extension is worth it.
2,101
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
A few typical scenarios
From engineering collaboration to document flows to email plus internal APIs, start by letting agents run common work that already exists.
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.
Advanced extension
When ready-made scenarios are not enough, continue in OOMOL Studio
When you need to recombine existing connections, orchestrate multi-step workflows, or build brand-new function tools, extend the same path in OOMOL Studio.
Recombine built-in connections
Take GitHub, Slack, Notion, Gmail, and other ready-made capabilities and rearrange them into your own execution chain.
Orchestrate more complex workflows
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.
Bring those capabilities back into oo-cli
New workflows and tools do not become a parallel product. They extend the same CLI path your agents already use.
Start in oo-cli. Build your own only when ready-made tools stop short
Get one tool working first. When ready-made tools are not enough, build your own in Studio, then hand it to Cloud when it needs to keep running and be delivered.
Install oo-cli and let agents call apps and tools
In Codex, OpenClaw, Claude Code, and terminal workflows, start by searching, inspecting, and running published tools to get the usage path working.
Agent demo video
Show installing, searching, inspecting, and running a tool in Codex.
When ready-made tools are not enough, build your own in OOMOL Studio
Tell the agent what you want, then keep editing code, dependencies, parameters, and compositions yourself. Studio does not replace engineering workflow; it helps you create new tools faster and validate them locally.
Studio demo video
Show the path from prompting to generating a tool and validating it locally.
When it needs to keep running and be delivered, Cloud takes over
After local validation is done, Cloud handles runtime, configuration, secrets, and delivery relationships. You do not need to rebuild another delivery layer around the same implementation.
Handle runtime and delivery in one path
Keep the same implementation as you deliver the tool to yourself, your team, or customers.
Keep configuration 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.
Start with ready-made tools, build your own only when needed
Use oo-cli to get ready-made tools working first. When you need custom ones, move into Studio and Cloud to compose, extend, and deliver your own tools.