Point Conduit at your REST API, describe the tools, and get a live MCP endpoint — no new backend, no redeploys when the tool list changes.
Define tools once, clone an existing connector, or build one from scratch.
Name each tool, describe its inputs, and point it at an HTTP endpoint — path, query, and body parameters included.
Your gateway lives at its own slug, backed by Postgres. Credentials stay encrypted, server-side only.
Paste the MCP URL and bearer token into Claude, or any MCP-compatible client, and start calling tools.
Every tool is a name, an input schema, and an HTTP call spec — path, query, and body parameters mapped from a plain field list. No redeploy to add or change a tool.
Start from a public connector with your own credentials, or build one from scratch.
Backend API keys are encrypted at rest and decrypted only server-side, per call.
Each MCP endpoint has its own bearer token — revoke and regenerate independently.
Every account gets its own gateways. Nothing is shared unless you clone it.