天气 MCP 服务器

Created By
odinggga year ago
weather mcp server with openweather
Overview

what is Weather MCP?

Weather MCP is a Model Context Protocol (MCP) server that utilizes the OpenWeather API to provide weather data and air quality information for any city.

how to use Weather MCP?

To use Weather MCP, clone the repository, connect to the MCP server using a compatible client like Anthropic Claude, and configure it with your OpenWeather API key.

key features of Weather MCP?

  • Detailed weather forecasts for any city (up to 5 days)
  • Current air quality information for any city

use cases of Weather MCP?

  1. Retrieving weather forecasts for travel planning.
  2. Checking air quality for health and safety considerations.
  3. Integrating weather data into applications for enhanced user experience.

FAQ from Weather MCP?

  • What do I need to run Weather MCP?

You need Python 3.11+, an OpenWeather API key, and a compatible MCP client like Claude Desktop.

  • How do I get an OpenWeather API key?

You can obtain an API key by signing up at OpenWeather.

  • Can I use Weather MCP for any city?

Yes! You can get weather and air quality information for any city worldwide.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
odinggg
Star
0
Language
Python
License
MIT 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