Korean Agriculture Market Data MCP Server

Korean wholesale agriculture market data - auction prices, seasonal produce, market trends. That is what the korean agriculture market data mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Real-time auction prices from 32+ public wholesale markets across South Korea, powered by data.go.kr Open API.

The tools it exposes

The server publishes 6 tools. What each one is for:

• get_realtime_auction — Real-time auction data (63,000+ daily records nationwide)
• search_product_price — Search prices by product keyword with market-level summaries
• compare_market_prices — Compare prices across markets for a product
• get_price_trend — Price trends over recent N days
• get_market_list — List of all wholesale markets and category codes
• get_auction_summary — Daily auction statistics by product and market

What it needs from you

Configuration is passed through the environment: DATA_GO_KR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Korean Agriculture Market Data's toolset — get_realtime_auction, search_product_price, compare_market_prices and 3 more — is a fair guide to whether it matches your workflow. It is maintained by SongT-50; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Korean Agriculture Market Data's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.