Works best with
Local command-based MCP servers using stdio transport, started with command plus args, and supporting initialize and tools/list.
Documentation navigation
MCP Boundary docs
Compatibility
What works best today, what needs care, and what is outside the first public release scope.
Needs separate support
Remote OAuth-heavy servers, servers requiring interactive login during startup, non-standard transports, and servers that only run inside one specific client.
Plain-language rule
If your MCP client can start the server with a local command, MCP Boundary can usually wrap it. Remote and login-heavy servers need separate support.