osm-tagging-schema-mcp — Claude Code MCP server for OSM tags
An MCP server that answers questions about OpenStreetMap tags: checks keys and values, finds presets, and points to replacements for deprecated tags.
claude mcp add osm-tagging-schema-mcp -- npx -y @gander-tools/osm-tagging-schema-mcpWhat osm-tagging-schema-mcp does
The server runs over stdio or HTTP and hands the agent a set of tools for working with the OSM tagging schema. All answers come from the @openstreetmap/id-tagging-schema library, version 7 — presets, fields, deprecated tags, translations. Nothing reaches out to OSM over the network, and there is no model inside the server: the agent calls the tools and reads the results.
The toolset covers single-tag checks (validate_tag), whole collections (validate_tag_collection), preset suggestions (suggest_improvements), allowed values (get_tag_values), name search (search_tags, search_presets) and preset lookup by id (get_preset_details). Validation is straightforward: is the key known, does the matching field allow this value, is the tag marked deprecated and what should replace it.
The author calls this a Proof of Concept and says so plainly. Tags that show up in real data or on the OSM wiki are not all covered by the schema, so validation does not replace a wiki check. Typos and foreign values pass as valid, since custom tags are allowed. railway=platform and railway=station get flagged as deprecated by mistake. Name search misses keys, and keys with a colon such as addr:street often slip through.
What it helps with
- check a tag before uploading an OSM edit
- look up the values a key accepts
- match a preset to a set of tags
- swap a deprecated tag for the current one
- sort a tag collection into valid and problematic
Example prompts for the agent
- Validate the tag
amenity=restaurantagainst the OSM schema and tell me if anything is off - Which values does the key
surfaceallow? - Find the preset for a bicycle parking and show its details
How to install osm-tagging-schema-mcp
Platform CLI
claude mcp add osm-tagging-schema-mcp -- npx -y @gander-tools/osm-tagging-schema-mcpPlatform CLI
codex mcp add osm-tagging-schema-mcp -- npx -y @gander-tools/osm-tagging-schema-mcpConfig file
{
"mcpServers": {
"osm-tagging-schema-mcp": {
"command": "npx",
"args": [
"-y",
"@gander-tools/osm-tagging-schema-mcp"
]
}
}
}Config file
{
"servers": {
"osm-tagging-schema-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gander-tools/osm-tagging-schema-mcp"
]
}
}
}Platform CLI
gemini mcp add osm-tagging-schema-mcp npx -y @gander-tools/osm-tagging-schema-mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about osm-tagging-schema-mcp
How do I install osm-tagging-schema-mcp in Claude Code?
Run claude mcp add osm-tagging-schema-mcp -- npx -y @gander-tools/osm-tagging-schema-mcp. That writes the server into your Claude config, and the tools show up for the agent after a restart.
What does osm-tagging-schema-mcp do?
It answers questions about OpenStreetMap tags: checks a key and its value, finds presets and allowed values, and suggests a replacement for a deprecated tag. Everything is served from the @openstreetmap/id-tagging-schema data.
Can I trust the validation results?
No — this is a Proof of Concept with known gaps. Typos and foreign values come back as valid, and railway=platform plus railway=station are wrongly reported as deprecated.
