geocodage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeB | Géocode une chaîne de caractères (adresse, lieu ou parcelle cadastrale) via l'API Géoplateforme de l'IGN. Retourne une FeatureCollection GeoJSON. |
| geocode_reverseB | Géocodage inverse via l'API Géoplateforme de l'IGN : retourne les adresses/lieux/parcelles les plus proches d'un point géographique (lon/lat) ou d'une géométrie (cercle, polygone…). |
| geocode_capabilitiesA | Retourne les capacités de l'API Géoplateforme : opérations disponibles, index et champs interrogeables, catégories de POI, etc. |
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 3 tools
Each tool has a distinct purpose: forward geocoding, reverse geocoding, and API capabilities. No overlap.
All tool names follow the 'geocode' prefix with a descriptive suffix (geocode, geocode_reverse, geocode_capabilities), creating a predictable pattern.
Three tools is minimal but sufficient for a geocoding server, covering forward, reverse, and capabilities. Slightly on the low end but appropriate for the domain.
Essential geocoding operations (forward and reverse) are present, along with capabilities. Missing batch or autocomplete, but core workflow is covered.