Skip to main content

​
Install FastMCP

We recommend using uv to install and manage FastMCP. If you plan to use FastMCP in your project, you can add it as a dependency with:
Alternatively, you can install it directly with pip or uv pip:
FastMCP 3.0 is in development and may include breaking changes. To avoid unexpected issues, pin your dependency to v2: fastmcp<3

​
Verify Installation

To verify that FastMCP is installed correctly, you can run the following command:
You should see output like the following:

​
Dependency Licensing

FastMCP depends on Cyclopts for CLI functionality. Cyclopts v4 includes docutils as a transitive dependency, which has complex licensing that may trigger compliance reviews in some organizations.If this is a concern, you can install Cyclopts v5 alpha which removes this dependency:
Alternatively, wait for the stable v5 release. See this issue for details.

​
Upgrading from the Official MCP SDK

Upgrading from the official MCP SDK’s FastMCP 1.0 to FastMCP 2.0 is generally straightforward. The core server API is highly compatible, and in many cases, changing your import statement from from mcp.server.fastmcp import FastMCP to from fastmcp import FastMCP will be sufficient.
Prior to fastmcp==2.3.0 and mcp==1.8.0, the 2.x API always mirrored the official 1.0 API. However, as the projects diverge, this can not be guaranteed. You may see deprecation warnings if you attempt to use 1.0 APIs in FastMCP 2.x. Please refer to this documentation for details on new capabilities.

​
Versioning Policy

FastMCP follows semantic versioning with pragmatic adaptations for the rapidly evolving MCP ecosystem. Breaking changes may occur in minor versions (e.g., 2.3.x to 2.4.0) when necessary to stay current with the MCP Protocol. For production use, always pin to exact versions:
See the full versioning and release policy for details on our public API, deprecation practices, and breaking change philosophy.

​
Contributing to FastMCP

Interested in contributing to FastMCP? See the Contributing Guide for details on:
  • Setting up your development environment
  • Running tests and pre-commit hooks
  • Submitting issues and pull requests
  • Code standards and review process