Connection types

Broxy connects to downstream MCP servers using transport options shown in the Add/Edit Server screen. In the UI, you choose a value under the "Transport" field.

STDIO

Use "STDIO" for local processes:

• Broxy starts a process and communicates over stdin/stdout.
• Best for tools distributed as local binaries or node packages.
• You provide a command and optional args.

HTTP Streamable

Use "HTTP Streamable" for JSON-only MCP endpoints:

• Best for servers that handle one request per HTTP call.
• You provide a single URL.

HTTP SSE

Use "HTTP SSE" for servers that speak MCP over Server-Sent Events:

• Useful when the server provides a streaming SSE endpoint.
• You provide a single URL.

WebSocket

Use "WebSocket" for servers that speak MCP over WebSockets:

• Useful for bidirectional streaming or long-lived connections.
• You provide a single URL (typically ws:// or wss://).

Authorization

If an HTTP or WebSocket server requires OAuth, Broxy will prompt you to authorize. See OAuth, discovery, and dynamic client registration for the flow and dynamic client registration details.

If you edit configuration files

In mcp.json, the transport values map like this:

• UI "STDIO" -> "stdio"
• UI "HTTP Streamable" -> "http"
• UI "HTTP SSE" -> "sse"
• UI "WebSocket" -> "ws"