Skip to main content
Glama
deenesjakoruzh
overstarry

qweather-mcp

by overstarry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

qweather-mcp

Schmiedeabzeichen

Englisch |简体中文

MCP-Server für die QWeather- API, der umfassende Abfragefunktionen für Wetterinformationen über das Model Context Protocol (MCP) bietet.

✨ Funktionen

  • 🌤️ Wetterabfragen in Echtzeit

  • 📅 Mehrtägige Wettervorhersagen (3/7/10/15/30 Tage)

  • 🔑 Einfache API-Schlüsselkonfiguration

  • 🔌 Unterstützung für benutzerdefinierte API-Basis-URLs

  • 🛠️ Vollständige Tool-Integration

Related MCP server: OpenWeatherMap MCP Server

📦 Installation

Über Smithery

Empfohlen: Automatische Installation für Claude Desktop mit Smithery :

npx -y @smithery/cli install @overstarry/qweather-mcp --client claude

Manuelle Konfiguration

  1. Holen Sie sich zunächst Ihren API-Schlüssel von der QWeather-Konsole .

  2. Starten Sie den Server:

# stdio server
npx -y qweather-mcp

  1. Konfigurieren Sie Umgebungsvariablen:

QWEATHER_API_BASE=https://api.qweather.com
QWEATHER_API_KEY=<your-api-key>

JSON-Konfiguration

Fügen Sie Ihrer Konfigurationsdatei hinzu:

{
  "mcpServers": {
    "qweather": {
      "command": "npx",
      "args": ["-y", "qweather-mcp"],
      "env": {
        "QWEATHER_API_BASE": "<your-api-url>",
        "QWEATHER_API_KEY": "<your-api-key>"
      }
    }
  }
}

🛠️ Verfügbare Tools

Wetter jetzt abrufen

Erhalten Sie aktuelle Wetterinformationen für einen bestimmten Ort.

Wettervorhersage abrufen

Erhalten Sie Wettervorhersageinformationen für einen bestimmten Ort mit anpassbaren Vorhersagetagen:

  • 3-Tages-Vorhersage

  • 7-Tage-Vorhersage

  • 10-Tage-Vorhersage

  • 15-Tage-Vorhersage

  • 30-Tage-Vorhersage

Zu den Prognosedaten gehören:

  • Temperaturbereich (min./max.)

  • Tag-/Nachtwetterbedingungen

  • Sonnenaufgangs-/Sonnenuntergangszeiten

  • Fällung

  • Luftfeuchtigkeit

  • Windverhältnisse

  • UV-Index

minütlich Niederschlag ermitteln

Bietet minutengenaue Niederschlagsvorhersagen für die nächsten 2 Stunden, einschließlich:

  • Niederschlagsart (Regen/Schnee)

  • Niederschlagsmenge pro Minute

  • Präzise Zeitvorhersagen

  • Echtzeit-Prognosebeschreibungen

Stündliche Vorhersage erhalten

Bietet stündliche Wettervorhersagen für 24, 72 oder 168 Stunden, einschließlich:

  • Temperaturänderungen

  • Wetterbedingungen

  • Windrichtung und -stärke

  • Relative Luftfeuchtigkeit

  • Luftdruck

  • Niederschlagswahrscheinlichkeit

  • Wolkenbedeckung

Wetterwarnung erhalten

Bietet Wetterwarninformationen in Echtzeit, darunter:

  • Warnung ausstellende Behörde

  • Warnstufe und -typ

  • Detaillierter Warninhalt

  • Gültigkeitsdauer der Warnung

  • Verwandte Empfehlungen

Wetterindizes abrufen

Bietet Informationen zu Wetterlebensindizes und unterstützt verschiedene Indextypen:

  • Sportindex

  • Autowaschindex

  • Dressing-Index

  • Fischereiindex

  • UV-Index

  • Tourismusindex

  • Allergieindex und 16 weitere Lebensindizes

Luftqualität ermitteln

Bietet Echtzeitdaten zur Luftqualität, darunter:

  • AQI-Index

  • Luftqualitätsniveau

  • Primäre Schadstoffe

  • Gesundheitstipps

  • Schadstoffkonzentrationen

Stündliche Luftqualitätsmessung

Bietet stündliche Luftqualitätsvorhersagen für die nächsten 24 Stunden:

  • Stündliche AQI-Vorhersagen

  • Veränderungen der Schadstoffkonzentration

  • Gesundheitsverträglichkeitsprüfung

  • Schutzempfehlungen

Tägliche Luftqualitätsdaten

Bietet eine Luftqualitätsvorhersage für die nächsten 3 Tage:

  • Tägliche AQI-Vorhersagen

  • Primäre Schadstoffprognosen

  • Änderungen der Luftqualität

  • Hinweise zum Gesundheitsschutz

🤝 Beitragen

Wir freuen uns über Probleme und Verbesserungen! Bitte beachten Sie unsere Beitragsrichtlinien.

📄 Lizenz

MIT

🔗 Verwandte Links

Available Tools

2 tools
get-weather-nowC

Get current weather for a location using QWeather API

ParametersJSON Schema
NameRequiredDescriptionDefault
locationYesLocation ID for the city

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description implies a read operation but lacks details about API key requirements, error handling, or response format. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise single sentence. Could be improved by adding a hint about the sibling tool or output format without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity, the description is incomplete. It does not explain how to obtain the location ID or what the output contains, missing essential context for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the parameter described as 'Location ID for the city'. The description adds no extra parameter info, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get current weather for a location' with a specific API mention. However, it does not differentiate from sibling 'lookup-city', which likely provides city IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description does not mention that the location parameter might come from the sibling tool 'lookup-city'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

lookup-cityC

Look up city information by name

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNameYesName of the city to look up

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the basic action, with no mention of side effects, authentication needs, rate limits, or error handling (e.g., if city not found). This is insufficient for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the action. It could be more structured (e.g., listing what information is returned), but it is not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with one parameter and no output schema, the description does not specify what fields of city information are returned, nor any behavioral context. This leaves the agent uncertain about the response format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (single parameter well-described in schema). The description adds no extra meaning beyond 'by name', but the schema already provides a clear description. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'look up city information by name', specifying verb and resource. However, it does not differentiate from the sibling tool 'get-weather-now', which may also involve city queries. The description lacks detail on what information is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or cases to avoid. The sibling tool exists but is not differentiated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedget-weather-now
    • First observedlookup-city
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one retrieves current weather data, and the other looks up city information. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern using snake_case: get-weather-now and lookup-city. The naming is predictable and clear.

Tool Count3/5

With only 2 tools, the set is on the lower end of reasonable. While it covers the basics, it feels minimal for a weather API, which typically includes more operations like forecasts or alerts.

Completeness2/5

The tool set lacks essential weather features such as forecasts, historical data, or severe weather alerts. For a weather-focused server, the absence of these common operations is a notable gap.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches