One local gateway for all your MCP servers, set up once and shared by every AI client (Claude, Cursor, VS Code, Codex...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Claude
Fastest way to find out if conduit belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add conduit -- npx conduitRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove conduitNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ conduit ← registers here
One local gateway for all your MCP servers, set up once and shared by every AI client (Claude, Cursor, VS Code, Codex). Lazy discovery collapses them to 3 meta-tools the agent searches on demand, ~90% fewer tokens. Keys in your OS keychain, no cloud.
Source: GitHub repository
Source check: No source check recorded
Upstream commit: July 2, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.