Simple MCP Server

Created By
rjmoggacha year ago
A basic stdio & streamable http implementation of FastMCP Server
Overview

What is Simple MCP Server?

Simple MCP Server is a minimal implementation of the Model Context Protocol (MCP) server using FastMCP, designed to connect AI systems with external tools and data sources.

How to use Simple MCP Server?

To use the Simple MCP Server, clone the repository, install the dependencies, and run the server in one of three modes: both transports, HTTP transport only, or stdio transport only.

Key features of Simple MCP Server?

  • Dual transport support (HTTP and stdio)
  • Simple authentication middleware for HTTP transport
  • Example tools implementation
  • Compatible with MCP clients like Windsurf IDE and Claude

Use cases of Simple MCP Server?

  1. Connecting AI systems to external tools and data sources.
  2. Providing a simple interface for AI clients to interact with.
  3. Demonstrating the capabilities of the Model Context Protocol.

FAQ from Simple MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standard that connects LLMs with external tools and data sources.

  • What are the prerequisites for running the server?

You need Python 3.11+ and the FastMCP library.

  • How can I extend the server with my own tools?

Modify the create_mcp_server() function in run_server.py to add custom tools.

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

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago