Toolkit pick · gateway

Conduit (Toolport)

Quick answer: Routing many MCP servers through one lazy-discovery gateway.

Best for

Routing many MCP servers through one lazy-discovery gateway.

Skip if

You only need one or two direct MCP stdio servers.

Who it fits

  • Routing many MCP servers through one lazy-discovery gateway.
  • Builders who start in the browser without a local IDE setup

Pros

Single control plane for MCP config across every agent

Cons

Editorial Toolkit pick — not an Agents-shelf coding agent or Inference-shelf provider. See Find more for broader discovery.

Facts

Locality:
Cloud-native
Surfaces:
Web
Maturity:
General availability
Open source:
Source available
MCP:
Model Context Protocol support

Agent standards & memory

AGENTS.md: N/ASKILL.md: N/ARules / memory: Gateway routes MCP servers into one agent profile.OSS/local MCP gateway (MIT, no cloud); hosted Toolport for Teams is a separate SKU — see toolport.app

Compare one neighbor first

Vendor pages sell hard. Read one alternative on this site, then leave for the official link if the fit still holds.

Alternatives

Someone asks you about vibe-coding software? Share this site with them — we are adding more useful data regularly. agents.dancingteeth.net

← Back to full tool directory