Cenogram - Polish Real Estate Transactions (RCN)

Polish real estate transaction prices from notarial deeds, not listings - 8M+ records from the national RCN registry, 2003 to present, with OAuth 2.1.

Documentation

Cenogram MCP Server

npm version Node.js License: MIT

Polish Real Estate Transaction & Parcel Data for AI

MCP server for Polish real estate data. Access 8M+ real estate transactions from the national Registry of Prices and Values (Rejestr Cen Nieruchomosci, RCN) - prices from notarial deeds, not listings - directly from Claude, Cursor, ChatGPT, Grok, or any MCP-compatible AI assistant. Beyond transaction prices, the server resolves cadastral parcels and adds per-parcel context: zoning, flood and landslide risk, heritage register, building permits and construction activity, public transport access, agricultural land classification, surrounding land use, nature - nearby forest and overlapping protected areas - what lies underground (mining terrains and major groundwater reservoirs), the land-use and soil-quality classification, and road access.

Data source: Polish national RCN registry (Rejestr Cen Nieruchomosci) | Platform: cenogram.pl

Get your API key

  1. Go to cenogram.pl/api
  2. Enter your email
  3. You'll receive your cngrm_... API key by email

Manage your keys at cenogram.pl/ustawienia.

Free tier

New accounts start with 1,000 tokens and a 14-day trial of the Standard plan. After that the key keeps working on 50 tokens a week - the balance is restored to 50 every 7 days rather than accumulating - with no expiry date and no card.

A call costs 1 token for statistics, reference data, parcel identity and municipal context; 2 for a transaction search, a price histogram or a list of the parcels in an area; 4 for one context layer of a parcel or transaction; 5 for spatial search, parcel outlines, valuation and a multi-district comparison; 45 for get_parcel_report, which returns every layer at once. Location catalogues are free. Paid plans raise the allowance - see cenogram.pl/api.

Installation

Pick your client. All options below use the hosted server - no local install needed (except npx/stdio).

Claude Code

One command - zero config files:

claude mcp add cenogram https://mcp.cenogram.pl/mcp \
  -t http -H "Authorization: Bearer YOUR_API_KEY"
Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "cenogram": {
      "type": "http",
      "url": "https://mcp.cenogram.pl/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Claude Desktop

Add to your config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

npx (stdio):

{
  "mcpServers": {
    "cenogram": {
      "command": "npx",
      "args": ["-y", "@cenogram/mcp-server@latest"],
      "env": {
        "CENOGRAM_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
VS Code / GitHub Copilot

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "cenogram": {
      "type": "http",
      "url": "https://mcp.cenogram.pl/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

HTTP remote:

{
  "mcpServers": {
    "cenogram": {
      "type": "http",
      "url": "https://mcp.cenogram.pl/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

If HTTP doesn't work, use the npx (stdio) option below instead.

Cline

In VS Code: Settings > Cline > MCP Servers. Add:

{
  "cenogram": {
    "type": "http",
    "url": "https://mcp.cenogram.pl/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_API_KEY"
    }
  }
}
npx (stdio) - local/offline

Requires Node.js >= 18. Use this if you want to run the server locally instead of connecting to the hosted one.

{
  "mcpServers": {
    "cenogram": {
      "command": "npx",
      "args": ["-y", "@cenogram/mcp-server@latest"],
      "env": {
        "CENOGRAM_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
ClientConfig file
Cursor.cursor/mcp.json
Claude Code.mcp.json in your project
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json
ClineVS Code settings > Cline > MCP Servers

Configuration

Env VariableRequiredDefaultDescription
CENOGRAM_API_KEYYes (stdio)-API key from cenogram.pl/api
CENOGRAM_API_URLNohttps://cenogram.plAPI base URL
MCP_TRANSPORTNostdioSet to http for Streamable HTTP mode
MCP_PORTNo3002HTTP server port (HTTP mode only)
CENOGRAM_CLIENT_IDNoauto-generatedPersistent client identifier

You can also use the --http CLI flag instead of MCP_TRANSPORT=http.

Tips

  • Model selection: For best results, use Claude Opus 4.7. It makes more sequential tool calls and produces richer analysis. You can switch the model in the dropdown at the bottom of the chat window.

Example Prompts

Polish:

  • "Jaka jest mediana cen mieszkan w Krakowie w 2025?"
  • "Pokaz transakcje z ulicy Pulawskiej 15 na Mokotowie"
  • "Znajdz transakcje na dzialce 126104_9.0015.201"
  • "Sprawdz plan miejscowy i ryzyko powodziowe dla dzialki 126104_9.0015.201"
  • "Znajdz transakcje gruntow w promieniu 5km od centrum Wroclawia powyzej 500 000 PLN"
  • "Porownaj ceny mieszkan na Mokotowie i Woli"
  • "Pokaz rozklad cen nieruchomosci w Polsce"

English:

  • "What's the median apartment price in Krakow in 2025?"
  • "Show transactions at Pulawska 15 in Mokotow"
  • "Find all transactions on parcel 126104_9.0015.201 and then search nearby"
  • "Check the zoning and flood risk for parcel 126104_9.0015.201"
  • "Find land transactions within 5km of Wroclaw center above 500,000 PLN"
  • "Compare apartment prices in Mokotow and Wola districts"
  • "Show the price distribution of real estate in Poland"

Tools

ToolDescriptionKey Parameters
search_transactionsSearch transactions with filterslocation, street, buildingNumber, parcelId, propertyType, marketType, price/date/area range
get_price_statisticsPrice/m2 stats by location (residential only)location (optional)
get_price_distributionPrice histogrambins, maxPrice
search_by_areaSearch transactions by geographic radiuslatitude, longitude, radiusKm
get_market_overviewDatabase overview and stats(none)
list_locationsList available locationssearch (optional)
search_parcelsSearch parcels by cadastral ID prefixq (parcel ID prefix, min 3 chars)
list_parcels_in_areaList the cadastral parcels in an area - light list or full outlinesteryt, location, bbox, lat + lng + radiusKm, or polygon; includeGeometry, minArea/maxArea, street/buildingNumber, cursor
search_by_polygonSearch transactions within a GeoJSON polygonpolygon, propertyType, dateFrom/dateTo
compare_locationsCompare stats across 2-5 districtsdistricts (comma-separated), propertyType
get_building_breakdownPer-building breakdown for one transaction (footprint, storeys, est. floor area)transaction_id (UUID from a search result)
get_parcel_reportComposite dossier for one parcel: core, 13 enrichment layers, transaction history, local price context and municipal contextparcelId (cadastral id or UUID)
resolve_parcelResolve a parcel to its cadastral identityparcelId, q (full cadastral id or 'locality + parcel number' - not a street address), or lat + lng
get_demographicsPopulation and demographic context for a locationlocation or teryt, year (or yearFrom/yearTo), category
get_infrastructure_signalsMunicipal infrastructure signals (tenders, utilities, capital spending)location or teryt
estimate_valueComparable-sales value estimate for a propertyarea, plus lat + lng or parcelId; rooms, market
get_transaction_floodFlood risk for the property in a transactiontransaction_id (UUID from a search result)
get_transaction_heritageHeritage-register status for the propertytransaction_id
get_transaction_landslideLandslide risk for the propertytransaction_id
get_transaction_surroundingsNuisance and land-use context around the propertytransaction_id
get_transaction_transitPublic transport accessibility for the propertytransaction_id
get_transaction_permitsBuilding permits recorded for the propertytransaction_id
get_transaction_planningLocal zoning and planning status for the propertytransaction_id
get_transaction_farmlandAgricultural land-use classification for the propertytransaction_id
get_transaction_natureNearby forest and overlapping protected natural areas for the propertytransaction_id
get_transaction_subsurfaceMining terrains and major groundwater reservoirs under the propertytransaction_id
get_transaction_roadsGeometric evidence of road access for the property (distances, road class, access indicator)transaction_id

Location naming

  • Most cities: use the city name directly (e.g., "Gdansk", "Lublin")
  • Warsaw: "Warszawa" covers all 18 districts at once; name one ("Mokotow", "Srodmiescie", "Wola") to narrow it down
  • Krakow and Lodz work the same way: the city name covers every sub-district, or name one ("Krakow-Podgorze")
  • Neighbourhood names are not administrative units - search by radius or polygon instead
  • Use list_locations to find valid names

Property types

ValuePolishEnglish
landGruntLand plot
buildingBudynekBuilding
developed_landGrunt zabudowanyDeveloped land
unitLokalApartment/unit

Workflows

Results include parcel IDs and GPS coordinates, enabling multi-step research:

1. Search by address    -> search_transactions(location="Mokotow", street="Pulawska", buildingNumber="15")
2. Note parcel_id and coordinates from results
3. Search nearby        -> search_by_area(lat=52.19, lng=21.01, radiusKm=2, propertyType="unit")
4. Compare prices       -> get_price_statistics(location="Mokotow")

This mimics how a property appraiser finds comparable transactions for valuation reports.

Starting from the land rather than from a deed is a different route:

1. List the parcels     -> list_parcels_in_area(location="Wawer", minArea=800)
2. Draw the ones you want -> list_parcels_in_area(bbox="21.10,52.20,21.14,52.23", includeGeometry=true)
3. Open one in full     -> get_parcel_report(parcelId="146518_8.0108.27")

Step 1 pages by cursor; step 2 is capped and usually truncated, so narrow the box rather than reading a truncated answer as the parcel list of the area.

Data

  • 8M+ transactions from all of Poland (380 counties)
  • Date range: 2003 - present
  • Source: Polish national RCN registry (Rejestr Cen Nieruchomosci)
  • Refresh: periodic updates from RCN
  • Per-parcel context: zoning, flood and landslide risk, heritage register, building permits and construction activity, transit access, agricultural land use, surroundings, nature (nearby forest and protected areas), subsurface (mining terrains and major groundwater reservoirs), land-use and soil-quality classification, and road access - addressable by cadastral ID

Troubleshooting

"Error: CENOGRAM_API_KEY is required" - This only applies to stdio mode. Make sure CENOGRAM_API_KEY is set in the env block of your MCP config. For HTTP remote, the key goes in the Authorization header instead.

npx hangs or fails - Check your Node.js version with node -v. The stdio mode requires Node.js >= 18. If you're on an older version, use the HTTP remote option instead (no Node.js needed).

A location returns 0 results - The name may not be an administrative unit. Districts and neighbourhoods are two different things: "Mokotow" is a district and works, "Sluzew" is a neighbourhood inside it and does not. Use list_locations(search="...") to find valid names, or search by radius (search_by_area) for anything smaller than a district.

401 Unauthorized (HTTP mode) - The Authorization header must be Bearer cngrm_... (with the Bearer prefix). Double-check that the full API key is included, not just the prefix.

402 Payment Required - The account is out of tokens. On a free account the response says the date from which the balance is back at its weekly 50; the key and the connection stay valid until then. A paid plan lifts the limit - see cenogram.pl/api.

Development

git clone https://github.com/cenogram/mcp-server.git
cd mcp-server
npm install
npm test
npm run build

License

MIT