Cwa Mcp Server

Created By
lincwa year ago
利用台灣中央氣象局的 API 建立 MCP-server
Overview

what is CWA MCP Server?

CWA MCP Server is a lightweight Model Context Protocol (MCP) server that connects Claude Desktop to Taiwan's Central Weather Administration (CWA) API to retrieve weather data.

how to use CWA MCP Server?

To use CWA MCP Server, obtain a CWA API key, set up the server by executing installation scripts, and configure your Claude Desktop settings to include the API key.

key features of CWA MCP Server?

  • Simple and lightweight Node.js implementation
  • Easy to set up and integrate with Claude Desktop
  • Access to weather forecast data for all cities in Taiwan

use cases of CWA MCP Server?

  1. Retrieving weather forecasts for specific cities in Taiwan.
  2. Integrating weather data into applications using Claude Desktop.
  3. Providing real-time weather updates in conversational interfaces.

FAQ from CWA MCP Server?

  • How do I obtain a CWA API key?

You can obtain a CWA API key by registering on the CWA open data portal and following the instructions to get your authorization code.

  • Can I run CWA MCP Server using Docker?

Yes! CWA MCP Server can be run using Docker by following the provided Docker setup instructions.

  • What cities are supported by CWA MCP Server?

CWA MCP Server supports various cities in Taiwan, including Taipei, Kaohsiung, and Tainan.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lincw
Star
0
Language
Shell
License
MIT license

Recommend Servers

View All
Voyei

3 hours 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.

13 hours ago