中国城市天气查询 MCP 服务

Created By
ACAne0320a year ago
Overview

What is AMap Weather MCP Server?

AMap Weather MCP Server is a Model Context Protocol (MCP) service that allows users to query real-time weather conditions and forecasts for cities in China using the AMap API.

How to use AMap Weather MCP Server?

To use the AMap Weather MCP Server, you need to clone the repository, install the dependencies, and run the service. You can then make requests to get current weather or forecasts for specific cities.

Key features of AMap Weather MCP Server?

  • Accurate weather data retrieval using AMap API.
  • Real-time weather status queries.
  • 3-4 day weather forecasts.
  • Intelligent city name recognition for queries at city and district levels.
  • Easy integration into AI applications as a standard MCP service.

Use cases of AMap Weather MCP Server?

  1. Checking the current weather in major Chinese cities.
  2. Planning trips based on weather forecasts.
  3. Integrating weather data into AI applications for enhanced user experience.

FAQ from AMap Weather MCP Server?

  • Is the service available for all cities in China?

Yes, it supports weather queries for cities across mainland China.

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

Yes, you need to configure an AMap API key as an environment variable.

  • What programming language is used for this project?

The project is implemented in Python.

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

21 hours ago