🧠 Servidor MCP com Python – Tutorial Prático

Created By
ryanbritoa year ago
Overview

What is MCP-Server-Example?

MCP-Server-Example is a practical tutorial repository that demonstrates how to create a Model Context Protocol (MCP) server using Microsoft's official SDK in Python.

How to use MCP-Server-Example?

To use this project, set up a virtual environment, install the necessary packages, and run the server using the provided commands. You can also integrate it with tools like Open WebUI.

Key features of MCP-Server-Example?

  • Demonstrates the creation of an MCP server in Python.
  • Provides example code for defining tools that can be consumed by LLMs.
  • Supports local execution and HTTP mode for API integration.

Use cases of MCP-Server-Example?

  1. Building a custom server for LLMs using the MCP protocol.
  2. Integrating with Open WebUI for enhanced functionality.
  3. Learning how to implement server-side tools in Python.

FAQ from MCP-Server-Example?

  • What technologies are used in this project?

The project uses Python 3.10+, uv for environment management, and the MCP SDK.

  • How can I run the server?

You can run the server in local mode or HTTP mode using the provided commands in the tutorial.

  • Can I contribute to this project?

Yes! Contributions are welcome, and you can suggest new tools or improvements.

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

a day ago