Weather API MCP Server

Created By
TuanKiria year ago
A lightweight Model Context Protocol (MCP) server that enables AI assistants like Claude to retrieve and interpret real-time weather data. What makes it popular:
Overview

What is Weather API MCP Server?

Weather API MCP Server is a lightweight Model Context Protocol (MCP) server that allows AI assistants like Claude to access and interpret real-time weather data.

How to use Weather API MCP Server?

To use the MCP server with Claude Desktop, you need to add it to your Claude configuration with your API key from weatherapi. You can also build it from source using Go.

Key features of Weather API MCP Server?

  • Retrieves current weather data for specified cities.
  • Easy integration with AI assistants like Claude.
  • Built with Go for performance and efficiency.

Use cases of Weather API MCP Server?

  1. Providing real-time weather updates in AI applications.
  2. Enhancing user interactions with weather-related queries in chatbots.
  3. Integrating weather data into various applications for better user experience.

FAQ from Weather API MCP Server?

  • How do I get my API key?

You can obtain your API key by creating an account at weatherapi.

  • Is the server easy to set up?

Yes! The setup process is straightforward, and you can follow the provided instructions in the documentation.

  • What programming language is used?

The server is built using Go.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TuanKiri
Star
184
Language
Go
License
MIT 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.

a day ago