Back to MCP directory
publicPublicdnsLocal runtime

fastmcp

FastMCP v2 是一个用于快速构建 MCP(模型上下文协议)服务器和客户端的 Python 框架。它通过简洁、Pythonic 的代码简化了 MCP 服务器的开发,支持工具、资源、提示等核心功能,并提供了客户端库、服务器代理、OpenAPI/FastAPI 集成等高级特性。FastMCP 2.0 扩展了 1.0 的基本功能,使其成为现代 AI 应用的完整工具包,适合开发者快速构建和部署 MCP 服务器。

article

README

FastMCP Logo

FastMCP 🚀

Move fast and make things.

Made with 💙 by Prefect

Docs Discord PyPI - Version Tests License

jlowin%2Ffastmcp | Trendshift


The Model Context Protocol (MCP) provides a standardized way to connect AI agents to tools and data. FastMCP makes it easy to build MCP applications with clean, Pythonic code:

from fastmcp import FastMCP

mcp = FastMCP("Demo 🚀")

@mcp.tool
def add(a: int, b: int) -> int:
    """Add two numbers"""
    return a + b

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

Why FastMCP

MCP lets you give agents access to your tools and data. But building an effective MCP server is harder than it looks.

Give your agent too much—hundreds of tools, verbose responses—and it gets overwhelmed. Give it too little and it can't do its job. The protocol itself is complex, with layers of serialization, validation, and error handling that have nothing to do with your business logic. And the spec keeps evolving; what worked last month might already need updating.

The real challenge isn't implementing the protocol. It's delivering the right information at the right time.

That's the problem FastMCP solves—and why it's become the standard. FastMCP 1.0 was incorporated into the official MCP SDK in 2024. Today, the actively maintained standalone project is downloaded a million times a day, and some version of FastMCP powers 70% of MCP servers across all languages.

The framework is built on three abstractions that map to the decisions you actually need to make:

  • Components are what you expose: tools, resources, and prompts. Wrap a Python function, and FastMCP handles the schema, validation, and docs.
  • Providers are where components come from: decorated functions, files on disk, OpenAPI specs, remote servers—your logic can live anywhere.
  • Transforms shape what clients see: namespacing, filtering, authorization, versioning. The same server can present differently to different users.

These compose cleanly, so complex patterns don't require complex code. And because FastMCP is opinionated about the details, like serialization, error handling, and protocol compliance, best practices are the path of least resistance. You focus on your logic; the MCP part just works.

Move fast and make things.

Installation

[!Note] FastMCP 3.0 is currently in beta. Install with: pip install fastmcp==3.0.0b1

For production systems requiring stability, pin to v2: pip install 'fastmcp<3'

We recommend installing FastMCP with uv:

uv pip install fastmcp

For full installation instructions, including verification and upgrading, see the Installation Guide.

📚 Documentation

FastMCP's complete documentation is available at gofastmcp.com, including detailed guides, API references, and advanced patterns.

Documentation is also available in llms.txt format, which is a simple markdown standard that LLMs can consume easily:

  • llms.txt is essentially a sitemap, listing all the pages in the documentation.
  • llms-full.txt contains the entire documentation. Note this may exceed the context window of your LLM.

Community: Join our Discord server to connect with other FastMCP developers and share what you're building.

Contributing

We welcome contributions! See the Contributing Guide for setup instructions, testing requirements, and PR guidelines.

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client