# Changelog of France Map MCP Server: cadastre and PLU data (`mrbridge/france-map-mcp-server`) Actor

- **URL**: https://apify.com/mrbridge/france-map-mcp-server/changelog.md
- **Full Actor documentation**: https://apify.com/mrbridge/france-map-mcp-server.md

## Changelog

### v0.1.4 (2026-07-02)

#### Added

- Added the `commune_profile` MCP tool for one-call commune summaries: reusable commune geometry, parcel totals, section breakdown, RPG rollup, and zoning families.

#### Changed

- Deprecated direct `lookup_cadastre(layer="division")` behavior in favor of a derived rollup from `cadastre_parcelle`.
- `lookup_administrative_boundaries` now returns a reusable commune GeoJSON feature when `includeGeometry=true`.

#### Fixed

- Declared GPU pagination parameters in the APICarto endpoint registry so GPU layer calls can be limited consistently.

### v0.1.3 (2026-07-02)

#### Changed

- Reworked the Input tab into an MCP setup guide aligned with the Vivino MCP Server pattern.

### v0.1.2 (2026-07-02)

#### Added

- Added a dataset schema view for Apify Task example publication and MCP response previews.

### v0.1.1 (2026-07-01)

#### Added

- Added Apify pay-per-event monetization for APICarto data retrieval and multi-layer site analysis MCP tool calls.
- Added Store pricing copy aligned with the Actor Pricing tab.

### v0.1.0 (2026-06-30)

#### Added

- Initial France Map MCP Server release for APICarto-backed French map, cadastre, administrative, urban-planning, environmental, agricultural, road, and postal-code analysis.
- Added 10 MCP tools for endpoint discovery, raw APICarto queries, postal-code lookup, administrative boundaries, cadastre, urbanism diagnostics, environmental diagnostics, RPG agriculture, nearby roads, and site context reports.
- Added Apify publication metadata, Store README, input schema, output schema, OpenAPI web-server schema, and Standby MCP configuration at `/mcp`.

#### Changed

- Renamed the Actor to `France-Map-MCP-Server` for publication.

#### Security & privacy

- MCP authentication is handled by Apify API tokens at the platform edge; no user token is stored in the Actor source.