Weather Forecast MCP Server

Created By
shibing624a year ago
weather-forecast-server, MCP server, without api key, free. Get weather for cities around the world.
Overview

What is Weather Forecast MCP Server?

Weather Forecast MCP Server is a Model Context Protocol (MCP) server that allows users to retrieve weather information for cities around the world without needing an API key.

How to use Weather Forecast MCP Server?

To use the server, you can install it via pip or from the source. After installation, you can run it as a standalone server or integrate it with MCP client applications.

Key features of Weather Forecast MCP Server?

  • Retrieve current weather conditions for any location.
  • Access multi-day weather forecasts (up to 3 days).
  • Support for multiple languages including Chinese and English.
  • Easy integration with various MCP client applications.

Use cases of Weather Forecast MCP Server?

  1. Providing real-time weather updates for applications.
  2. Integrating weather data into chatbots or virtual assistants.
  3. Offering weather forecasts for travel planning applications.

FAQ from Weather Forecast MCP Server?

  • Do I need an API key to use the server?

No, the server can be used without an API key.

  • How can I install the server?

You can install it using pip with the command pip install weather-forecast-server or clone the repository from GitHub.

  • What languages does the server support?

The server supports both Chinese and English for location names.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shibing624
Star
3
Language
Python
License
Apache-2.0 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