mcp-weather-server

Created By
MiesnerJacoba year ago
An example Model Context Protocol server that provides weather data to LLMs.
Overview

what is mcp-weather-server?

The mcp-weather-server is an example Model Context Protocol server designed to provide weather data to Large Language Models (LLMs).

how to use mcp-weather-server?

To use the mcp-weather-server, you can integrate it with your LLM application by sending requests to the server to retrieve weather data based on specified parameters.

key features of mcp-weather-server?

  • Provides real-time weather data to LLMs
  • Supports various weather data queries
  • Easy integration with existing LLM applications

use cases of mcp-weather-server?

  1. Enhancing conversational AI with real-time weather updates.
  2. Enabling weather-related queries in chatbots.
  3. Supporting data-driven decision-making in applications requiring weather information.

FAQ from mcp-weather-server?

  • What kind of weather data can I get?

You can retrieve various types of weather data including temperature, humidity, wind speed, and forecasts.

  • Is there a limit to the number of requests?

The server is designed to handle multiple requests, but performance may vary based on server load.

  • Can I customize the data I receive?

Yes, you can specify parameters in your requests to customize the weather data you receive.

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