This integration focuses on running local FastMCP server files with STDIO transport. For remote servers running with HTTP or SSE transport, use your client's native configuration - FastMCP's integrations focus on simplifying the complex local setup with dependencies and uv commands.
Claude Desktop supports MCP servers through local STDIO connections and remote servers (beta), allowing you to extend Claude’s capabilities with custom tools, resources, and prompts from your FastMCP servers.
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.
If you don’t have access to remote server support or need to connect to remote servers, you can create a proxy server that runs locally via STDIO and forwards requests to remote HTTP servers. See the Proxy Servers section below.

​
Create a Server

The examples in this guide will use the following simple dice-rolling server, saved as server.py.
server.py
import random
from fastmcp import FastMCP

mcp = FastMCP(name="Dice Roller")

@mcp.tool
def roll_dice(n_dice: int) -> list[int]:
    """Roll `n_dice` 6-sided dice and return the results."""
    return [random.randint(1, 6) for _ in range(n_dice)]

if __name__ == "__main__":
    mcp.run()

​
Install the Server

​
FastMCP CLI

New in version: 2.10.3 The easiest way to install a FastMCP server in Claude Desktop is using the fastmcp install claude-desktop command. This automatically handles the configuration and dependency management.
Prior to version 2.10.3, Claude Desktop could be managed by running fastmcp install <path> without specifying the client.
fastmcp install claude-desktop server.py
The install command supports the same 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: 
# These are equivalent if your server object is named 'mcp'
fastmcp install claude-desktop server.py
fastmcp install claude-desktop server.py:mcp

# Use explicit object name if your server has a different name
fastmcp install claude-desktop server.py:my_custom_server
After installation, restart Claude Desktop completely. You should see a hammer icon (🔨) in the bottom left of the input box, indicating that MCP tools are available.

​
Dependencies

FastMCP provides several ways to manage your server’s dependencies when installing in Claude Desktop: Individual packages: Use the --with flag to specify packages your server needs. You can use this flag multiple times: 
fastmcp install claude-desktop server.py --with pandas --with requests
Requirements file: If you have a requirements.txt file listing all your dependencies, use --with-requirements to install them all at once: 
fastmcp install claude-desktop server.py --with-requirements requirements.txt
Editable packages: For local packages in development, use --with-editable to install them in editable mode: 
fastmcp install claude-desktop server.py --with-editable ./my-local-package
Alternatively, you can specify dependencies directly in your server code:
server.py
from fastmcp import FastMCP

mcp = FastMCP(
    name="Dice Roller",
    dependencies=["pandas", "requests"]
)

​
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: 
fastmcp install claude-desktop server.py --python 3.11
Project directory: Use --project to run your server within a specific project directory. This ensures that uv will discover all pyproject.toml, uv.toml, and .python-version files from that project: 
fastmcp install claude-desktop server.py --project /path/to/my-project
When you specify a project directory, all relative paths in your server will be resolved from that directory, and the project’s virtual environment will be used.

​
Environment Variables

Claude Desktop runs servers in a completely isolated environment with no access to your shell environment or locally installed applications. You must explicitly pass any environment variables your server needs.
If your server needs environment variables (like API keys), you must include them: 
fastmcp install claude-desktop server.py --name "Weather Server" \
  --env API_KEY=your-api-key \
  --env DEBUG=true
Or load them from a .env file: 
fastmcp install claude-desktop server.py --name "Weather Server" --env-file .env
  • uv must be installed and available in your system PATH. Claude Desktop runs in its own isolated environment and needs uv to manage dependencies.
  • On macOS, it is recommended to install uv globally with Homebrew so that Claude Desktop will detect it: brew install uv. Installing uv with other methods may not make it accessible to Claude Desktop.

​
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
The configuration file is a JSON object with a mcpServers key, which contains the configuration for each MCP server. 
{
  "mcpServers": {
    "dice-roller": {
      "command": "python",
      "args": ["path/to/your/server.py"]
    }
  }
}
After updating the configuration file, restart Claude Desktop completely. Look for the hammer icon (🔨) to confirm your server is loaded.

​
Dependencies

If your server has dependencies, you can use uv 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: 
{
  "mcpServers": {
    "dice-roller": {
      "command": "uv",
      "args": [
        "run",
        "--with", "fastmcp",
        "--with", "pandas",
        "--with", "requests", 
        "fastmcp",
        "run",
        "path/to/your/server.py"
      ]
    }
  }
}
You can also manually specify Python versions and project directories in your configuration. Add --python to use a specific Python version, or --project to run within a project directory: 
{
  "mcpServers": {
    "dice-roller": {
      "command": "uv",
      "args": [
        "run",
        "--python", "3.11",
        "--project", "/path/to/project",
        "--with", "fastmcp",
        "fastmcp",
        "run",
        "path/to/your/server.py"
      ]
    }
  }
}
The order of arguments matters: Python version and project settings come before package specifications, which come before the actual command to run.
  • uv must be installed and available in your system PATH. Claude Desktop runs in its own isolated environment and needs uv to manage dependencies.
  • On macOS, it is recommended to install uv globally with Homebrew so that Claude Desktop will detect it: brew install uv. Installing uv with other methods may not make it accessible to Claude Desktop.

​
Environment Variables

You can also specify environment variables in the configuration: 
{
  "mcpServers": {
    "weather-server": {
      "command": "python",
      "args": ["path/to/weather_server.py"],
      "env": {
        "API_KEY": "your-api-key",
        "DEBUG": "true"
      }
    }
  }
}
Claude Desktop runs servers in a completely isolated environment with no access to your shell environment or locally installed applications. You must explicitly pass any environment variables your server needs.

​
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
from fastmcp import FastMCP

# Create a proxy to a remote server
proxy = FastMCP.as_proxy(
    "https://example.com/mcp/sse", 
    name="Remote Server Proxy"
)

if __name__ == "__main__":
    proxy.run()  # Runs via STDIO for Claude Desktop

​
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
from fastmcp import FastMCP, Client
from fastmcp.client.auth import BearerAuth

# Create authenticated client
client = Client(
    "https://api.example.com/mcp/sse",
    auth=BearerAuth(token="your-access-token")
)

# Create proxy using the authenticated client
proxy = FastMCP.as_proxy(client, name="Authenticated Proxy")

if __name__ == "__main__":
    proxy.run()