# osm-tagging-schema-mcp [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/gander-tools/osm-tagging-schema-mcp  
**GitHub Stars:** 8  
**npm Downloads (last month):** 931  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/osm-tagging-schema-mcp

## Description
MCP server for querying and validating OpenStreetMap tags

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "osm-tagging-schema-mcp": {
    "command": "npx",
    "args": ["-y","@gander-tools/osm-tagging-schema-mcp"]
  }
}
```

## Documentation

## What osm-tagging-schema-mcp does

The osm-tagging-schema-mcp MCP server connects AI agents to the OpenStreetMap iD tagging schema distributed by `@openstreetmap/id-tagging-schema`. It exposes structured operations for examining presets, fields, translations, deprecated tags, and allowed values. The project currently targets schema version 7 and is described as a proof of concept, so it is better suited to assisted workflows than to treating every result as a complete statement about current OSM practice.

No user interface is included. An MCP-compatible host calls the tools and interprets their responses; the server itself supplies deterministic results from its bundled schema data.

## How it works

The process communicates over stdio by default and also supports HTTP. Each request is evaluated against the schema packaged with the server. There is no live OSM lookup, OSM API access, or AI reasoning inside the process.

Validation can check whether a key is known, whether a value is accepted by the matching field, and whether a key or value is deprecated. Suggested replacements may be returned for deprecated entries. Collection validation applies the same general rules to multiple tags.

## Setup and configuration

The package can be launched with `npx` and is documented for use with Claude Code over stdio. The documented package name is `@gander-tools/osm-tagging-schema-mcp`. A Docker-based Claude Code setup is also shown using the published image `ghcr.io/gander-tools/osm-tagging-schema-mcp`.

Because the server can run over stdio or HTTP, the MCP host must be configured with the transport and launch details appropriate to the chosen deployment.

## Tools and capabilities

The osm-tagging-schema-mcp MCP server provides tools covering several distinct tasks:

- `validate_tag` checks individual key-value pairs against schema fields.
- `validate_tag_collection` validates a group of tags using the same validation behavior.
- `suggest_improvements` looks for a matching preset and possible improvements.
- `get_tag_values` returns known values for a tag key.
- `search_tags` searches schema keys and related matches.
- `search_presets` searches available presets.
- `get_preset_details` retrieves information for a preset identifier.
- `compare_tags` compares two tag sets without deciding whether either set is correct.
- `flat_to_json` and `json_to_flat` convert between flat tag text and JSON representations.

The conversion tools preserve values containing semicolons, spaces, equals signs, Unicode, colons, and slashes. Invalid inputs produce readable errors or empty results rather than crashing the server, according to the project’s documented testing.

## Limitations and notes

The osm-tagging-schema-mcp MCP server does not represent all tags found in the wild or documented on the OSM wiki. Validation accepts custom tags, so typos and foreign values can pass as valid. It detects only a portion of wiki-deprecated tags, and the project records known false deprecation results for `railway=platform` and `railway=station`.

Search is another weak area: typo tolerance is absent despite the fuzzy-search description, colon-containing keys may be missed, and multi-word preset searches can return no result. Ranking is limited, and some popular tags do not have presets. `compare_tags` only compares supplied sets; it does not judge whether a tag is valid. Flat-to-JSON conversion accepts duplicate keys and control characters silently, while JSON-to-flat preserves input order instead of sorting keys.

Use the results as schema-backed guidance for an agent workflow, not as a complete OSM tagging authority.

_Full upstream README: https://allmcps.com/mcp/osm-tagging-schema-mcp/readme_