Weather MCP Server

Created By
bittush8789a year ago
Creating MCP (Model Context Protocol) weather-related projects involves setting up an MCP server that can fetch and provide weather data.
Overview

What is Weather MCP Server?

Weather MCP Server is a project that sets up a Model Context Protocol (MCP) server to fetch and provide weather data from the National Weather Service API.

How to use Weather MCP Server?

To use the Weather MCP Server, install the required dependencies and run the server using the provided command. Configure your MCP client with the necessary settings to communicate with the server.

Key features of Weather MCP Server?

  • Fetches active weather alerts for US states.
  • Provides short-term weather forecasts based on geographical coordinates.
  • Utilizes the MCP framework for seamless integration.

Use cases of Weather MCP Server?

  1. Monitoring weather alerts for specific states.
  2. Obtaining weather forecasts for planning outdoor activities.
  3. Integrating weather data into applications for real-time updates.

FAQ from Weather MCP Server?

  • What programming language is used for the Weather MCP Server?

The server is built using Python 3.7 and above.

  • How do I install the required dependencies?

You can install the dependencies by running the command: uv add mcp[cli] httpx requests.

  • Can I run the server on any operating system?

Yes, as long as you have Python and the required libraries installed, you can run the server on any OS.

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