概要
What is Korea Tourism API MCP Server?
The Korea Tourism API MCP Server is a Model Context Protocol (MCP) server powered by the official Korea Tourism Organization (KTO) API. It enables AI assistants to discover South Korean tourist spots, cultural sites, festivals, restaurants, accommodations, and more.
How to use Korea Tourism API MCP Server?
Obtain a KTO API key from the KTO Data Portal, then set the KOREA_TOURISM_API_KEY environment variable. Run the server using uv sync && uv run -m mcp_tourism.server (with optional transport flags) or via Docker. For Cursor integration, add a mcp.json entry that runs the Docker image with the API key.
Key features of Korea Tourism API MCP Server
- Comprehensive search by keyword, area, or location
- Rich details: descriptions, hours, fees, photos, addresses, contacts
- Location-aware discovery near GPS coordinates
- Find festivals and events by date range
- Multilingual support: English, Japanese, Chinese, Russian, Spanish, German, French
- Response caching, rate limiting, and automatic retries
- Supports stdio, HTTP, and SSE transport protocols
Use cases of Korea Tourism API MCP Server
- Plan a trip to South Korea with personalized attraction suggestions
- Provide real-time local recommendations in an AI travel assistant
- Discover cultural events and festivals within specific date ranges
- Get detailed information about accommodations, restaurants, and shopping
- Integrate Korean tourism data into web or mobile applications
FAQ from Korea Tourism API MCP Server
What API key is required?
You must obtain a Service Key from the Korea Tourism Organization (KTO) Data Portal for the TourAPI services, then set it as the environment variable KOREA_TOURISM_API_KEY.
Which languages are supported?
English, Japanese, Simplified Chinese, Traditional Chinese, Russian, Spanish, German, and French. Each language requires a separate API key from its respective data portal link.
What transport protocols are available?
The server supports three transports: stdio (default for MCP clients), streamable-http (for web applications), and sse (for real-time applications). Configuration is done via CLI arguments or environment variables.
Where does the data come from?
All data is fetched from the official Korea Tourism Organization (KTO) API. The server caches responses with a TTL to reduce redundant API calls.
Are there any rate limits or retries?
Yes, the server includes rate limiting to respect API usage limits and automatic retries for temporary network or server errors.
