ZBS Index What actually exists in applied AI, with the source next to it

mcp server

japan-seasons

Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather.

Description as published by the maintainer. Source

  • version 0.5.0
  • active

active — Most recent push to the repository was 2026-07-13.

What this server can do

17 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

festivals_list(type, month, prefecture)
Use this when the user wants recurring Japan events to plan around, such as fireworks, matsuri, or winter festivals. Returns curated events with typical dates, attendance, official URLs, notes, and GPS coordinates. Do not use this for bloom timing, one-off concerts, or weather forecasts.
fetch(id)
Use this after search to retrieve a full Japan in Seasons result with citation URL and text. For live sakura or autumn leaves result IDs, this fetches the current forecast answer from live JMC data. Required: id.
flowers_spots(type, month, prefecture)
Use this for non-sakura flower trips such as plum, wisteria, hydrangea, lavender, sunflower, or cosmos. Returns curated flower spots with peak windows, official URLs, notes, and GPS coordinates. Do not use this for cherry blossom or autumn leaves timing; use the sakura or koyo tools for those live forecasts.
fruit_farms(fruit, limit, month, region)
Use this when the user needs actual fruit-picking farms, booking links, and map coordinates. Returns farms from the local dataset, and month filtering automatically narrows results to fruits that are in season. If the user only asks which fruit is in season, call fruit_seasons first.
fruit_seasons(month)
Use this when the user asks what fruit is in season in a given month or which month is best for strawberries, grapes, peaches, apples, and similar picking trips. Returns the fruit season calendar, peak months, best regions, and notes for 14 fruits. Call fruit_farms next if the user needs actual farm listings, map coordinates, or booking links.
japan_seasonal_answer(season, end_date, location, question, start_date)
Use this first when the user asks a broad Japan seasonal travel question, including cherry blossom forecasts, autumn leaves, flowers, festivals, fruit picking, or what is good during travel dates. This is the best entry point for natural traveler prompts because it routes to the right live dataset and returns a ready-to-use recommendation. Do not use this for hotels, flights, trains, visas, restaurants, or generic itinerary planning unrelated to seasonal timing.
kawazu_forecast(spot_name, include_spots)
Use this for January-February cherry blossom requests or when the user specifically asks about Kawazu-zakura, early blossoms, or the Izu Peninsula. Returns the Japan Meteorological Corporation forecast comment, forecast map links, and Kawazu cherry spots with bloom percentages, full-bloom percentages, forecast dates, and coordinates. Do not use this for standard Somei-Yoshino sakura elsewhere in Japan.
koyo_best_dates(end_date, start_date)
Use this when the user gives autumn travel dates and wants the best cities during that window. Returns cities whose maple or ginkgo viewing windows overlap the trip, based on forecast peak dates. Do not use this for general climate questions or for exact park recommendations without dates; use koyo_spots when the prefecture is already known. Required: start_date, end_date.
koyo_forecast(region, tree_type)
Use this when the user asks when autumn leaves peak, whether one city colors earlier than another, or wants a national overview for October-December. Returns city-level maple and ginkgo forecast dates, forecast maps, and regional commentary from Japan Meteorological Corporation. Do not use this for specific temples, gardens, or GPS-tagged locations; call koyo_spots next for those.
koyo_now(region, end_date, start_date)
Use this first for broad autumn leaves prompts such as 'How are autumn leaves looking?', 'Where is koyo good now?', 'Kyoto autumn leaves forecast', or 'Where should I see fall foliage in Japan?'. Returns a concise current answer from live Japan Meteorological Corporation maple and ginkgo forecast data. Do not use this for cherry blossoms, fruit picking, hotels, trains, or generic itinerary planning.
koyo_spots(prefecture)
Use this when the user already knows the prefecture and needs exact autumn leaves viewing spots. Returns Japan Meteorological Corporation koyo spots for one prefecture with best start, peak, and end dates, leaf type, popularity rating, and GPS coordinates. Omit prefecture to get a top-destinations guide. Do not use this for cross-city date matching; use koyo_forecast or koyo_best_dates first.
sakura_best_dates(end_date, start_date)
Use this when the user provides travel dates and wants to know where sakura is likely to be best during that trip. Returns cities whose viewing window overlaps the requested date range, based on observed or forecast full-bloom dates. Do not use this for January-February early-bloom Kawazu requests; use kawazu_forecast for those. Required: start_date, end_date.
sakura_forecast(city)
Use this when the user asks about cherry blossom timing, peak bloom, whether sakura has started, or how cities compare across Japan. Returns Japan Meteorological Corporation forecast bloom dates, full-bloom dates, observed dates when available, historical averages, and status for 48 observation cities. Do not use this for specific parks or temples; call sakura_spots next for prefecture-level viewing spots.
sakura_now(city, end_date, start_date)
Use this first for broad cherry blossom prompts such as 'How is the sakura forecast?', 'Is sakura blooming now?', 'Where should I view sakura today?', 'Where should I see cherry blossoms this week?', or 'How is Kyoto sakura looking?'. Returns a concise current answer from live Japan Meteorological Corporation forecast and observation data, including specific viewing spot suggestions when current spot data is available, plus next-step guidance for the full park list and weather. Do not use this for autumn leaves, non-sakura flowers, hotels, trains, or generic itinerary planning.
sakura_spots(prefecture)
Use this when the user already knows the prefecture and needs exact cherry blossom viewing spots with current status and GPS coordinates. Each spot uses JMC reporter observations as the primary status when filed within the last 48 hours (states: pre-bloom through hazakura/green leaves); falls back to the JMC bloom-meter estimate otherwise, with any stale observation shown as secondary context. Also returns the prefecture's JMA reference station summary. Do not use this for nationwide timing comparisons or date matching; use sakura_forecast or sakura_best_dates first. Required: prefecture.
search(query)
Use this for ChatGPT/deep-research style retrieval over Japan in Seasons. Searches live seasonal-travel dataset guides and returns result IDs for fetch. Use for questions about Japan cherry blossom forecasts, autumn leaves, seasonal flowers, festivals, fruit picking, weather, or the MCP server itself. Do not use for hotels, flights, trains, visas, or restaurants. Required: query.
weather_forecast(city)
Use this when short-range weather could change the recommendation, especially for sakura petal fall, rain risk, or packing advice. Returns the next 3 days of Japan Meteorological Agency forecast text, temperatures, and 6-hour rain probabilities for one supported city. Do not use this for seasonal bloom timing months in advance; use the sakura or koyo forecast tools for that. Required: city.

