Connect upstream MCP servers with high-level transport helpersThis page is kept for older links. The current concepts entrypoint is Servers and transports.
Quick Start
Usestdio(...) for local upstream MCP servers:
streamableHttp(...) for native remote MCP HTTP endpoints:
Transport Matrix
| Direction | Helper | Use case |
|---|---|---|
| Upstream | stdio(...) | Local MCP process over stdin/stdout. |
| Upstream | streamableHttp(...) | Remote native MCP Streamable HTTP endpoint. |
| Upstream | SseMcpTransport | Legacy SSE-capable MCP servers. |
| Upstream | HttpTransport | Compatibility adapter for REST-like /listTools and /callTool endpoints. |
| Downstream | proxy.start() | Default Streamable HTTP exposure for MCP clients. |
Stdio Options
command
Executable to spawn.
args
Arguments passed to the upstream process.
env
Environment variables passed to the upstream process.
stderr
How to handle stderr from the upstream process. Use inherit during local development to see upstream logs.
HTTP-Family Auth
streamableHttp(...) supports static headers, bearer tokens, API keys, and per-user header resolvers.
Fentaris does not acquire or refresh OAuth tokens. Pass an already-valid access token through a resolver when the upstream needs one.
Close Cleanly
Close the proxy on shutdown so upstream transports can release processes, sockets, and sessions.Low-Level API
Transport classes such asStdioTransport, StreamableHttpMcpTransport, SseMcpTransport, and exposure transports remain available for advanced integrations. New application docs should prefer stdio(...), streamableHttp(...), and proxy.start().