io.github.woonstadrotterdam/monumenten
OfficialThis MCP server converts Dutch addresses to BAG verblijfsobject IDs and checks their monumental heritage status.
Find BAG verblijfsobject IDs from an address using postal code + house number, or street + house number + city, with optional house letter and suffix support.
Handle address variations such as
1234AB 30,30-2,30A, and full street addresses.Return structured address matches, including whether a match is a nevenadres.
Check monumental status for a 16-digit verblijfsobject ID: rijksmonument, rijksmonument voorbescherming, rijksbeschermd stads-/dorpsgezicht, gemeentelijk monument, and provinciaal monument.
Include supporting details such as province, monument number, URL, source, and provincial monument description when available.
Distinguish undetermined from false:
nullmeans the status could not be determined, not that the property is not a monument.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.woonstadrotterdam/monumenten Is Coolsingel 30 in Rotterdam a rijksmonument?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Monumenten MCP Server 🏛️
A Model Context Protocol (MCP) server that enables AI assistants to check monumental status of Dutch addresses relevant for woningwaardering (rent-point system). Connects to the Dutch BAG (Basisadministratie Adressen en Gebouwen) data and Ministry of Cultural Heritage (Rijksdienst voor het Cultureel Erfgoed) to identify national monuments, nationally protected cityscapes, and municipal monuments.
Built on the MCP Python SDK v2 (MCPServer). Tools return structured results; validation and lookup failures raise ToolError (is_error=true) so the model can retry.
Requires Python 3.11+.
This MCP server is based on themonumenten package. For more information, see the monumenten package.
What This Does
This MCP server allows AI assistants to:
🏠 Find verblijfsobject IDs - Convert Dutch addresses to BAG identifiers (
verblijfsobject_id)🏛️ Check monumental status - Determine if a property is protected as cultural heritage
📍 Support flexible address input - Search by postal code + house number or full address
🔍 Handle address variations - Support house letters and suffixes (30A, 30-2, etc.)
Available Tools
Tool | Parameters | Result |
|
| Structured |
|
| Structured monumental status (provincie, rijksmonument, voorbescherming, rijksbeschermd stads-/dorpsgezicht, municipal and provincial monument; |
Related MCP server: Dutch-law-mcp
Quick Setup
Add to your AI assistant's MCP configuration:
{
"mcpServers": {
"monumenten": {
"command": "uvx",
"args": ["mcp-monumenten"]
}
}
}For local development:
{
"mcpServers": {
"monumenten": {
"command": "uv",
"args": ["run", "--project", "/path/to/mcp-monumenten", "mcp-monumenten"]
}
}
}Streamable HTTP (mcp-monumenten --http) listens on http://127.0.0.1:8000/mcp by default.
Claude Code plugin
Requires uv. Then:
/plugin marketplace add woonstadrotterdam/mcp-monumenten
/plugin install monumenten@woonstad-rotterdamOr add the server directly: claude mcp add monumenten -- uvx mcp-monumenten.
OpenAI Codex plugin
Requires uv. Then:
codex plugin marketplace add woonstadrotterdam/mcp-monumentencodex plugin add monumenten@woonstad-rotterdamIn the ChatGPT desktop app you can instead install Monumenten from the Woonstad Rotterdam marketplace in the Plugins Directory.
Gemini CLI extension
Requires uv. Run outside an interactive session, then restart Gemini CLI:
gemini extensions install https://github.com/woonstadrotterdam/mcp-monumentenUpdate later with gemini extensions update monumenten.
GitHub Copilot CLI plugin
Requires uv. Then:
copilot plugin marketplace add woonstadrotterdam/mcp-monumentencopilot plugin install monumenten@woonstad-rotterdamThe repo ships one portable Agent Plugins manifest (plugin.json + mcp.json) that Codex and Copilot CLI both read. Gemini CLI reads gemini-extension.json; every client picks up the same skills/monumenten skill.
Usage Examples
Finding Monumental Status
"What is the monumental status of Coolsingel 30, Rotterdam?"
The AI will:
Convert the address to a BAG verblijfsobject ID
Check monument registries
Report rijksmonument status, rijksbeschermd stads-/dorpsgezicht, or municipal or provincial monument designation
"Is 1234AB 30-2 a rijksmonument?"
The AI can handle:
Postal code + house number format
House number suffixes (30-2, 30A, etc.)
Direct verblijfsobject ID lookups
Address Flexibility
The server handles Dutch address formats:
1234AB 30- Basic postal code + house number1234AB 30-2- With house number suffix1234AB 30A- With house letterCoolsingel 30, Rotterdam- Full street address
Installation
Via uvx (Recommended)
uvx mcp-monumentenLocal Development
git clone https://github.com/woonstadrotterdam/mcp-monumenten.git
cd mcp-monumenten
uv sync
uv run --project . mcp-monumentenData Sources
Kadaster - BAG (Basisadministratie Adressen en Gebouwen) - Official Dutch address registry, queried through the PDOK BAG WFS (
bag:verblijfsobjectlayer) to turn an address into a verblijfsobject ID. The layer only has hoofdadressen of verblijfsobjecten, so ligplaatsen and standplaatsen return no match.PDOK Locatieserver - Current provincie of a verblijfsobject. When the WFS finds no hoofdadres, it also finds nevenadressen (returned with
nevenadres: true) and lists the huisletter and toevoeging variants that exist for the house number in the errorRCE (Rijksdienst voor het Cultureel Erfgoed) - National monuments registry
Provinces Noord-Holland and Drenthe - Provincial monuments, from their map services
When a source does not answer
A status that could not be determined is null, never false. If a source (RCE, BAG or BRK-PB) does not answer at all, get_monumental_status returns a tool error naming the source. If only a provincial service is down, the call succeeds and provinciaal_monument is null for addresses in Noord-Holland and Drenthe.
License
MIT License - see LICENSE file for details.
Available Tools
2 toolsget_monumental_statusARead-only
Get the monumental status of a verblijfsobject.
Always mention the source for the Rijksmonument status if it is a Rijksmonument. (RCE = Rijksdienst voor het Cultureel Erfgoed.) Reply in the user's language. A status that is null could not be determined because a source did not answer: say so, never report it as false. rijksmonument_voorbescherming is not a rijksmonument.
Inputs: bag_verblijfsobject_id (required). Returns: Monumental status for one verblijfsobject.
get_verblijfsobject_idARead-only
Get verblijfsobject ID using address.
Use postal_code + house_number OR street + house_number + city. Additional filters like house_letter and house_suffix can be provided for more precise matching.
Inputs: house_number (required), city, street, postal_code, +2 more. Returns: Address lookup result from the PDOK BAG WFS and Locatieserver.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools form a clean sequential pipeline: one resolves an address into a verblijfsobject ID, the other consumes that ID to fetch monumental status. There is no overlap in inputs or purpose, so misselection is essentially impossible.
Both tools follow the same snake_case get_<resource> convention (get_verblijfsobject_id, get_monumental_status). Naming is fully predictable for any additional lookup added later.
Two tools is thin even for a narrow lookup server; the surface is just a two-step chain with no search, listing, or batch variants. It is defensible for the tightly scoped purpose, but it sits at the borderline of being under-provisioned.
The address-to-ID-to-status path works end to end, but there are notable gaps: no direct address-to-status call, no reverse lookup (monuments by ID or area), and no way to enumerate or search monuments. Agents can complete the primary workflow only by chaining both tools in a fixed order.
Maintenance
Related MCP Connectors
Dutch address data for AI assistants: BAG building facts, energy labels, reviewed crime signals.
Dutch building and soil data lookup: BAG/3DBAG buildings, BRO soil investigations, wind zones
Live Dutch open data for AI assistants: transport, weather, water, traffic, housing, government.
Nederlandse open geodata (BAG, BGT, Kadaster, RVO) als MCP-tools voor AI-assistenten.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language search and exploration of the Dutch WWII Oorlogsbronnen archives, allowing users to query historical documents, photographs, and personal accounts through AI assistants.15MIT
- AlicenseAqualityFmaintenanceEnables querying over 3,200 Dutch statutes (AVG, Wetboek van Strafrecht, Burgerlijk Wetboek, etc.) with verbatim, citation-grounded text from official sources, directly from MCP-compatible AI assistants.1849 npm15Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables querying Dutch property context for an address, returning building, energy, neighborhood, environment, heritage, and school data from public registers, with explicit match verification and signals.MIT

GetApi MCP Serverofficial
AlicenseCqualityBmaintenanceEnables AI clients to call a broad set of Dutch data and validation API endpoints as tools, including address, postcode, IP, DNS, IBAN/VAT, vehicle, and property lookups, with secure API-key handling and automatic tool-list updates.30MIT