🚀 Build Custom MCP Servers 📝☀️📰

Created By
sourangshupala year ago
Overview

What is Build Custom MCP Servers?

Build Custom MCP Servers is a project that demonstrates how to create a simple MCP server using the MCP mcp[cli] Python SDK, providing tools for note management, weather information, and news search.

How to use Build Custom MCP Servers?

To use this project, clone the repository, set up a virtual environment, install dependencies, configure your API keys in the .env file, and run the main script to start the server.

Key features of Build Custom MCP Servers?

  • Note management: Add, read, retrieve the latest, and summarize notes.
  • Fetch current weather data for a specified city.
  • Perform news searches using the Brave Search API.
  • Configuration via a .env file for API keys.

Use cases of Build Custom MCP Servers?

  1. Managing personal notes and summaries.
  2. Accessing real-time weather information.
  3. Searching for news articles based on specific queries.

FAQ from Build Custom MCP Servers?

  • What programming language is used?

The project is built using Python.

  • Do I need to set up API keys?

Yes, you need to configure your API keys in the .env file to access external services.

  • Can I contribute to this project?

Yes, contributions are welcome! You can submit pull requests or open issues.

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

17 hours ago