Skip to main content
Glama
Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data

Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data

Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data MCP server – quality and maintenance score on Glama

Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data

Model Context Protocol server for Italian cadastral, geospatial and real estate data, powered by the Zornade API v2.

Add it to any MCP client (Claude, Cursor, VS Code Copilot, Cline, ...) and ask questions about Italian properties in natural language: geocoding, cadastral parcels, risk layers, valuations, solar potential, administrative lists.

Endpoint

https://mcp.zornade.com/mcp

Related MCP server: io.github.stucchi/italy-opendata

Authentication

A free Zornade API key (zrn_...) from https://app.zornade.com/api is required. Send it as 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 use the 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 to https://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-28 server, answers the legacy initialize handshake itself and rewrites the following requests for the modern era. And it takes the key from ZORNADE_API_KEY and sends it as x-api-key:VALUE with no space after the colon, 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 on first connection.

Package source lives in npm/, and the package page is npmjs.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:

  1. The user asks: "Is this parcel at risk of flooding, and what is it worth?"

  2. The agent calls zornade_geocode_search with { "query": "via del corso 1, roma" }, then zornade_parcel_by_id with the returned fid.

  3. 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 are English across the API (area_m2, pga, risk_label, ...). One note for tooling that scans this file: meta.zornade_attribution_required is a field of the API response, not a tool. The tool names are the six listed above and nothing else.

A few official cadastral terms stay in Italian on purpose (foglio, sezione), and values like street, municipality and region names are proper names 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-28 revision instead of an SDK because the published libraries do not serve it: mcp-lite stops at 0.10.0 (Nov 2025), and @modelcontextprotocol/server 2.4.0 declares LATEST_PROTOCOL_VERSION = 2025-11-25 despite its README.

  • functions/mcp/index.ts - Supabase Edge Function (Deno) with Hono. Auth (API key, Bearer, query, OAuth 2.1), 401 with WWW-Authenticate, JSON or SSE depending on what the client accepts.

  • functions/mcp/tools.ts - tool definitions shared by both transports, with title and annotations (readOnlyHint, idempotentHint, openWorldHint).

  • functions/mcp/stdio.ts - stdio entrypoint, used by the Docker image and by wrapper tools that spawn a child process. It runs the same dispatcher, so directory validators exercise the same code as HTTP clients.

  • netlify.toml + public/ - Netlify reverse proxy for the clean hostname mcp.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

glama.ai/mcp/servers/zornade/zornade-mcp

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 when the 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 its own 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 a scoped package is treated as private on first publish and the registry answers 402 Payment Required.

From CI, push a tag matching npm-v*. .github/workflows/publish-npm.yml publishes through OIDC trusted publishing, checks that npm is at least 11.5.1 and that the tag equals package.json, and needs no token. Configure the trusted publisher on the package page first, and note two things: a fresh configuration expires if it does not complete its first publish within 2 days, and configurations created after 3 September 2026 allow only npm stage publish unless the permission for direct npm publish is ticked.

Never tag npm-v1.0.0 for an already published version: the workflow runs and fails on the duplicate.

After a publish, the full registry document answers immediately while the abbreviated one that npm install uses can lag for a few minutes. A 404 from registry.npmjs.org/@zornade%2fmcp right after publishing is not necessarily a failed publish: check dist-tags in the full document. The registry also leaves a 0.0.0-stage placeholder version behind, described as "Temporary package placeholder for staged publishing". It is npm's own object and does not affect latest.

Documentation

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 endpoint answers 405 with an Allow: POST, OPTIONS header.

  • Protocol revisions served: 2026-07-28, 2025-11-25 and 2025-06-18. Modern clients start with server/discover; older clients still get a working initialize answer, which is the dual-era behaviour the specification allows.

  • Tool responses are text-only: geometries are omitted to keep the LLM context light.

  • Tool calls require a free Zornade API key. Direct API v2 calls are the right tool for batch pipelines, see api.zornade.com.

Costs

Reading is free: a Zornade API key allows 10,000 requests per hour and you can keep five keys per account. The server itself is MIT, so it can also be self-hosted from this repository.

A commercial license, from 490 EUR per year, removes the "Dati elaborati da Zornade" attribution for products that embed the data. Source attributions stay mandatory 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 for commercial purposes. The full text is in LICENSE.

  • Data: licenses of the original sources, which remain in force for every consumer 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, partly CC 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 the required attribution text. Two attribution levels exist: source attributions are always mandatory; the "Dati elaborati da Zornade" attribution with link to zornade.com is required for free plan keys and can be waived with a commercial license (the response field meta.zornade_attribution_required tells you which rule applies). Full data terms: zornade.com.

Available Tools

6 tools
zornade_admin_listsAInspect

Italian administrative reference data: regions, provinces, or municipalities. Provinces can be filtered by region; municipalities by province or region.

Inputs: type (required), region, province.

zornade_geocode_reverseAInspect

Reverse geocoding: find Italian addresses near WGS84 coordinates. Returns the closest ANNCSU addresses with distance in meters.

Inputs: lat (required), lng (required), limit, radius.

zornade_parcel_by_idAInspect

Enriched cadastral parcel profile by FID or GML ID. Returns municipality, area, cadastral reference, and the requested data sections (risk, subsidence, terrain, buildings, economics, demographics, valuation, valuation_history, solar, POI, etc.). Geometry is omitted to keep the reply compact.

Inputs: fid (required), include.

zornade_parcel_locateAInspect

Find cadastral parcels by coordinates or bounding box. Three modes: single point (lat+lng), multiple points (points="lat,lng;lat,lng", max 10), or bounding box (bbox="minLng,minLat,maxLng,maxLat", max 0.05 degrees per side). Returns matching parcels with FID, municipality and centroid.

Inputs: lat, lng, bbox, limit, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: forward vs reverse geocoding, parcel retrieval by ID vs spatial locate vs cadastral reference search, and administrative list lookup. No two tools overlap in purpose.

    Naming Consistency4/5

    All names follow a consistent snake_case pattern with the zornade_ prefix and a domain identifier (geocode, parcel, admin). However, the action parts mix verbs (search, locate) with noun-like descriptors (by_id, lists), so the convention is readable but not perfectly uniform.

    Tool Count5/5

    Six tools is well-scoped for a geocoding and cadastral data server. Each tool covers a distinct core capability without redundancy or bloat.

    Completeness4/5

    The surface covers key workflows: forward/reverse geocoding, parcel lookup by ID or spatial search, cadastral reference search, and admin reference data. The only minor gap is the deliberate omission of parcel geometry in by_id, but other tools compensate with centroids and bounding-box queries.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers