ezmcp

Created By
jujumilk3a year ago
Easy-to-use MCP server framework specialized for SSE.
Overview

what is ezmcp?

ezmcp is an easy-to-use MCP server framework specialized for Server-Sent Events (SSE), designed to simplify the creation of MCP-compatible servers using a FastAPI-like syntax.

how to use ezmcp?

To use ezmcp, install it via pip and create an application using the provided API. Define tools with decorators and run the application to start serving requests.

key features of ezmcp?

  • FastAPI-style decorator API for defining MCP tools
  • Automatic parameter validation and type conversion
  • Automatic generation of tool schemas from function signatures
  • Built-in support for SSE transport
  • FastAPI-style middleware support
  • Easy integration with existing Starlette applications
  • Interactive documentation page for exploring and testing tools

use cases of ezmcp?

  1. Building real-time applications that require server-sent events.
  2. Creating lightweight MCP-compatible servers for various tools.
  3. Integrating with existing FastAPI or Starlette applications.

FAQ from ezmcp?

  • Is ezmcp suitable for production use?

Yes! ezmcp is designed to be lightweight and efficient for production environments.

  • Can I use ezmcp with other frameworks?

Yes! ezmcp can be easily integrated with existing Starlette applications.

  • How do I access the interactive documentation?

Once the server is running, you can access the documentation at http://localhost:8000/docs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jujumilk3
Star
12
Language
Python
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.

7 hours ago