MCP Server Template (Python)

Created By
Nisarg38a year ago
Overview

what is MCP Server Template?

MCP Server Template is a ready-to-use template for building Model Context Protocol (MCP) servers in Python, designed to help developers quickly create servers that can register and expose tools and prompts for AI models to use.

how to use MCP Server Template?

To use the MCP Server Template, clone the repository, install the package in development mode, and run the server using Python or the command line interface (CLI).

key features of MCP Server Template?

  • Quick setup for MCP servers in Python
  • Command line options for customization
  • Easy addition of tools and prompts for AI models
  • Support for Docker and cloud deployment

use cases of MCP Server Template?

  1. Building custom AI tools for specific applications.
  2. Creating interactive AI-driven applications.
  3. Deploying AI models in cloud environments.

FAQ from MCP Server Template?

  • What is the minimum Python version required?

Python 3.10 or newer is required.

  • Can I deploy the server using Docker?

Yes! The template includes instructions for Docker deployment.

  • How can I add my own tools?

You can add tools by editing the src/main.py file and using the @mcp.tool() decorator.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Nisarg38
Star
1
Language
Python
License
-

Recommend Servers

View All
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.

8 hours ago