Skip to main content
Glama
b84330808

mcp-server-jma

by b84330808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-jma

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.
      13 npm
      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.
      -

    • 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

    • PPN Hub Free MCP

      dkurokawa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables keyless, read-only access to a wide range of public APIs (including weather, elevation, Japanese addresses, environment, science, and civic data) through MCP clients, with usage limits and abuse protection built in.
      MIT

    • MCP-Weather

      Takatoshi-Miura
      A
      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.
      3 npm
      MIT
    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

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct JMA data product: area lookup, forecast, weather warnings, earthquake list, earthquake detail, tsunami, and volcano warnings. The list/get pair for earthquakes follows a clear convention, and the three hazard tools (warnings, tsunami, volcano) are unambiguous because each names a different hazard type. No two tools appear interchangeable.

    Naming Consistency5/5

    Every tool uses the same jma_ prefix followed by a verb_noun pattern (find_area, get_forecast, list_earthquakes, get_earthquake, get_tsunami, get_volcano_warnings). The list vs get distinction is applied consistently and predictably.

    Tool Count5/5

    Seven tools is well within the sweet spot for a domain-specific data server. Each tool corresponds to a genuine, distinct JMA dataset with no filler or trivially wrapped endpoints.

    Completeness4/5

    The surface covers area resolution, forecasts, weather warnings, earthquakes (both list and detail), tsunami, and volcano warnings — strong lifecycle coverage for hazard monitoring. Minor gaps remain, such as current/observed conditions (AMeDAS) and typhoon tracks, but agents can work around these for most JMA use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources