MCP server for real estate, land and infrastructure data
Korzy is an MCP server for real estate and land data: it gives an AI assistant tools that look up real parcel and infrastructure records, so its answers about a place come from data rather than memory.
AI agents: the job to be done
Language models answer questions about specific properties from whatever they saw in training, which is rarely the current record. Agents that research land, energy or real estate need tools that return the record itself: the parcel at an address, the utilities at a point, the projects nearby.
The Korzy MCP server exposes those lookups as tools any MCP client can call. The plugin for Claude Code and Codex adds a research skill that chains them: address search, parcel record, then site context.
Questions Korzy answers for AI agents
- Who owns this property and when did it last sell? (owner fields where published)
- Does this address have public water and sewer?
- What data-center projects are planned near this site?
- What generation and grid capacity are in this region?
API routes and MCP tools for AI agents
Each lookup is a REST route and, where named, a tool on the Korzy MCP server. Routes link to their section of the API reference; credits and rate limits covers what each request costs.
| MCP tool | REST route | What it returns |
|---|---|---|
search_parcels | /api/search | Parcels at an address. |
get_parcel | /api/parcel-record | One parcel’s attributes and a map link. |
get_site_context | /api/query/point | Parcels, water and sewer service, treatment plants and data-center projects at a point. |
get_environment_context | /api/environment/context | Environmental layers at a point and nearby cleanup sites. |
get_logistics_context | /api/logistics/context | Nearby transport and logistics features. |
list_datasets | /api/query/catalog | Coverage, source dates and query limits, so the agent knows what exists before it spends credits. |
Example requests and production responses
Real responses from the production API, captured November 5, 2026 and trimmed to the main fields. Every request needs an API key; see API authentication.
1. search_parcels with owner fields
The tool call an agent makes for “Who owns 1600 Glenarm Pl, Denver?”, and the first record returned. Owner values are placeholders. 2 credits.
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "search_parcels",
"arguments": {
"address": "1600 Glenarm Pl, Denver, CO",
"limit": 5,
"include_owner": true
}
}
}Response (trimmed)
{
"results": [
{
"korzy_id": "08031-38ea02a85c11fd253b1c",
"address": "1600 GLENARM PL",
"city": "DENVER",
"postcode": "80202-4311",
"county": "Denver",
"statefp": "08",
"longitude": -104.98947115039978,
"latitude": 39.744195649999995,
"match_type": "exact",
"countyname": "Denver",
"parceladdr": "1600 GLENARM PL",
"parcelcity": "DENVER",
"parcelid": "0234610035000",
"saleamt": 131000000,
"saledate": "2018-07-11",
"updated": "2026-04-21",
"usedesc": "COMMERCIAL-OFFICE",
"situs_zip": "80202-4311",
"zoning_code": "CBD",
"assessed_value_usd": 0,
"market_value_usd": 885700,
"geoid": "08031",
"owner_name": "EXAMPLE HOLDINGS LLC",
"owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}
],
"truncated": false,
"limit": 5
}2. get_site_context at the parcel
One call returns the parcel, the water and sewer service areas and nearby data-center projects at the point.
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "get_site_context",
"arguments": {
"longitude": -78.666186,
"latitude": 35.787588,
"parcel_limit": 1
}
}
}Response (trimmed)
{
"longitude": -78.666186,
"latitude": 35.787588,
"parcels": {
"available": true,
"records": [
{
"bldgsqft": 32147,
"countyname": "Wake",
"latitude": 35.78758805,
"longitude": -78.66618558988388,
"korzy_id": "37183-a18c4295290bf3664953",
"parceladdr": "2304 HILLSBOROUGH ST",
"parcelcity": "RALEIGH",
"parcelid": "0794910704",
"saleamt": 225000,
"saledate": "1989-08-17",
"statefp": "37",
"taxacres": 0.21,
"totalvalue": 9236920,
"updated": "2026-05-17",
"usedesc": "C",
"yearbuilt": 2016,
"situs_zip": "27607",
"land_use_code": "COM",
"building_count": 2,
"land_value_usd": 2476416,
"improvement_value_usd": 6760504,
"last_sale_document": "Deed Book/Page 016128/02260",
"geoid": "37183"
}
],
"limit": 1,
"truncated": false,
"as_of": "2026-11-04"
},
"utilities": {
"available": true,
"longitude": -78.666186,
"latitude": 35.787588,
"matches": {
"water": [
{
"feature_id": "water:29943",
"name": "RALEIGH, CITY OF",
"boundary_basis": "System Sourced"
}
],
"sewer": [
{
"feature_id": "sewer:2161",
"name": "NEUSE RIVER RESOURCE RECOVERY FACILITY",
"boundary_basis": "Sourced"
}
]
},
"nearby_treatment": [
{
"feature_id": "treatment:7989",
"name": "NORTH CARY WWTP",
"distance_km": 11.327051931207679
},
{
"feature_id": "treatment:7990",
"name": "SOUTH CARY WWTP",
"distance_km": 17.15015426882848
},
{
"feature_id": "treatment:7988",
"name": "APEX WWTP",
"distance_km": 17.341396114306253
}
],
"truncated": {
"water": false,
"sewer": false
}
},
"datacenters": {
"available": true,
"projects": [
{
"project_id": "dc_2d5986069aa831e54347",
"name": "Segra Data Center",
"operator": "",
"status": "unknown",
"state": "NC",
"city": "Raleigh",
"address": "2100 Garner Station Boulevard",
"longitude": -78.6623631815708,
"latitude": 35.72499205,
"location_precision": "footprint",
"distance_km": 6.9689044329670615
},
{
"project_id": "dc_72c2d4763a2eed2b4c93",
"name": "TierPoint Raleigh (Departure Drive)",
"operator": "TierPoint",
"status": "operating",
"state": "NC",
"city": "Raleigh",
"address": "5301 Departure Drive",
"longitude": -78.595815,
"latitude": 35.8543896,
"location_precision": "exact",
"distance_km": 9.768935059607678
}
],
"radius_km": 10,
"limit": 5,
"truncated": false
},
"complete": true
}County parcel data for AI agents
Parcel coverage, infrastructure counts and example requests for counties where this work is common. Korzy covers parcel data in every U.S. county.
How Korzy compares with other parcel data APIs
More Korzy use cases
Connect your agent to Korzy
Every plan includes the MCP server and the plugin for Claude Code and Codex. Sign in with your Korzy account or use an API key.