Osm MCP Server

Osm MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for querying and validating OpenStreetMap tags.

What you get

This is a Model Context Protocol (MCP) server designed specifically for AI agents and LLM applications. It acts as a bridge between artificial intelligence systems and the comprehensive OpenStreetMap tagging knowledge base provided by the official @openstreetmap/id-tagging-schema library.

• Tag Query — (2 tools): Query tag values and search tags
• Preset Discovery — (2 tools): Search and explore OSM presets with detailed configurations
• Validation — (3 tools): Validate tags, check for deprecated tags, suggest improvements

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Osm is connected, these are the calls the assistant has available:

• Property — based fuzz tests with fast-check for edge case discovery

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the osm mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Osm's toolset — Property — is a fair guide to whether it matches your workflow. It is maintained by gander-tools; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.