Fastapi Mcp Server

Created By
NishizukaKoichia year ago
FastAPI MCP Server は、FastAPI を用いた MCP (Model Context Protocol) サーバーです。 このプロジェクトは、各種ツールやデータソースへのアクセスを統一的に実現することを目指します。
Overview

what is FastAPI MCP Server?

FastAPI MCP Server is a server built using FastAPI that implements the Model Context Protocol (MCP). This project aims to provide a unified access point to various tools and data sources.

how to use FastAPI MCP Server?

To use the FastAPI MCP Server, clone the repository, set up a virtual environment, install the dependencies, and start the server using the provided command. Access the API documentation via your browser at http://localhost:8000/docs.

key features of FastAPI MCP Server?

  • FastAPI-based: Provides fast and simple API endpoints.
  • MCP protocol implementation: Offers a unified interface for tool calls using JSON-RPC.
  • Unified access: Enables consistent access to various tools and data sources.

use cases of FastAPI MCP Server?

  1. Integrating AI assistants like Claude Code with various tools.
  2. Providing a backend for applications that require access to multiple data sources.
  3. Simplifying the development of applications that need to interact with different APIs.

FAQ from FastAPI MCP Server?

  • What is the MCP protocol?

The Model Context Protocol (MCP) is a protocol designed to provide a unified interface for accessing various tools and data sources.

  • How do I install FastAPI MCP Server?

Follow the installation instructions in the documentation, which include cloning the repository and installing dependencies.

  • Is FastAPI MCP Server open source?

Yes, FastAPI MCP Server is open source and licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NishizukaKoichi
Star
0
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)

2 days ago
Voyei

4 hours ago