Korean Public Data MCP Server

Korean Public Data MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Korean government open data - weather, population, law search via data.go.kr.

What you get

Korean government open data - weather, population, law search via data.go.kr

What the assistant can call

Once Korean Public Data is connected, these are the calls the assistant has available:

• API — 발급처

Configuration and credentials

You will need 2 environment variables: DATA_GO_KR_API_KEY, ECOS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Korean Public Data's toolset — API — 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 Public Data's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the korean public data mcp server does with a few real requests.