freshcrate
Home > MCP Servers > fastmcp

fastmcp

🚀 The fast, Pythonic way to build MCP servers and clients.

Description

🚀 The fast, Pythonic way to build MCP servers and clients.

README

FastMCP Logo

FastMCP 🚀

Move fast and make things.

Made with 💙 by Prefect

Docs Discord PyPI - Version Tests License

prefecthq%2Ffastmcp | Trendshift


The Model Context Protocol (MCP) connects LLMs to tools and data. FastMCP gives you everything you need to go from prototype to production:

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

Building an effective MCP application is harder than it looks. FastMCP handles all of it. Declare a tool with a Python function, and the schema, validation, and documentation are generated automatically. Connect to a server with a URL, and transport negotiation, authentication, and protocol lifecycle are managed for you. You focus on your logic, and the MCP part just works: with FastMCP, best practices are built in.

That's why FastMCP is the standard framework for working with MCP. FastMCP 1.0 was incorporated into the official MCP Python 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.

FastMCP has three pillars:

Servers
Servers

Expose tools, resources, and prompts to LLMs.
Apps
Apps

Give your tools interactive UIs rendered directly in the conversation.
Clients
Clients

Connect to any MCP server — local or remote, programmatic or CLI.

Servers wrap your Python functions into MCP-compliant tools, resources, and prompts. Clients connect to any server with full protocol support. And Apps give your tools interactive UIs rendered directly in the conversation.

Ready to build? Start with the installation guide or jump straight to the quickstart. When you're ready to deploy, Prefect Horizon offers free hosting for FastMCP users.

Installation

We recommend installing FastMCP with uv:

uv pip install fastmcp

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

Upgrading? We have guides for:

📚 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.

Release History

VersionChangesUrgencyDate
v3.2.4A grab bag of fixes, hardening, and polish. The headline behavior change: background tasks are now scoped to the authorization context rather than the MCP session, so a task kicked off by an authenticated user survives session churn and stays tied to who started it. This is a breaking change for anyone relying on the old session-scoped semantics. Security got three meaningful upgrades. `FileUpload` now validates actual decoded base64 size instead of trusting the client-reported number, so an aHigh4/14/2026
v3.2.3fakeredis 2.35.0 shipped an undocumented rename (`FakeConnection` → `FakeAsyncRedisConnection`) that broke pydocket's `memory://` backend, causing `fastmcp[tasks]` installs to fail at startup with an `ImportError`. This pins `fakeredis<2.35.0` in the `tasks` extra as a stopgap until a fixed pydocket ships. <!-- Release notes generated using configuration in .github/release.yml at main --> ## What's Changed ### Fixes 🐞 * Pin fakeredis<2.35.0 in tasks extra by @jlowin in https://github.com/PreHigh4/9/2026
v3.2.1Most of the fixes in this patch are about auth providers getting audience validation wrong. Cognito token verification was checking the `aud` JWT claim, but Cognito access tokens don't include one; they use `client_id` instead. Azure was hardcoding the raw client ID as the expected audience, ignoring the `identifier_uri` parameter even though Entra v2.0 tokens use the Application ID URI as `aud`. Both now validate correctly without changing the provider API. Consent cookies also had an unboundedHigh4/8/2026

Dependencies & License Audit

Loading dependencies...

Similar Packages

mcpOfficial MCP Servers for AWS2026.04.20260414152327
comfy-pilot🤖 Create and modify workflows effortlessly with ComfyUI's AI assistant, enabling natural conversations with agents like Claude and Gemini.main@2026-04-21
n8n-oracle-cloud-selfhost🚀 Host n8n on Oracle Cloud Free Tier using Docker, secure it with Nginx and HTTPS, and connect via a custom domain with this straightforward guide.main@2026-04-21
scraper-mcp🌐 Streamline web scraping with Scraper MCP, a server that optimizes content for AI by filtering data and reducing token usage for LLMs.main@2026-04-21
agentic-codingAgentic Coding Rules, Templates etc...main@2026-04-21