天气 MCP Server

Created By
HZreala year ago
Overview

What is MCP Weather Server?

MCP Weather Server is a server application designed to provide weather-related data and services through the Model Context Protocol (MCP).

How to use MCP Weather Server?

To use the MCP Weather Server, run the server using the command uv run weather.py and configure your client (Claude for Desktop) to connect to the server.

Key features of MCP Weather Server?

  • Provides real-time weather data through MCP.
  • Easy integration with clients like Claude for Desktop.
  • Logs for monitoring and troubleshooting.

Use cases of MCP Weather Server?

  1. Integrating weather data into applications.
  2. Providing weather updates in real-time to users.
  3. Analyzing weather patterns through data collected by the server.

FAQ from MCP Weather Server?

  • What is the purpose of the MCP Weather Server?

The MCP Weather Server provides weather data and services to clients using the Model Context Protocol.

  • How do I configure the client to connect to the server?

You need to edit the claude_desktop_config.json file to include the server's command and arguments.

  • Where can I find the logs for troubleshooting?

Logs can be found in the ~/Library/Logs/Claude directory.

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

8 hours ago