Last successful function declaration observed on . Source: https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage}.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 1 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-13 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 2 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 0.5.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-07-13 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License MIT Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-07-13 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 17 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe seasons.kooexperience.com
mcp endpoint status ok The server listed 17 functions when asked. as of probe seasons.kooexperience.com

Where to get it

Related, by what their authors tagged them

  • Gachi Data API — Japan Station & Accessibility Data — last commit 2026-08-02, shares japan, open-data, travel
    Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first.
  • Torify — Japan Locale APIs for AI Agents — last commit 2026-05-29, shares japan
    39 Japanese locale APIs — wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI).
  • Japan Food DB — last commit 2026-07-02, shares japan
    Resolve Japanese food names to nutrition facts. All 2,538 foods from Japan's official tables.
  • io.github.ajtgjmdjp/edinet-mcp — last commit 2026-07-27, shares japan
    Access Japanese financial disclosures (EDINET). Search companies, retrieve BS/PL/CF statements.
  • com.trainrouter/atlas — last commit 2026-07-31, shares open-data, travel
    The world railway atlas as MCP tools: 744+ legendary train routes, night trains, journey times.
  • ai.gondola/gondola — last commit 2026-07-24, shares travel
    Travel award search: compare cash vs points on hotels, flights & cars, cents-per-point, and book.
  • OctoTrip Flights — last commit 2026-07-07, shares travel
    Free, no-login flight search with real-time pricing from multiple airlines.
  • OctoTrip Rental Cars — last commit 2026-07-06, shares travel
    Free, no-login rental car search with real-time pricing.
  • travel.art — last commit 2026-06-21, shares travel
    Art-tourism data for AI agents: biennales, art fairs, museums, layover itineraries with 2026 facts.
  • My Next Adventure — last commit 2026-07-29, shares travel
    Create trips, compare variants side by side, and add accommodation, transport and event options.

These share tags the maintainers applied themselves, such as japan, open-data, travel. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

How the author describes it

Topics the maintainer set on GitHub: autumn-leaves, cherry-blossom, japan, mcp, model-context-protocol, open-data, travel, typescript.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. haomingkoo/japan-seasons-mcp on GitHub — GitHub, observed , trust tier 3.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.
  3. Tools declared by the MCP server at https://seasons.kooexperience.com/mcp?dateStyle={dateStyle}&temperatureUnit={temperatureUnit}&includeCoordinates={includeCoordinates}&mapLanguage={mapLanguage} — seasons.kooexperience.com, observed , trust tier 1.