Conduit
@tsouth89
Conduit is a local-first gateway that puts every MCP server behind one endpoint shared by all your AI coding tools (Claude, Cursor, VS Code, Codex, and more). Set up and authenticate each server once, then connect every client to Conduit instead of re-adding servers everywhere. K
概要
What is Conduit?
Conduit is a local MCP (Model Context Protocol) gateway and manager. You set up and authenticate each MCP server once in Conduit, point your AI agents at the single Conduit gateway, and every server is instantly available in all of them. It is built for people who use more than one AI coding tool and are tired of managing MCP servers per app.
How to use Conduit?
Install the desktop app from the Releases page (Windows and macOS, Linux in beta). In the app, add and authenticate MCP servers, create profiles, and connect AI clients. Each client launches the gateway binary (conduit-gateway) over stdio, which reads Conduit's registry and routes tool calls to downstream servers.
Key features of Conduit
- Set up once, use across every AI client
- Lazy discovery keeps context flat with three meta-tools
- Per-agent scoping limits servers per client
- OAuth and API key auth stored in OS keychain
- Curated catalog and MCP Registry search
- No secrets in client configuration files
- Governance with per-tool toggles and audit log
- Full MCP support: tools, resources, and prompts
Use cases of Conduit
- Manage multiple MCP servers across Cursor, Claude, Codex, and more from one place
- Give each AI agent only the servers it should access
- Test tools in the built-in playground before connecting a client
- Keep agent context small while having many servers available
FAQ from Conduit
What clients does Conduit support?
Cursor, Claude Desktop, Claude Code, Codex, Google Antigravity, VS Code, Windsurf, Gemini CLI, Cline, and Roo Code. Conduit detects each one, installs the gateway with one click, and can import a client's existing servers.
How does lazy discovery work?
The gateway advertises three meta-tools (conduit_status, conduit_search_tools, conduit_call_tool) instead of the full catalog. The agent searches and calls on demand, keeping context flat regardless of how many servers are connected.
What are the runtime requirements?
Conduit runs on Windows and macOS (the macOS build is signed and notarized), with Linux (.deb and AppImage) in beta. The gateway binary spawns over stdio from AI clients.
Where are credentials stored?
Secrets live in the OS keychain (macOS Keychain, freedesktop Secret Service on Linux) and are injected at runtime. Client configs only point to Conduit and contain no secrets.
How do I handle OAuth on macOS?
The OAuth flow redirects to a local http://127.0.0.1 callback. Safari can silently block that redirect, so set Chrome or Brave as your default browser, or paste an access token instead.
