mcp-commune-france
# mcp-commune-france
MCP server for French commune intelligence: geo.api.gouv.fr, postal codes, departments, regions, and dataset discovery.
## Tools
Run the MCP and call `commune_france_get_sources` first to inspect source coverage. This server also exposes domain-specific tools for the topic described above.
Includes commune resolution, department commune lists, commune profiles, BAN address geocoding, and address-to-commune profiles.
## Install
```bash
npm install
npm run build
npm test
npm run dev
```
## Claude Desktop
```json
{
"mcpServers": {
"commune-france": {
"command": "npx",
"args": ["mcp-commune-france"]
}
}
}
```
## Sources
- geo.api.gouv.fr: https://geo.api.gouv.fr/
- data.gouv.fr API: https://doc.data.gouv.fr/api/reference/
- BAN: https://adresse.data.gouv.fr/
- INSEE official statistics: https://www.insee.fr/
## Publishing
See [docs/publishing.md](docs/publishing.md).
## Glama / Docker
The repo includes `Dockerfile` and `glama.json`.
Build steps:
```json
["npm install", "npm run build"]
```
CMD arguments:
```json
["node", "dist/index.js"]
```
## Safety
This MCP helps agents discover and summarize public sources. It is not an official authority. Verify decisions against the competent public service or original data producer.
## License
MIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: source list, source excerpt, commune resolution, department listing, and profile building. No overlap exists between finding a specific commune and listing all communes in a department, and the profile combines earlier data without redundancy.
All tools share the 'commune_france_' prefix and follow a verb_noun pattern (get, fetch, find, list, profile). The only deviation is 'profile' as a noun, but it functions as a verb-like action and remains uniform with the prefix, making the pattern predictable.
Five tools is well within the optimal range for a focused server. Each tool covers a discrete part of the domain—sources and commune data—without unnecessary expansion or redundancy.
The server covers its stated purpose completely: retrieving source metadata, fetching excerpts, resolving communes, listing department communes, and building a composite profile. There are no obvious missing operations for a read-only, data-retrieval service.