MCP Weather Server

Created By
aditi-joshi-usca year ago
Overview

what is MCP Weather Server?

MCP Weather Server is a lightweight TypeScript and Node.js server that provides real-time weather alerts and forecast data using the National Weather Service API. It is built on the Model Context Protocol (MCP) to demonstrate how AI tools can consume external APIs.

how to use MCP Weather Server?

To use MCP Weather Server, you can invoke its API endpoints to get current weather alerts for a specific US state or to retrieve detailed weather forecasts based on geographic coordinates.

key features of MCP Weather Server?

  • get-alerts: Returns current weather alerts for a given US state code (e.g., "CA" for California).
  • get-forecast: Provides a detailed weather forecast based on latitude and longitude.

use cases of MCP Weather Server?

  1. Receiving timely weather alerts for specific regions.
  2. Accessing detailed weather forecasts for planning outdoor activities.
  3. Integrating weather data into other applications or services.

FAQ from MCP Weather Server?

  • What technology stack is used in MCP Weather Server?

The server is built using TypeScript and Node.js, utilizing the MCP SDK for tool communication and the NWS API for weather data.

  • Is MCP Weather Server free to use?

Yes! MCP Weather Server is open-source and available for anyone to use.

  • How can I contribute to MCP Weather Server?

You can contribute by visiting the GitHub repository and submitting pull requests or issues.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

33 minutes ago