Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data
Model Context Protocol server for Italian cadastral, geospatial and realestate data, powered by the Zornade API v2.
Add it to any MCP client (Claude, Cursor, VS Code Copilot, Cline, ...) and askquestions about Italian properties in natural language: geocoding, cadastralparcels, risk layers, valuations, solar potential, administrative lists.
Endpoint
https://mcp.zornade.com/mcp
Authentication
A free Zornade API key (zrn_...) fromhttps://app.zornade.com/api is required. Send itas x-api-key header, Authorization: Bearer, or ?api_key= query parameter.Rate limits and scopes are the ones of your key (10,000 requests/hour).
Tools
| Tool | Description |
|---|---|
zornade_geocode_search |
Forward geocoding on 18.7M+ Italian addresses (ANNCSU) |
zornade_geocode_reverse |
Reverse geocoding by WGS84 coordinates |
zornade_parcel_by_id |
Enriched cadastral parcel profile (risk, economics, solar, valuations, POI, ...) |
zornade_parcel_locate |
Parcels by point, multiple points, or bounding box |
zornade_parcel_search |
Parcels by comune, foglio, label |
zornade_admin_lists |
Regions, provinces, municipalities |
Connect
Claude Code:
claude mcp add zornade -t http https://mcp.zornade.com/mcp \
--header "x-api-key: zrn_YOUR_KEY"
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"zornade": {
"type": "http",
"url": "https://mcp.zornade.com/mcp",
"headers": { "x-api-key": "zrn_YOUR_KEY" }
}
}
}
Cursor: Add to Cursor,or in .cursor/mcp.json (project) / ~/.cursor/mcp.json (global):
{
"mcpServers": {
"zornade": {
"url": "https://mcp.zornade.com/mcp",
"headers": { "x-api-key": "zrn_YOUR_KEY" }
}
}
}
VS Code, Cline and other clients that read the standard mcpServers shape usethe same JSON as Cursor.
Clients that only speak stdio
Some clients accept only a command to launch locally, not a remote url entry.For those, use the npm bridge: it starts on your machine and speaks tohttps://mcp.zornade.com/mcp on your behalf.
{
"mcpServers": {
"zornade": {
"command": "npx",
"args": ["-y", "@zornade/mcp"],
"env": { "ZORNADE_API_KEY": "zrn_YOUR_KEY" }
}
}
}
The bridge does two things a generic stdio-to-HTTP proxy cannot. It passes--protocol auto, so it probes server/discover and, finding a 2026-07-28server, answers the legacy initialize handshake itself and rewrites thefollowing requests for the modern era. And it takes the key fromZORNADE_API_KEY and sends it as x-api-key:VALUE with no space after thecolon, which is the form that survives the argument escaping bug in Cursor,Codex-CLI and Claude Desktop on Windows.
Without a key the OAuth flow starts instead: the server mints a personal key onfirst connection.
Package source lives in npm/, and the package page isnpmjs.com/package/@zornade/mcp.
Test
curl -X POST https://mcp.zornade.com/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "x-api-key: zrn_YOUR_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Example
A typical conversation, from natural language to a structured answer:
- The user asks: "Is this parcel at risk of flooding, and what is it worth?"
- The agent calls
zornade_geocode_searchwith{ "query": "via del corso 1, roma" },thenzornade_parcel_by_idwith the returnedfid. - The answer comes back as compact JSON with English field names:
{
"fid": 28007851,
"municipality": { "code": "H501", "name": "Roma", "province": "Roma", "region": "Lazio" },
"cadastral": { "foglio": "481", "urban_section": null, "municipality_code": "H501", "postal_code": "00186" },
"risk": { "seismic_zone": 3, "pga": 0.058, "flood_level": null, "landslide_level": null },
"subsidence": { "velocity_mm_year": -0.8, "risk_class": 1, "risk_label": "negligible", "direction": "stable" },
"economics": { "avg_residential_price_m2": 6283.33, "tax_year": 2023 },
"meta": { "licenses": ["..."], "zornade_attribution_required": true }
}
(abridged for brevity; geometry is omitted from tool replies). Field names areEnglish across the API (area_m2, pga, risk_label, ...). One note fortooling that scans this file: meta.zornade_attribution_required is a field ofthe API response, not a tool. The tool names are the six listed above andnothing else.
A few official cadastral terms stay in Italian on purpose (foglio,sezione), and values like street, municipality and region names are propernames and stay as they are.
Architecture
functions/mcp/dispatch.ts- the protocol, in one place: JSON-RPC dispatch(server/discover,initialize,ping,tools/list,tools/call),version negotiation and result envelopes. Written against the 2026-07-28revision instead of an SDK because the published libraries do not serve it:mcp-litestops at 0.10.0 (Nov 2025), and@modelcontextprotocol/server2.4.0 declaresLATEST_PROTOCOL_VERSION = 2025-11-25despite its README.functions/mcp/index.ts- Supabase Edge Function (Deno) with Hono. Auth(API key, Bearer, query, OAuth 2.1), 401 withWWW-Authenticate, JSON or SSEdepending on what the client accepts.functions/mcp/tools.ts- tool definitions shared by both transports, withtitleandannotations(readOnlyHint,idempotentHint,openWorldHint).functions/mcp/stdio.ts- stdio entrypoint, used by the Docker image and bywrapper tools that spawn a child process. It runs the same dispatcher, sodirectory validators exercise the same code as HTTP clients.netlify.toml+public/- Netlify reverse proxy for the clean hostnamemcp.zornade.com(no build step).
Distribution
| Where | Entry |
|---|---|
| Official MCP Registry | io.github.zornade/zornade-mcp, from server.json in this repo |
| npm | @zornade/mcp, source in npm/ |
| Glama | |
| public-apis | MCP Servers table, pull request open |
The registry manifest is republished after every version bump:
mcp-publisher validate # offline check against the published schema
mcp-publisher publish # requires `mcp-publisher login github` once
Publishing the npm bridge
The package is a thin wrapper over mcp-remote, so it needs a release only whenthe wrapper changes, not when the server does.
Two ways to publish, both documented because the first one has three traps.
From a workstation, npm publish in npm/. The account needs 2FA enabled:npm refuses to publish without it, and its 2FA is security-key only (Touch ID,Face ID, Windows Hello, YubiKey), not a six digit code. Each publish raises itsown challenge, so the one you answered when enabling 2FA does not carry over.publishConfig.access is set to public in package.json because without it ascoped package is treated as private on first publish and the registry answers402 Payment Required.
From CI, push a tag matching npm-v*. .github/workflows/publish-npm.ymlpublishes through OIDC trusted publishing, checks that npm is at least 11.5.1 andthat the tag equals package.json, and needs no token. Configure the trustedpublisher on the package page first, and note two things: a fresh configurationexpires if it does not complete its first publish within 2 days, andconfigurations created after 3 September 2026 allow only npm stage publishunless the permission for direct npm publish is ticked.
Never tag npm-v1.0.0 for an already published version: the workflow runs andfails on the duplicate.
After a publish, the full registry document answers immediately while theabbreviated one that npm install uses can lag for a few minutes. A 404 fromregistry.npmjs.org/@zornade%2fmcp right after publishing is not necessarily afailed publish: check dist-tags in the full document. The registry also leavesa 0.0.0-stage placeholder version behind, described as "Temporary packageplaceholder for staged publishing". It is npm's own object and does not affectlatest.
Documentation
- API docs: api.zornade.com
- API keys: app.zornade.com/api
- Main site: zornade.com
Known limitations
- The transport is stateless by design, as the 2026-07-28 revision requires.There are no SSE sessions and no
Mcp-Session-Id: a GET on the endpointanswers 405 with anAllow: POST, OPTIONSheader. - Protocol revisions served: 2026-07-28, 2025-11-25 and 2025-06-18. Modernclients start with
server/discover; older clients still get a workinginitializeanswer, which is the dual-era behaviour the specificationallows. - Tool responses are text-only: geometries are omitted to keep the LLMcontext light.
- Tool calls require a free Zornade API key. Direct API v2 calls are theright tool for batch pipelines, see api.zornade.com.
Costs
Reading is free: a Zornade API key allows 10,000 requests per hour and you cankeep five keys per account. The server itself is MIT, so it can also beself-hosted from this repository.
A commercial license, from 490 EUR per year, removes the "Dati elaborati daZornade" attribution for products that embed the data. Source attributions staymandatory in every case. Product page and plans: https://zornade.com/mcp/
License
Two distinct layers:
- Server code: MIT. Free to use, modify and redistribute, also forcommercial purposes. The full text is in
LICENSE. - Data: licenses of the original sources, which remain in force for everyconsumer of the API and of this server. Key ones:
- cadastral parcels and cadastral data: Agenzia delle Entrate (free reuse,attribution required)
- addresses: ANNCSU, ISTAT and Agenzia delle Entrate (CC BY 4.0, partlyCC BY 3.0 IT)
- buildings and map layers: OpenStreetMap (ODbL 1.0)
- risk and environmental layers: ISPRA, INGV, Copernicus (CC BY 4.0 /Copernicus Data Policy)
- solar potential: PVGIS-SARAH3, JRC European Union (free reuse)
- real estate market data: OMI and MEF (free reuse)
Every API response lists the applicable licenses in meta.licenses and therequired attribution text. Two attribution levels exist: source attributionsare always mandatory; the "Dati elaborati da Zornade" attribution with link tozornade.com is required for free plan keys and can be waived with acommercial license(the response field meta.zornade_attribution_required tells you which ruleapplies). Full data terms: zornade.com.