Skip to main content
Glama
koizumikento

JMA Data MCP

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to JMA Data MCP

No user-submitted related servers found.

    Related Servers

    • mcp-jma

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables you to retrieve JMA weather forecasts, warnings/advisories, and earthquake reports by place name, with no API key required.
      247 npm
      MIT

    • MCP-Weather

      Takatoshi-Miura
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables retrieval of weather information for major cities across Japan using the Japan Meteorological Agency API. Supports weather overviews, precipitation probability, and wind speed data with both local and remote OAuth 2.0 authenticated deployment options.
      10 npm
      -

    • Japanese Weather MCP

      tsukiyama85
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides weather information for 110 cities across Japan with natural language support for location names in kanji, hiragana, and katakana. Retrieves current weather conditions and forecasts using OpenMeteo API through MCP-compliant tools.
      1
      MIT

    • mcp-lab-jma

      sasonoda
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing weather forecast, warnings, AMeDAS observations, and area search from Japan Meteorological Agency JSON APIs. It normalizes responses and supports Japanese place names.
      -
    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

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes, but get_current_weather and get_weather_by_location both return current observations, differing only in how the station is specified, which could cause confusion. Similarly, get_historical_weather and get_weather_time_series overlap slightly. Descriptions help clarify, but some ambiguity remains.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., get_current_weather, list_prefectures, search_stations). Verbs are appropriate (get, list, search), and there is no mixing of naming conventions.

    Tool Count5/5

    With 11 tools, the server covers station information, current weather, forecasts, historical data, and search capabilities. This is well-scoped for a weather data server, neither too many nor too few.

    Completeness4/5

    The tool surface covers station queries, current weather, forecasts by prefecture, historical data, and time series. Minor gaps include lack of forecast for specific coordinates (only prefecture) and absence of weather alerts/warnings, but core workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources