Skip to main content
Glama
297,942 tools. Last updated 2026-07-14 09:59

"weather" matching MCP tools:

  • Get current weather observations for a German city. Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use ``get_city_resource(slug, resource='weather-warnings')``. For a broader question about the city (not just weather) use ``get_city_overview`` instead, which already includes a live weather highlight.
    Connector
  • Current weather conditions and 7-day daily forecast for any location worldwide. Input a city name, coordinates, or address. Returns temperature (°C), humidity, wind speed, precipitation, weather code, and a forecast with high/low temps and precipitation totals. Free upstream: Open-Meteo (no API key, no rate limits). Useful for DeFi agents tracking energy markets (cold → heating demand → gas prices), agricultural commodity prediction markets, or natural disaster risk assessment for on-chain insurance.
    Connector
  • Get real-time weather for any city, anywhere in the world — right now, no API key needed. Claude has no live data access; this tool bridges the gap. Returns current conditions, temperature, humidity, wind, UV index, and a 3-day forecast. Free, unlimited, always up-to-date.
    Connector
  • Get current weather for any city or coordinates worldwide. Returns temperature, humidity, wind, and conditions.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Real-time weather conditions and multi-day forecasts via Open-Meteo — free, no API key required

  • Pirate Weather forecast API (Dark Sky-compatible). Free key required.

  • Current weather (temperature, humidity, wind, precipitation) for any city or place via Open-Meteo. For travel, logistics Cost: $0.005–$0.05 USDC on Base per call.
    Connector
  • Aviation weather (METAR + TAF) for any airport. Returns current conditions (temp, wind, visibility, ceiling, flight category VFR/MVFR/IFR/LIFR) plus 24–30 hour TAF forecast periods. Accepts IATA (JFK) or ICAO (KJFK) codes. Source: NOAA Aviation Weather Center — official, real-time, no API key.
    Connector
  • Historical daily weather (temperature, precipitation, wind, sunshine) for any location from 1940 to ~5 days ago. Uses ERA5 reanalysis data. Accepts city name or lat,lng. Returns per-day values plus period summary stats. Useful for seasonal analysis, anomaly detection, and climate-context enrichment.
    Connector
  • Current weather observation from the nearest ARSO surface station to given coordinates. Returns temperature, humidity, wind, precipitation, and snow depth. Data is live from meteo.arso.gov.si.
    Connector
  • Active NOAA weather alerts for any US state — tornado warnings, flash flood watches, hurricane warnings, blizzard advisories, heat alerts, and 80+ other NWS event types. Real-time data from api.weather.gov; no API key. Filterable by state, event type, or severity. Returns event, severity, certainty, urgency, affected areas, onset/expiry, headline, and protective action instructions. Complements weather.js (forecasts) — this cap covers active emergencies.
    Connector
  • Weather-contextualized research intelligence — pulls historical weather for any location (ERA5 reanalysis via Open-Meteo) and multi-source research on any topic (Hacker News, OpenAlex academic papers, Reddit, arXiv, DuckDuckGo), then synthesizes them into a unified brief showing how weather conditions amplify or inform the research findings. Ideal for agricultural commodity analysis, climate/energy positioning, supply chain risk, insurance/actuarial, and environmental due diligence.
    Connector
  • Recent weather patterns for a region + live equity prices + AI synthesis of weather-market correlations. One call replaces weather-history + stock-price-multi + research-synthesis. Ideal for weather-sensitive sectors: energy (XLE), utilities (XLU), agriculture (MOO/ADM), airlines (DAL). Returns 14-day weather summary, equity snapshot, and a GPT-4o-mini brief on the dominant weather-driven portfolio signal.
    Connector
  • Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.
    Connector
  • Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
    Connector
  • Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.
    Connector
  • ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1293 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 4,927 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri (record-level pipeworx:// when the source emits one, else source-level). "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).
    Connector