Remote MCP server support is currently in beta and available for users on Claude Pro, Max, Team, and Enterprise plans (as of June 2025). Most users will still need to use local STDIO connections.
This guide focuses specifically on using FastMCP servers with Claude Desktop. For general Claude Desktop MCP setup and official examples, see the official Claude Desktop quickstart guide.
Requirements
Claude Desktop traditionally requires MCP servers to run locally using STDIO transport, where your server communicates with Claude through standard input/output rather than HTTP. However, users on certain plans now have access to remote server support as well.Create a Server
The examples in this guide will use the following simple dice-rolling server, saved asserver.py.
server.py
Install the Server
FastMCP CLI
The easiest way to install a FastMCP server in Claude Desktop is using thefastmcp install claude-desktop command. This automatically handles the configuration and dependency management.
file.py:object notation as the run command. If no object is specified, it will automatically look for a FastMCP server object named mcp, server, or app in your file:
Dependencies
FastMCP provides several ways to manage your server’s dependencies when installing in Claude Desktop: If your server declares its dependencies inpyproject.toml, use the --project option to select that Python project.
Individual packages: Use the --with flag to specify packages your server needs. You can use this flag multiple times:
requirements.txt file listing all your dependencies, use --with-requirements to install them all at once:
--with-editable to install them in editable mode:
fastmcp.json configuration file (recommended):
fastmcp.json
Python Version and Project Directory
FastMCP allows you to control the Python environment for your server: Python version: Use--python to specify which Python version your server should run with. This is particularly useful when your server requires a specific Python version:
--project to select the directory containing your MCP server’s pyproject.toml. FastMCP passes this to uv run --project, which discovers the project’s configuration and installs its dependencies into the project environment:
--project selects the Python environment without changing the server’s working directory. If your server reads local files, use absolute paths or resolve them relative to the server file.
Environment Variables
If your server needs environment variables (like API keys), you must include them:.env file:
Manual Configuration
For more control over the configuration, you can manually edit Claude Desktop’s configuration file. You can open the configuration file from Claude’s developer settings, or find it in the following locations:- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
mcpServers key, which contains the configuration for each MCP server.
Dependencies
If your server has dependencies, you can useuv or another package manager to set up the environment.
When manually configuring dependencies, the recommended approach is to use uv with FastMCP. The configuration uses uv run to create an isolated environment with your specified packages:
--python to use a specific Python version, or --project to run within a project directory:
Environment Variables
You can also specify environment variables in the configuration:Remote Servers
Users on Claude Pro, Max, Team, and Enterprise plans have first-class remote server support via integrations. For other users, or as an alternative approach, FastMCP can create a proxy server that forwards requests to a remote HTTP server. You can install the proxy server in Claude Desktop. Create a proxy server that connects to a remote HTTP server:proxy_server.py
Authentication
For authenticated remote servers, create an authenticated client following the guidance in the client auth documentation and pass it to the proxy:auth_proxy_server.py

