Skip to main content
Glama
Sign In
JMA Data MCP

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-server-jma

      b84330808
      A
      license
      A
      quality
      B
      maintenance
      Enables access to Japan Meteorological Agency data through MCP, covering weather forecasts, warnings, earthquakes with seismic intensity, tsunami bulletins, and volcano alerts, with place-name lookup in kanji, kana, or romaji and no API key.
      7
      MIT

    • 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.
      134 npm
      MIT

    • MCP-Weather

      Takatoshi-Miura
      A
      license
      Not graded
      quality
      D
      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.
      9 npm
      MIT

    • 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
      D
      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.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Station lookup tools are split by clear query mode (code, name, coordinates, type, list-all), and weather tools are separated by temporal scope and access pattern (current, location-based, forecast, historical, time series). No two tools appear to do the same thing.

    Naming Consistency5/5

    All names use snake_case with a predictable verb_noun structure (get_, search_, list_), including compound names like search_nearby_stations and get_weather_by_location. The convention is consistent throughout.

    Tool Count5/5

    11 tools is well-scoped for a station-and-weather data server. Each tool covers a distinct retrieval mode without excessive granularity.

    Completeness4/5

    The surface covers station discovery thoroughly and weather retrieval across current, forecast, historical, and time-series modes. Minor gaps exist, such as forecast retrieval by coordinates rather than only prefecture, but core workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources