Korea Building Register MCP
# ๐ข Korea Building Register MCP
[English](#english) | [ํ๊ตญ์ด](#ํ๊ตญ์ด)
---
## English
Ask Claude about Korean building register data โ powered by data.go.kr's Building Register API.
Provides **12 tools** for querying building register (๊ฑด์ถ๋ฌผ๋์ฅ) information including title sheets, floor details, exclusive-use areas, house prices, zoning, and more.
### Supported Tools
| Tool | Description |
|------|-------------|
| `smart_building_lookup` | ๐ข Smart lookup โ auto-detects general vs. collective buildings |
| `search_bjdong_code` | Search region codes (sigungu_cd, bjdong_cd) by name |
| `get_building_title_info` | Title sheet (ํ์ ๋ถ) โ area, structure, usage, etc. |
| `get_building_recap_title_info` | Summary title sheet (์ด๊ดํ์ ๋ถ) |
| `get_building_basis_ouln_info` | Basic outline (๊ธฐ๋ณธ๊ฐ์) |
| `get_building_floor_ouln_info` | Floor outline (์ธต๋ณ๊ฐ์) |
| `get_building_expos_info` | Exclusive-use units (์ ์ ๋ถ) |
| `get_building_expos_pubuse_area_info` | Exclusive/common area details (์ ์ ๊ณต์ฉ๋ฉด์ ) |
| `get_building_house_price_info` | Official house prices (์ฃผํ๊ฐ๊ฒฉ) |
| `get_building_wclf_info` | Sewage treatment facilities (์ค์์ ํ์์ค) |
| `get_building_atch_jibun_info` | Attached land lots (๋ถ์์ง๋ฒ) |
| `get_building_jijigu_info` | Zoning districts (์ง์ญ์ง๊ตฌ๊ตฌ์ญ) |
### Prerequisites
- [uv](https://docs.astral.sh/uv/getting-started/installation/)
- API key from [๊ณต๊ณต๋ฐ์ดํฐํฌํธ (data.go.kr)](https://www.data.go.kr)
- Apply for: [๊ฑด์ถHUB ๊ฑด์ถ๋ฌผ๋์ฅ์ ๋ณด ์๋น์ค](https://www.data.go.kr/data/15044713/openapi.do)
### Quick Start: Claude Desktop (stdio)
1. **Clone this repository**
```bash
git clone https://github.com/coding-realtor/building-register-mcp.git
cd building-register-mcp
```
2. **Open the Claude Desktop config file**
```bash
# macOS
open "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
# Windows
notepad %APPDATA%\Claude\claude_desktop_config.json
```
3. **Add the entry below under `mcpServers`**
```json
{
"mcpServers": {
"building-register": {
"command": "uv",
"args": [
"run",
"--directory", "/path/to/building-register-mcp",
"data-go-mcp-building-register"
],
"env": {
"BUILDING_REGISTER_API_KEY": "your_api_key_here"
}
}
}
}
```
> Replace `/path/to/building-register-mcp` with the actual path where you cloned the repository.
4. **Restart Claude Desktop**
Setup is complete when you can see the `building-register` server in the tool list.
### Usage Example
```
Tell me about the building at ์์ธ ์ข
๋ก๊ตฌ ์ฒญ์ด๋ 89-3
```
Claude will automatically:
1. Look up the region code via `search_bjdong_code`
2. Call `smart_building_lookup` to fetch building details
3. Present the results in a readable table
---
## ํ๊ตญ์ด
Claude์๊ฒ ๊ฑด์ถ๋ฌผ๋์ฅ ์ ๋ณด๋ฅผ ๋ฌผ์ด๋ณด์ธ์ โ ๊ณต๊ณต๋ฐ์ดํฐํฌํธ ๊ฑด์ถ๋ฌผ๋์ฅ์ ๋ณด API ๊ธฐ๋ฐ MCP ์๋ฒ์
๋๋ค.
๊ฑด์ถ๋ฌผ๋์ฅ **ํ์ ๋ถ, ์ธต๋ณ๊ฐ์, ์ ์ ๋ถ, ์ฃผํ๊ฐ๊ฒฉ, ์ง์ญ์ง๊ตฌ๊ตฌ์ญ** ๋ฑ์ ์กฐํํ๋ **12๊ฐ ๋๊ตฌ**๋ฅผ ์ ๊ณตํฉ๋๋ค.
### ์ ๊ณต ๋๊ตฌ (Tools)
| Tool ๋ช
| ์ค๋ช
|
|---------|------|
| `smart_building_lookup` | ๐ข ์ค๋งํธ ์กฐํ โ ์ผ๋ฐ/์งํฉ๊ฑด์ถ๋ฌผ ์๋ ํ๋ณ |
| `search_bjdong_code` | ์ง์ญ๋ช
์ผ๋ก ์๊ตฐ๊ตฌ์ฝ๋ยท๋ฒ์ ๋์ฝ๋ ๊ฒ์ |
| `get_building_title_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **ํ์ ๋ถ** (๋์ง๋ฉด์ , ๊ฑด์ถ๋ฉด์ , ์ฉ์ ๋ฅ ๋ฑ) |
| `get_building_recap_title_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ด๊ดํ์ ๋ถ** |
| `get_building_basis_ouln_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **๊ธฐ๋ณธ๊ฐ์** |
| `get_building_floor_ouln_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ธต๋ณ๊ฐ์** |
| `get_building_expos_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ ์ ๋ถ** (๋/ํธ ์ ๋ณด) |
| `get_building_expos_pubuse_area_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ ์ ๊ณต์ฉ๋ฉด์ ** |
| `get_building_house_price_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ฃผํ๊ฐ๊ฒฉ** (๊ณต์๊ฐ๊ฒฉ) |
| `get_building_wclf_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ค์์ ํ์์ค** |
| `get_building_atch_jibun_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **๋ถ์์ง๋ฒ** |
| `get_building_jijigu_info` | ๊ฑด์ถ๋ฌผ๋์ฅ **์ง์ญ์ง๊ตฌ๊ตฌ์ญ** |
### ์ฌ์ ์ค๋น
- [uv](https://docs.astral.sh/uv/getting-started/installation/) ์ค์น
- [๊ณต๊ณต๋ฐ์ดํฐํฌํธ](https://www.data.go.kr)์์ API ํค ๋ฐ๊ธ
- ์ ์ฒญ ๋์: [๊ฑด์ถHUB ๊ฑด์ถ๋ฌผ๋์ฅ์ ๋ณด ์๋น์ค](https://www.data.go.kr/data/15044713/openapi.do)
### ๋น ๋ฅธ ์์: Claude Desktop (stdio)
1. **๋ ํฌ์งํ ๋ฆฌ ํด๋ก **
```bash
git clone https://github.com/coding-realtor/building-register-mcp.git
cd building-register-mcp
```
2. **Claude Desktop ์ค์ ํ์ผ ์ด๊ธฐ**
```bash
# macOS
open "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
# Windows
notepad %APPDATA%\Claude\claude_desktop_config.json
```
3. **`mcpServers` ํญ๋ชฉ์ ์๋ ๋ด์ฉ ์ถ๊ฐ**
```json
{
"mcpServers": {
"building-register": {
"command": "uv",
"args": [
"run",
"--directory", "C:\\path\\to\\building-register-mcp",
"data-go-mcp-building-register"
],
"env": {
"BUILDING_REGISTER_API_KEY": "์ฌ๊ธฐ์_API_ํค_์
๋ ฅ"
}
}
}
}
```
> `C:\\path\\to\\building-register-mcp` ๋ถ๋ถ์ ์ค์ ํด๋ก ํ ๊ฒฝ๋ก๋ก ๋ณ๊ฒฝํ์ธ์.
4. **Claude Desktop ์ฌ์์**
๋๊ตฌ ๋ชฉ๋ก์ `building-register` ์๋ฒ๊ฐ ํ์๋๋ฉด ์ค์ ์๋ฃ์
๋๋ค.
### ์ฌ์ฉ ์์ (Claude์์)
```
์์ธ ์ข
๋ก๊ตฌ ์ฒญ์ด๋ 89-3 ๊ฑด๋ฌผ์ ๊ฑด์ถ๋ฌผ๋์ฅ ์กฐํํด์ค
```
```
๊ฐ๋จ๊ตฌ ์ญ์ผ๋ 736๋ฒ์ง ๊ฑด๋ฌผ์ ์ฃผํ ๊ณต์๊ฐ๊ฒฉ์ ์๋ ค์ค
```
```
์กํ๊ตฌ ์ ์ค๋ 40๋ฒ์ง ์ํํธ์ ๋/ํธ ๋ชฉ๋ก์ ๋ณด์ฌ์ค
```
Claude๊ฐ ์๋์ผ๋ก:
1. `search_bjdong_code`๋ก ์๊ตฐ๊ตฌ/๋ฒ์ ๋ ์ฝ๋๋ฅผ ๊ฒ์
2. `smart_building_lookup`์ผ๋ก ๊ฑด์ถ๋ฌผ ์ ๋ณด๋ฅผ ์กฐํ
3. ๊ฒฐ๊ณผ๋ฅผ ๋ณด๊ธฐ ์ข์ ํ๋ก ์ ๋ฆฌํ์ฌ ๋ณด์ฌ์ค๋๋ค
### Gemini CLI / ๊ธฐํ MCP ํด๋ผ์ด์ธํธ
Gemini CLI ๋ฑ ๋ค๋ฅธ MCP ํด๋ผ์ด์ธํธ์์๋ ๋์ผํ๊ฒ ์ฌ์ฉํ ์ ์์ต๋๋ค.
์ค์ ํ์ผ์ MCP ์๋ฒ ํญ๋ชฉ์ ์์ ๊ฐ์ ํ์์ผ๋ก ์ถ๊ฐํ์ธ์.
### ๋ก์ปฌ ํ
์คํธ
```bash
# ์๋ฒ ์ง์ ์คํ
uv run data-go-mcp-building-register
```
## ๋ผ์ด์ผ์ค
Apache-2.0 โ ์์ธํ ๋ด์ฉ์ [LICENSE](LICENSE) ํ์ผ์ ์ฐธ๊ณ ํ์ธ์.
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose targeting specific aspects of building registry data (e.g., basic overview, floor details, ownership information, sewage facilities). The descriptions clearly differentiate what each tool retrieves, with no apparent overlap in functionality. An agent can easily distinguish between tools like get_building_floor_ouln_info for floor-level data and get_building_expos_info for ownership unit details.
All tools follow a consistent snake_case naming pattern with a clear 'get_' or 'search_' prefix followed by a descriptive noun phrase. The naming convention is uniform across all 12 tools, making them predictable and easy to parse. Even the two non-get tools (search_bjdong_code and smart_building_lookup) maintain the same structural consistency.
With 12 tools, the server is well-scoped for its domain of building registry data in Korea. Each tool serves a specific, necessary function (e.g., retrieving different sections of the building registry, searching for codes, smart lookups). The count is neither too sparse nor excessive, covering various data aspects without redundancy.
The toolset provides comprehensive coverage for building registry queries, including code search (search_bjdong_code), smart overview (smart_building_lookup), and detailed retrievals for all major registry sections (title, floor, ownership, area, price, etc.). There are no obvious gaps; agents can navigate from address lookup to detailed data retrieval seamlessly, with tools like smart_building_lookup guiding workflows effectively.