FastAPI MCP SSE

Created By
panz2018a year ago
A working example to create a FastAPI server with SSE-based MCP support
Overview

What is FastAPI MCP SSE?

FastAPI MCP SSE is a project that demonstrates how to create a FastAPI server with Server-Sent Events (SSE) support, integrating the Model Context Protocol (MCP) for enhanced AI model interactions.

How to use FastAPI MCP SSE?

To use this project, you can either run it directly without installation using UV's execution tool or set up a virtual environment and install the required dependencies. After starting the server, you can access various endpoints for both standard web routes and MCP SSE functionality.

Key features of FastAPI MCP SSE?

  • Implementation of Server-Sent Events (SSE) with MCP integration.
  • Customizable route structure within a FastAPI application.
  • Unified web application with both MCP and standard web endpoints.
  • Clean separation of concerns between MCP functionality and web routes.

Use cases of FastAPI MCP SSE?

  1. Real-time data streaming for AI applications.
  2. Integration of external tools and APIs with AI models.
  3. Development of modular web applications using FastAPI.

FAQ from FastAPI MCP SSE?

  • What is the Model Context Protocol (MCP)?

MCP is an open standard that allows AI models to interact with external tools and data sources, addressing context limitations and enabling tool integration.

  • How can I run the application?

You can run it directly using UV's execution tool or set up a virtual environment and install dependencies.

  • What endpoints are available?

The application provides standard web routes and MCP SSE endpoints, including /sse for SSE functionality.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
panz2018
Star
4
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago