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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago