Skip to main content
fastmcp-remote is FastMCP’s standalone stdio bridge for remote MCP servers. Use it when an MCP host expects to launch a local command, but the server you want to use is hosted over Streamable HTTP or SSE.
The package is powered by FastMCP. It builds one FastMCP client for the remote URL, exposes that client as a local stdio proxy, and keeps the executable focused on that bridge. For running Python server files, local project environments, FastMCP config files, and development reload loops, use fastmcp run. The command shape follows the original mcp-remote npm project, which established this stdio-to-remote bridge pattern for MCP hosts.

​
Installation

Most MCP hosts can run fastmcp-remote directly through uvx, so you usually do not need to install it yourself:
If your host requires an already-installed command, install the package with your Python package manager:

​
Host Configuration

For hosts that use mcpServers JSON configuration, set the command to uvx and pass fastmcp-remote plus the remote server URL as arguments:

​
Endpoint URLs and Connection Status

Pass the full MCP endpoint URL for the remote server. Many FastMCP HTTP servers expose MCP at /mcp, so a local development server may need http://localhost:8000/mcp rather than http://localhost:8000. fastmcp-remote starts a local stdio bridge, then connects to the upstream server when the MCP host initializes that bridge. If the upstream server is unavailable, the URL does not point to an MCP endpoint, or authentication cannot complete, initialization fails and the host should report the remote server as failed. After initialization succeeds, later tool, resource, prompt, and ping requests continue to proxy through the same remote server configuration. OAuth is enabled automatically for HTTPS servers. The first connection opens the browser-based OAuth flow when the server requires authentication, then stores tokens locally for future runs. To pass a bearer token or another custom header directly, provide --header in Name: Value form. The header name ends at the first colon, so values can contain additional colons. Quote the header when the value contains spaces, just like any other shell argument. An Authorization header disables OAuth by default:
Repeat --header to send multiple headers:
Some MCP hosts on Windows have trouble preserving spaces inside command arguments. Put the spaced value in an environment variable and reference it from the header value:
For local development servers over plain HTTP, disable OAuth when the server is unauthenticated:

​
Self-Signed Certificates

For servers behind a self-signed certificate, point --verify at a CA bundle that trusts the certificate:
To disable certificate verification entirely, pass --verify false. This is insecure and should only be used for trusted servers on private networks:
To trust a CA bundle without a flag, set the standard SSL_CERT_FILE environment variable, which OpenSSL reads automatically:

​
OAuth Storage

OAuth tokens are stored under ~/.fastmcp/remote by default. Set FASTMCP_REMOTE_CONFIG_DIR to use another directory:
Use --resource to isolate tokens for a particular remote server identity:
If the remote authorization server requires a fixed callback port or hostname, pass them after the URL:

​
Options