Relvo is an MCP server for Codex. Connect it once and Codex can search the Relvo catalog and call 140,000+ tools across 50+ providers, with the price shown before each run.
Ask for the job in plain language. Codex searches the whole catalog, shows the price, and calls the platform that fits — 50+ platforms behind one key.
Two ways in: the automatic route is a link or one instruction, and the manual route is done by hand. Both reach the same MCP endpoint with the same OAuth sign-in.
One command adds the server.
Codex keeps its MCP servers in ~/.codex/config.toml — shared by the CLI, the desktop app and the IDE extension — and this command writes the entry for you.
codex mcp add relvo --url https://app.relvo.si/mcpCodex lists Relvo among its MCP servers and marks it as needing OAuth. Select Authenticate and approve Relvo in the browser; no token is written to the file.
The same entry, written by hand.
Use this to keep the server in a project's .codex/config.toml or to review the change before it lands.
Open ~/.codex/config.toml, or .codex/config.toml inside a trusted project.
[mcp_servers.relvo]
url = "https://app.relvo.si/mcp"Restart Codex, choose Authenticate next to Relvo, and approve it in the browser. The Relvo tools appear in the MCP server list.
One access layer in front of the provider's own API — priced per call, with the provider's response passed back as it is.
The same token calls every platform in the catalog.
Relvo's published rate, shown before the call.
Eligible tools run on Relvo's key.
Register a provider key and Relvo uses it instead.
Pick the client you already use. Every one reaches the same catalog through one Relvo key.
Real jobs teams run through the same catalog and the same key, priced per call.
Short answers about the key, the price and the call itself.
One token, one prepaid balance, no provider signup. Start free.
