Convex
Set up and scale Convex apps with the team's own runbooks and scaling guidance. No key required.
What Convex exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the convex__ namespace. Your agent never loads them all — it searches, and gets the few that match.
convex__add_convex_to_existing_project4 arguments · 1 required
CALL THIS FIRST when adding Convex (or any backend: database, server functions, auth, realtime, file storage, scheduled jobs) to an EXISTING JavaScript or TypeScript project, before editing files. Returns concrete install/init commands, framework-specific Convex React provider wiring, repo checks, and auth/setup notes — the correct wiring that hand-rolling usually gets wrong. Guidance only (it does not touch the repo), so call it first, then follow its steps.
Required
frameworkconvex__get_convex_scaling_guidance2 arguments
Return Convex scaling guidance for indexes, pagination, large tables, realtime queries, actions, workflows, storage, and multi-tenant apps. Use when the user asks how to scale a Convex app, avoid performance pitfalls, or review a Convex architecture. The tool returns guidance only and does not inspect live deployments or logs.
convex__get_runbook1 argument
Fetch the full Convex quickstart runbook — the authoritative, end-to-end playbook for building a Convex app (scaffold → install → start the backend → schema → functions → client wiring → run → verify). `start_convex_app` tells you to call this; do it, and follow the runbook in order. It carries load-bearing rules your training data may get wrong: how to start `npx convex dev` without hanging, when to use a cloud vs. anonymous-local deployment (prefer cloud whenever the user is signed in), Convex Auth/JWT setup, and which components to use instead of hand-rolling. Pass `section` to fetch a single heading; omit it for the whole runbook.
convex__start_convex_app3 arguments · 1 required
CALL THIS FIRST — before writing any files — whenever the user asks to build, scaffold, create, or start a new app, prototype, or backend and Convex is in play (they mentioned Convex, invoked the Convex tool/app, or want a reactive/full-stack TS/JS backend). Returns the exact `npm create convex@latest` scaffold command, a derived app slug, harness-specific notes, and the next step: call `get_runbook`. Skipping this and hand-rolling a Convex app is the most common mistake — it leads to anonymous throwaway backends, missing auth/JWT setup, and re-implemented components. This tool only returns guidance (it does not run commands), so calling it is cheap and safe; always start here.
Required
idea
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Convex is already on
It needs no credential, so it is on for every account from the first call.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
