Your clients hold one URL. Behind it, Omniio decides which tools a person can reach, which calls may run, and writes down every one of them — across 145 servers and the ones you bring yourself.
6 servers on the moment you sign up · 25,000 calls a month on Free · no card to start
Connecting agents to tools one server at a time works until the third server. After that, three costs compound — and all three have the same fix.
Every server is another block of JSON, on every laptop and in every CI runner. Adding one means a pull request; removing one means finding all the copies.
Tokens end up in shell profiles and config files, one per person per server, with nothing that says which are still in use or when they were last rotated.
Each upstream keeps its own log, in its own format, if it keeps one at all. Nothing answers the question people actually ask: what did my agent change, and when.
{ "mcpServers": { "postman": { "type": "http", "url": "https://mcp.postman.example/mcp", "headers": { "Authorization": "Bearer ${TOKEN}" } }, "resend": { "type": "http", "url": "https://mcp.resend.example/mcp", "headers": { "Authorization": "Bearer ${TOKEN}" } }, "make": { "type": "http", "url": "https://mcp.make.example/mcp", "headers": { "Authorization": "Bearer ${TOKEN}" } }, "close": { "type": "http", "url": "https://mcp.close.example/mcp", "headers": { "Authorization": "Bearer ${TOKEN}" } } }}…and one more block for every server after these, kept in step across every laptop and runner that runs an agent.
{ "mcpServers": { "omniio": { "type": "http", "url": "https://mcp.omniio.dev" } }}The rest is a toggle in your library. The config a client wrote on day one keeps working as the toolset changes underneath it.
Not an illustration of the pipeline — it is the pipeline, in the order the endpoint runs it. Step along it, or let it run.
An unauthorized request is answered with a 401 and a WWW-Authenticate header pointing at the authorization server, which is how an MCP client knows to start the flow. It registers itself dynamically, gets a token bound to this endpoint, and that token is what every later call carries.
Wiring servers into a client config gives you no control layer at all. A single vendor’s hosted MCP server gives you control over their product and nothing else.
| Capability | Servers in a client config | One vendor's MCP server | Omniio |
|---|---|---|---|
| Client setup | One config block per server, per machine | One URL, for that vendor's tools only | One URL, for everything |
| Adding a server | Edit and redistribute the config | Wait for the vendor to add it | A toggle; live on the next call |
| Tool discovery | Every tool preloaded into context | Every tool preloaded into context | Searched, three tools exposed |
| Credentials | Env vars and config files on each machine | Held by the vendor, for their own APIs | Sealed per person, unsealed per call |
| Control before a write | None | Whatever that vendor offers | Allow, ask or block, per tool |
| Audit trail | Whatever each upstream keeps | That vendor's actions only | One log across every server |
| Changing model | Reconfigure every machine | Reconnect, per person | Nothing to change; the URL is the same |
Everything below is in the product today, and every card links to the page that documents it rather than to a form.
The same endpoint serves curated agent skills — other people's published procedures, carried at a pinned commit under their own licences. Your agent reads one when the task calls for it, over the connection it already has.
Browse the skill librarySAML or OIDC single sign-on, and SCIM 2.0 so joiners and leavers in your directory become Omniio accounts and closed ones without anybody filing a ticket.
How SSO and SCIM workTool policy is set per account and enforced at the endpoint, so it holds whichever client, model or harness is asking — including ones that did not exist when you wrote it.
How tool policy worksSpans are emitted over OTLP to whatever collector you use, so gateway latency shows up beside the rest of your traces rather than in a dashboard nobody opens.
How tracing worksRecords are kept for 7 days on Free and up to 1 year on Enterprise, pruned nightly, and readable over the REST API for as long as they are held.
Read API referenceA layer between your agents and the MCP servers they call. Instead of each client holding its own list of servers and its own credentials, the clients hold one URL, and the gateway decides which tools that person can see, which calls may run, and what gets written down.
An MCP server exposes one product’s tools. Omniio is a client of many of those servers and a server to your agent, which is what lets it rank across all of them at once and hold one credential set per person rather than per machine.
It adds one hop. The upstream request is wrapped in its own span nested under the run, so the difference between the two is Omniio’s own overhead — gating, credential decryption, the catalog lookup — and you can see it separately from the upstream’s time in your own tracing.
Yes. Add your own MCP server URL from the dashboard and it joins your endpoint alongside the curated ones, with the same search, the same policy and the same audit trail. Servers you add are yours — they never appear in the public library.
Every tool definition is hashed — name, title, description and input schema — so a description that quietly grows a line of instructions to the model is detectable rather than invisible. Changes are listed in the dashboard and can be sent to a webhook.
Any client that speaks MCP over streamable HTTP with OAuth. That includes Claude Code, the Claude desktop app, Cursor, VS Code and Windsurf; the exact snippet for each is on the clients page.
It passes through, and the call is recorded — arguments and result — so the audit trail can answer what the agent did. That record is yours, kept for your plan’s retention window and then deleted by the nightly prune. What is held and for how long is set out in security.
145 servers and 2,251 cached tools in the catalog right now, served from mcp.omniio.dev.
Free covers 25,000 calls a month, which is a personal agent running all month. Nothing to install and no contract.