One MCP URL for your whole toolset.
Omniio sits between your agent and every MCP server you use. Connect once; switch servers on and off without touching a config file. Your agent searches for tools instead of loading all of them.
36 servers in the library · 6 on by default · 10,000 calls a month on Free
Connect once. Change anything after.
The endpoint never changes, so the client config you write today keeps working as your toolset grows.
Add one URL
Paste the Omniio endpoint into Claude, Cursor, Windsurf or any MCP client. Your client authorizes once, against Omniio.
Switch servers on
Turn servers on in your library. Open servers work immediately; the rest take an API token or an OAuth grant, held per user.
Let the agent search
Instead of hundreds of preloaded tools, your agent gets three: search for a tool, read its schema, run it.
claude mcp add --transport http omniio https://mcp.omniio.dev36 servers, one authorization.
Every server below is in the catalog today. Turn one on and its tools join your endpoint on the next call.
Three tools instead of three hundred.
Loading every tool from every server burns context before your agent has done anything. Omniio exposes a search interface over the catalog instead.
Your agent searches the catalog by intent, reads the schema for the tool it picked, then runs it. Names are namespaced per server, so nothing collides.
How the meta-tools work →API tokens are sealed before storage and OAuth grants are held per user, then refreshed on demand. Every run is recorded with its arguments, result and duration, and kept for 7 days.
How authorization works →Add the URL. Keep your context for the work.
Free covers 10,000 MCP calls a month — enough to run a personal agent all month. No card, and no payment processor to sign up to.