IGN API Carto MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (http mode only) | 3000 |
| TRANSPORT | No | Transport mode (stdio or http) | stdio |
| IGN_API_KEY | No | Your IGN API key for accessing AOC viticoles endpoint. Obtain a free key at https://geoservices.ign.fr/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ign_get_communes_by_postal_codeA | Retrieve French communes (municipalities) associated with a postal code. This tool queries the IGN API Carto codes-postaux module to find all communes that share a given postal code. In France, a postal code can cover multiple communes, and this tool returns all of them. Args:
Returns: For JSON format: [ { "codePostal": "75001", "codeCommune": "75101", "nomCommune": "Paris 1er Arrondissement", "libelleAcheminement": "PARIS" } ] Examples:
|
| ign_get_cadastre_parcellesA | Search for cadastral parcels (land plots) in France. This tool queries the IGN API Carto cadastre module to find parcels by geometry intersection or administrative codes. Useful for property identification, urban planning, and administrative procedures. Args:
Returns: GeoJSON FeatureCollection with parcel geometries and properties including:
Examples:
|
| ign_get_cadastre_communesA | Get commune (municipality) boundaries from the cadastral database. Args:
Returns: GeoJSON FeatureCollection with commune boundaries. |
| ign_get_rpgA | Query the Registre Parcellaire Graphique (RPG) for agricultural parcel information. The RPG contains agricultural land use data declared by farmers for CAP (Common Agricultural Policy) subsidies. Two versions exist:
Args:
Returns: GeoJSON FeatureCollection with:
Examples:
|
| ign_get_nature_areasA | Query protected natural areas in France (Natura 2000, ZNIEFF, national parks, etc.). Available layers:
Args:
Returns: GeoJSON FeatureCollection with protected area boundaries and attributes. Examples:
|
| ign_get_gpu_urbanismeA | Query the Géoportail de l'Urbanisme (GPU) for urban planning documents and zones. This tool accesses French urban planning data including local urban plans (PLU), zoning, and public utility easements. Available layers:
Args:
Returns: GeoJSON FeatureCollection with urban planning data. Examples:
|
| ign_get_aoc_viticolesA | Query wine appellation zones (AOC, IGP, VSIG) in France. This tool accesses wine appellation data maintained by FranceAgriMer based on INAO data. Args:
Returns: GeoJSON FeatureCollection with appellation zones including:
Examples:
Note: This endpoint requires an IGN API key. Get one for free at https://geoservices.ign.fr/ |
| ign_wfs_geoportailA | Generic query interface for Geoportail WFS layers. This tool provides access to various WFS layers from the IGN Geoportail. It allows querying any WFS layer by intersection with a geometry. Args:
Returns: GeoJSON FeatureCollection with features from the requested layer. Note: Only WGS84 (EPSG:4326) geometries are supported. Examples:
|
| ign_get_administrative_limitsA | Query French administrative boundaries (communes, departments, regions). This tool accesses administrative limit data from the IGN Admin Express dataset. Args:
Note: Either provide geom OR (lon + lat), but not both. Returns: GeoJSON FeatureCollection with administrative boundaries. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes targeting specific French geospatial datasets (e.g., administrative boundaries, cadastral parcels, wine appellations, urban planning), with clear separation by domain. However, some overlap exists between ign_get_administrative_limits and ign_get_cadastre_communes (both provide commune boundaries), and ign_wfs_geoportail is a generic tool that could duplicate functionality of others, potentially causing confusion.
All tool names follow a consistent 'ign_get_*' or 'ign_wfs_*' pattern with snake_case, clearly indicating the server (IGN) and action (get/wfs). The naming is highly predictable and uniform across all nine tools, making it easy for agents to understand the pattern and purpose.
With 9 tools, the count is well-scoped for a French geospatial API server, covering diverse datasets like administrative limits, cadastre, wine appellations, urban planning, and natural areas. Each tool serves a specific niche, and the number is neither too thin nor overwhelming for the domain.
The toolset provides comprehensive coverage for querying French geospatial data, including administrative, cadastral, agricultural, urban, and environmental layers. Minor gaps exist, such as no explicit tools for updating or deleting data (likely read-only by design) and some redundancy with the generic WFS tool, but core query workflows are well-supported.