LibraryAPI vs Ban Fr — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
LibraryAPI vs Ban Fr
In-depth architectural comparison of the LibraryAPI and Ban Fr MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
LibraryAPI
Location Services · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Ban Fr
Location Services · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose LibraryAPI if you need specialized Location Services tools running via a local process. Choose Ban Fr if your workspace requires Location Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose LibraryAPI when:
You need dedicated capabilities in the Location Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
LibraryAPI is categorized under Location Services and uses a local stdio subprocess. In contrast, Ban Fr belongs to Location Services using local stdio subprocess. Select LibraryAPI when you need capabilities focused on location services and Ban Fr when you require tools for location services.
Forward-geocode a French address, street, locality or commune. Returns scored GeoJSON matches (score 0-1) with label, coordinates, postcode, citycode (INSEE) and context. France only.
reverse_geocode
Reverse-geocode a coordinate to the nearest French address/feature. Returns scored GeoJSON matches with label, postcode, citycode (INSEE), context and distance (metres). France only.
search_municipality
Look up a French commune (municipality) by name to resolve its INSEE citycode, postcode, population and centre coordinates. Shortcut for geocode with type=municipality.