JMA Data MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_station_infoA | Get AMeDAS station information by station code. |
| search_stationsB | Search AMeDAS stations by name (Japanese, Kana, or English). |
| search_nearby_stationsA | Search AMeDAS stations within a radius from given coordinates. |
| get_stations_of_typeB | Get all AMeDAS stations of a specific type. |
| list_stationsA | List all AMeDAS stations (1286 stations) with pagination. |
| get_current_weatherB | Get current weather observation data from AMeDAS stations. |
| get_weather_by_locationA | Get current weather from the nearest AMeDAS station to given coordinates. |
| get_forecastC | Get weather forecast for a prefecture. |
| list_prefecturesA | List all available prefecture codes for weather forecast. Returns: Dictionary of prefecture names and their codes |
| get_historical_weatherB | Get historical weather data for a specific date and time. Data is available for approximately the past 1-2 weeks. |
| get_weather_time_seriesB | Get time series weather data for a station. Useful for analyzing weather trends over hours or days. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/koizumikento/jma-data-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server