Skip to main content
Glama
deenesjakoruzh
overstarry

qweather-mcp

by overstarry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

qweather-mcp

insignia de herrería

inglés |简体中文

Servidor MCP para la API de QWeather , que proporciona capacidades integrales de consulta de información meteorológica a través del Protocolo de Contexto de Modelo (MCP).

✨ Características

  • 🌤️ Consultas meteorológicas en tiempo real

  • 📅 Previsiones meteorológicas para varios días (3/7/10/15/30 días)

  • 🔑 Configuración sencilla de clave API

  • 🔌 Compatibilidad con URL base de API personalizada

  • 🛠️ Integración completa de herramientas

Related MCP server: OpenWeatherMap MCP Server

📦 Instalación

Vía Smithery

Recomendado: Instalar automáticamente para Claude Desktop usando Smithery :

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

Configuración manual

  1. Primero, obtenga su clave API desde la consola QWeather .

  2. Iniciar el servidor:

# stdio server
npx -y qweather-mcp

  1. Configurar variables de entorno:

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

Configuración JSON

Añade a tu archivo de configuración:

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

🛠️ Herramientas disponibles

obtener el tiempo ahora

Obtenga información meteorológica actual para una ubicación específica.

obtener el pronóstico del tiempo

Obtenga información del pronóstico del tiempo para una ubicación específica con días de pronóstico personalizables:

  • Pronóstico de 3 días

  • Pronóstico de 7 días

  • Pronóstico de 10 días

  • Pronóstico de 15 días

  • Pronóstico de 30 días

Los datos de pronóstico incluyen:

  • Rango de temperatura (mín./máx.)

  • Condiciones climáticas diurnas y nocturnas

  • Horas de salida y puesta del sol

  • Precipitación

  • Humedad

  • Condiciones del viento

  • Índice UV

obtener precipitación minuciosa

Proporciona un pronóstico de precipitaciones minuto a minuto para las próximas 2 horas, que incluye:

  • Tipo de precipitación (lluvia/nieve)

  • Cantidad de precipitación por minuto

  • Predicciones de tiempo precisas

  • Descripciones de pronósticos en tiempo real

obtener pronóstico por hora

Proporciona pronósticos meteorológicos por hora para 24, 72 o 168 horas, incluidos:

  • Cambios de temperatura

  • Condiciones climáticas

  • Dirección y fuerza del viento

  • Humedad relativa

  • Presión atmosférica

  • Probabilidad de precipitación

  • Cobertura de nubes

obtener alerta meteorológica

Proporciona información de advertencia meteorológica en tiempo real, que incluye:

  • Autoridad emisora de advertencias

  • Nivel y tipo de advertencia

  • Contenido detallado de la advertencia

  • Periodo de validez de la advertencia

  • Recomendaciones relacionadas

obtener índices meteorológicos

Proporciona información sobre índices de vida climática, admitiendo varios tipos de índices:

  • Índice de deportes

  • Índice de lavado de coches

  • Índice de vestimenta

  • Índice de pesca

  • Índice UV

  • Índice de turismo

  • Índice de alergia y otros 16 índices de vida

obtener calidad del aire

Proporciona datos sobre la calidad del aire en tiempo real, incluidos:

  • Índice AQI

  • Nivel de calidad del aire

  • Contaminantes primarios

  • Consejos de salud

  • Concentraciones de contaminantes

obtener la calidad del aire cada hora

Proporciona un pronóstico de la calidad del aire por hora para las próximas 24 horas:

  • Predicciones horarias del IQA

  • Cambios en la concentración de contaminantes

  • Evaluación del impacto en la salud

  • Recomendaciones de protección

obtener información diaria sobre la calidad del aire

Proporciona un pronóstico de la calidad del aire para los próximos 3 días:

  • Predicciones diarias del IQA

  • Pronósticos de contaminantes primarios

  • Cambios en el nivel de calidad del aire

  • Consejos de protección de la salud

🤝 Contribuyendo

¡Agradecemos cualquier problema o mejora! Consulta nuestras normas de contribución.

📄 Licencia

Instituto Tecnológico de Massachusetts (MIT)

🔗 Enlaces relacionados

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