双源天气 MCP 服务器

Created By
qiangge2008a year ago
Overview

What is Weather MCP Server?

Weather MCP Server is a weather server based on the Model Context Protocol (MCP) that provides weather data using APIs from HeWeather and Seniverse, supporting failover and prioritizing the fastest response.

How to use Weather MCP Server?

To use the Weather MCP Server, clone the repository, install dependencies, configure environment variables with your API keys, and run the server using npm commands.

Key features of Weather MCP Server?

  • View current weather as a resource.
  • Get current weather for a specified city.
  • Retrieve weather forecasts for a specified city.
  • Use multiple API sources simultaneously, automatically selecting the fastest response.
  • Support for minimum/maximum temperature, humidity, and wind speed data.

Use cases of Weather MCP Server?

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

FAQ from Weather MCP Server?

  • How do I obtain API keys for HeWeather and Seniverse?

You can register on their respective developer platforms to create applications and obtain API keys.

  • Does the server support HTTP requests?

No, the server operates solely in MCP mode and does not provide HTTP server functionality.

  • What happens if one of the APIs fails?

The server automatically switches to the other API to ensure continuous service.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qiangge2008
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

3 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.

14 hours ago