MCP

Created By
Abhinavexistsa year ago
A Simple Implementation of the Model Context Protocol
Overview

What is MCP?

MCP is a simple implementation of a command-line tool that provides access to US weather data through a client-server architecture using the Model Context Protocol (MCP) and Google's Gemini AI.

How to use MCP?

To use MCP, clone the repository, install the necessary dependencies, and run the client to connect to the weather server. You can then query weather information using natural language.

Key features of MCP?

  • Query weather alerts for US states using state codes.
  • Get detailed weather forecasts for specific locations using latitude and longitude.
  • Natural language interface powered by Google's Gemini AI.
  • Client-server architecture using Model Context Protocol (MCP).

Use cases of MCP?

  1. Fetching current weather alerts for specific US states.
  2. Retrieving weather forecasts for specific geographic coordinates.
  3. Utilizing natural language queries to interact with weather data.

FAQ from MCP?

  • What programming languages are used in MCP?

MCP is primarily built using Python.

  • Do I need an API key to use MCP?

Yes, you need a Google Gemini API key to access the natural language features.

  • Is MCP open source?

Yes, MCP is available under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Abhinavexists
Star
4
Language
Python
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours 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