Let your agent install the CLI
Install CLI →Copy the prompt on the right into Codex, Claude Code, or OpenClaw. It will run the official install command for your environment, then handle sign-in and checks.
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.
One connection path for every agent
Connect accounts, apps, and tool capabilities to OOMOL first, then let Codex, Claude Code, OpenClaw, and terminal workflows call them through the same oo-cli path.
Build custom tools in Studio
Explore Studio →When ready-made tools are not enough, use OOMOL Studio to combine third-party tools, cloud functions, and APIs, or build a new tool. Published tools stay available through oo-cli.
# copy the prompt to your agent so it can install and verify$ curl -fsSL https://cli.oomol.com/install.sh | bash# oo-cli is installed in the current environment$ oo login# sign in with your OOMOL account and confirm the CLI is ready$ oo --version# next: search for available tools and start running tasksConnect the tools you love without changing habits
GitHub, Slack, Notion, Gmail, and your own APIs can work together through OOMOL, so agents can help without asking your team to change how they already work.
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.
Deep coverage for common tools
OOMOL comes with support for 273 apps and 3,760 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.
273
appsCovering common services across collaboration, development, marketing, and payments.
3,760
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
When ready-made tools are not enough, use Studio's built-in AI to generate new tools or extend existing ones with workflows, then deliver them to Cloud for oo-cli use.
Developer path 02Run it in Cloud
After validation, run your tool in Cloud
Cloud runs the tool, stores config and secrets, manages access, and tracks usage. You do not need to build a separate backend service for the same tool.
Publish the tool and keep it running
Use the same tool for yourself, your team, or customers without copying and maintaining separate versions.
Manage config, access, and usage in one place
Secrets, permissions, versions, runtime config, and usage logs live in Cloud, making updates and troubleshooting easier.
Start with included usageFree users get 200 Cloud Task minutes each month. You can launch first without 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.
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.