Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@KMA Weather MCP Server 서울 강남구의 오늘 오후 날씨와 강수 확률 알려줘"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
대한민국 기상청(KMA) 단기예보 Open API를 연결하는 Model Context Protocol (MCP) 서버입니다.
weather://seoul/now: 서울(시청)의 현재 날씨 데이터를 조회합니다.
weather://{latitude}/{longitude}/now: 입력한 위도/경도 위치의 현재 날씨를 조회합니다.
get_ultra_short_term_forecast: 향후 6시간의 초단기 예보를 조회합니다. (강수확률, 하늘상태 등)
get_village_forecast: 오늘부터 모레까지의 단기 예보를 조회합니다.
Related MCP server: Weather MCP Server
공공데이터포털에서 '기상청_단기예보 조회서비스' 활용신청을 하고 **일반 인증키(Decoding)**를 발급받으세요.
프로젝트 루트 .env 파일에 키를 저장합니다:
KMA_API_KEY_DECODED=your_decoding_key_hereclaude_desktop_config.json)Claude Desktop 앱에서 이 서버를 사용하려면 설정 파일을 수정해야 합니다.
경로:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
설정 내용:
{
"mcpServers": {
"kma-weather": {
"command": "uv",
"args": [
"run",
"-q",
"--with",
"mcp[cli]",
"--with",
"httpx",
"--with",
"fastmcp",
"--with",
"python-dotenv",
"/ABSOLUTE/PATH/TO/Public API to MCP Converter Agent/kma-weather-mcp/src/server.py"
],
"env": {
"KMA_API_KEY_DECODED": "YOUR_KEY_HERE (Optional if using .env file in project dir)"
}
}
}
}*주의: args의 마지막 경로는 실제 server.py가 위치한 절대 경로로 수정해야 합니다.*
# Run server using default MCP Inspector
npx @modelcontextprotocol/inspector uv run src/server.pyGet Ultra Short Term Forecast (Next 6 hours).
useful for: checking immediate weather changes, near-future rain/snow probability.
Inputs: latitude (required), longitude (required). Returns: result
Get Village Forecast (Short Term, up to 3 days).
useful for: planning for tomorrow or the day after, checking daily highs/lows.
Note: Can be slow as it returns a lot of data.
Inputs: latitude (required), longitude (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: one provides an ultra short-term forecast for the next 6 hours, while the other offers a village forecast for up to 3 days. There is no overlap in their temporal scope or use cases, making it easy for an agent to choose the appropriate tool based on the required timeframe.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive names (get_ultra_short_term_forecast and get_village_forecast). The naming is predictable and readable, adhering to snake_case throughout without any deviations.
With only 2 tools, the server feels thin for a weather forecasting domain, as it lacks coverage for common needs like current conditions, alerts, or longer-term forecasts beyond 3 days. This limited scope may hinder agents from performing comprehensive weather-related tasks.
The toolset is severely incomplete for weather forecasting, missing essential operations such as getting current weather, historical data, or severe weather alerts. While the two tools cover short-term forecasts, the absence of broader functionality creates significant gaps that could lead to agent failures in real-world scenarios.
Current weather and forecast lookup as an agent tool.
Global weather via Open-Meteo: forecast, historical, marine, air quality, geocoding, elevation.
Current weather and forecasts for any coordinates, backed b… — paid per call (x402/credits), 1 tools
Current weather and 7-day forecast for any place (MET Norway). $0.006/call via x402.