Skip to main content
Glama
Weather MCP Server

Weather MCP Server

mcp-poc

Proyecto de prueba de concepto (POC) para un servidor MCP (Model Context Protocol) usando TypeScript y el SDK oficial.

Descripción

Este proyecto implementa un servidor MCP sencillo que expone una herramienta para obtener el clima actual de una ciudad utilizando la API de Open-Meteo. El servidor se comunica a través de stdin/stdout, lo que lo hace ideal para integraciones o pruebas automatizadas.

Related MCP server: mcp-poc

Requisitos

  • Node.js (recomendado v18+)

  • pnpm (o npm/yarn)

Instalación

pnpm install
# o
npm install
# o
yarn install

Uso

Para iniciar el servidor:

pnpm start
# o
node main.ts

El servidor expondrá una herramienta llamada get-weather que recibe el nombre de una ciudad y retorna información meteorológica actual.

Dependencias principales

  • @modelcontextprotocol/sdk: SDK oficial para implementar servidores MCP.

  • zod: Validación de esquemas para los parámetros de las herramientas.

Estructura principal

  • main.ts: Implementación del servidor MCP y la herramienta de clima.

  • .gitignore: Configuración para ignorar archivos y carpetas comunes en proyectos Node.js.

Para poder probar el servidor MCP con el inspector, se puede usar el siguiente comando:

npx @modelcontextprotocol/inspector npx -y tsx main.ts

Para agregar el mcp dentro del IDE, hay que seguir el siguiente formato json:

{
  "mcpServers": {
    "demo":{
      "command": "npx",
      "args": [
        "-y",
        "tsx",
        "<path_to>/mcp-poc/main.ts"
      ]
    }
  }
}

Available Tools

1 tool
get-weatherC

Tool to fetch the weather for a given city

Inputs: city (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'get-weather' follows a clear verb-noun pattern.

    Tool Count2/5

    A single tool is too few for a weather server's typical scope, which might include forecasts, historical data, or multiple locations. This feels thin and limits functionality.

    Completeness2/5

    The tool surface is severely incomplete for a weather domain. It only fetches current weather for a city, missing essential operations like forecasts, alerts, or multi-location queries, which will cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Lightweight MCP server that exposes tools for system information and weather lookup, designed for agent integration via stdio.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A proof-of-concept MCP server that provides weather information using the Open-Meteo API, with tools for greeting, getting weather by coordinates, and by location name.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that provides current weather for any city using Open-Meteo APIs. It exposes a single tool 'get_weather' returning temperature, humidity, wind, and other weather data.
      1
      12 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A minimal MCP server that provides current weather and forecasts for any city using the free Open-Meteo API, no API key required.
      9 npm
      -