Filesystem vs OpenStreetMap
A side-by-side look at the Filesystem and OpenStreetMap MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose OpenStreetMap for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Choose OpenStreetMap when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
geocode, reverse_geocode, route.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | Location Services |
| Quality signal | 85/100 · Excellent | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | 4 |
| Directory activity | 9 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 11 |
| Full listing | View Filesystem | View OpenStreetMap |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
OpenStreetMap tools 11
geocodeConverts a place name or address into coordinates using OpenStreetMap. Returns matching places with lat/lon, a display label and the OSM id. Provider "nominatim" (default) is best for addresses; "photon" is typo-tolerant and better for fuzzy place names.reverse_geocodeConverts coordinates into the nearest address or place name (Nominatim).routeCalculates the real-world travel distance and time between two or more places, walking, driving or cycling, on OpenStreetMap data. Waypoints are visited in the given order. Set include_steps for a turn-by-turn summary. Use route_matrix to compare many pairs, optimize_route to reorder stops.route_matrixComputes travel times and distances from every origin to every destination in one call — ideal for comparing options (e.g. 5 hotels against 3 sights). Cells are null where no route exists.optimize_routeFinds the best order to visit a set of stops (traveling-salesman optimization) and returns the optimized itinerary with total distance and time. With roundtrip (default) the tour returns to the first stop; without it the first stop is the start and the last stop the end.isochroneShows how far you can get from a place within a time or distance budget ("what is reachable in 15 minutes on foot?"). Returns a compact summary of the reachable area: bounding box and reach per compass direction. Give exactly one of minutes or kilometers.find_nearby_poisFinds points of interest near a location, sorted by distance. Category shortcuts: restaurant, cafe, bar, pub, fast_food, ice_cream, hotel, hostel, guest_house, apartment, camp_site, attraction, museum, gallery, viewpoint, information, artwork, castle, monument, ruins, supermarket, bakery, convenience, pharmacy, hospital, doctors, police, atm, bank, fuel, charging_station, parking, toilets, drinking_water, bus_stop, train_station, tram_stop, ferry_terminal, bicycle_rental, car_rental, playground, park, beach, swimming_pool. Any other OSM tag works as "key" or "key=value" (e.g. "diet:vegan=yes"). Use poi_details for the full record of one result.poi_detailsFetches the full OpenStreetMap record of one element — all tags (opening hours, website, phone, …), coordinates and a map link. Takes an OSM id as returned by find_nearby_pois or geocode, e.g. "node/240109189".suggest_meeting_pointSuggests a fair place to meet for people starting from different locations: finds venues around the geographic midpoint and picks the one with the most balanced travel times for everyone.straight_line_distanceGreat-circle ("as the crow flies") distance between two places. Instant and independent of any road network — use route for real travel distances.map_linkGenerates openstreetmap.org links to open in a browser: a marker link for a single place, or a directions link when from and to are given. Provide either "place", or both "from" and "to".
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
OpenStreetMap
{
"mcpServers": {
"openstreetmap": {
"command": "npx",
"args": [
"-y",
"osm-mcp"
]
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. OpenStreetMap belongs to Location Services and uses a local stdio subprocess. Pick Filesystem for file systems work and OpenStreetMap for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Filesystem is listed as free. Auth: no auth required. OpenStreetMap has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add filesystem and openstreetmap as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 85/100 (Excellent) with 9 views, 0 installs and 91,512 GitHub stars. OpenStreetMap has 63/100 (Good) with 1 views, 0 installs and 4 GitHub stars.