Command-based wrapper
If your MCP client can start the server with a local command, MCP Boundary can usually wrap it. Use command plus args, not an already-hosted remote transport.
Documentation navigation
MCP Boundary docs
Add an MCP server
How MCP Boundary wraps a downstream MCP server started by local command and args.
Client replacement entry
The MCP client should connect to MCP Boundary's generated entry instead of registering the downstream server directly. Do not keep both entries active for the same tool surface.
Environment names
Prefer explicit environment variable names. Avoid servers that write logs to stdout, because stdio transport expects protocol messages on stdout.