Osm Tagging Schema Mcp

io.github.gander-tools由 GitHub 帳號 gander-tools 發布v3.0.1更新於 Oct 24, 2026

MCP server for querying and validating OpenStreetMap tags

已驗證STDIO僅桌面位置與生活開發者工具

概覽

AI 產生的概覽

一個本機 MCP 伺服器,讓助理離線、確定性地查詢 OpenStreetMap 標籤,並依官方 iD 標註 schema 進行驗證。

可以做什麼
驗證單一標籤或標籤集合,包括辨識已棄用的鍵值並提供替代建議,以及為符合預設的標籤提供改善建議。查詢某個鍵允許的取值,依名稱搜尋標籤與預設,依 id 讀取預設詳情。比較兩組標籤,並在扁平標籤字串與 JSON 之間轉換。所有結果都來自內建 schema 資料,伺服器不連線 OSM,也不含 AI。
適用情境
適合助理需要確定性的 OSM 標註協助時:檢查常見標籤是否有效、轉換標籤格式、比較標籤集合,或讀取預設與允許取值。專案自稱概念驗證,因此不宜依賴它做棄用標籤偵測或模糊搜尋。
執行需求
透過 npx(Node.js)或 Docker 以本機程序執行,預設使用 stdio。設定 TRANSPORT=http 可啟用選用 HTTP 模式,另有 PORT、HOST、CORS_ORIGINS 與 LOG_LEVEL 設定。不需帳號、API 金鑰,也不連線 OSM。
安裝前請注意
README 說明這是概念驗證,有已知缺口:只能辨識約 20% 的 wiki 棄用標籤,會把拼字錯誤與外來取值判為有效,搜尋會漏掉含冒號的鍵與多字查詢。它只依 schema 資料作答,schema 未涵蓋的標籤無法判斷。它供 AI 代理使用,不適合直接給人操作。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Osm Tagging Schema Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

OpenStreetMap Tagging Schema MCP Server

[Test] [Fuzzing] [Release] [Docker]

[npm downloads] [GitHub Release]

[TypeScript] [MCP SDK] [OSM Schema]

[Code Quality] [NPM Provenance] [SLSA 3]

[License: GPL-3.0] [Last Commit] [GitHub Issues] [GitHub PRs]

What is this?

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.

Project status

This project is a Proof of Concept. It gives real value in some areas and has known gaps in others, both described honestly below.

  • It works with the latest tagging schema, @openstreetmap/id-tagging-schema v7.
  • A better replacement tool is being worked on. It will arrive later than originally planned, and no date is promised.

Bug reports and ideas: open an issue or start a discussion.

How it works

The server runs over stdio (default) or HTTP and exposes the tagging schema as MCP tools. Every tool reads the schema data shipped in @openstreetmap/id-tagging-schema (presets, fields, deprecated tags, translations) and answers from it deterministically. There is no network access to OSM and no AI inside the server: the AI agent calls the tools and interprets the results.

Validation checks a tag against the schema: known key, value allowed by the matching field, deprecated key/value with a suggested replacement.

What works and what doesn't

The tool has limitations. Know what to expect before relying on it: it answers from the schema data only, and a part of the tags that exist in the wild or on the OSM wiki is not covered.

ToolWorksLimitations
validate_tagPopular tags accepted (100%), almost no false deprecated alarms (99.2%)Detects only ~20% of wiki-deprecated tags; typos and foreign values are accepted as valid (custom tags are allowed); railway=platform and railway=station are wrongly flagged as deprecated
validate_tag_collectionConsistent with validate_tag (100%)Same gaps as validate_tag; control characters are not reported
suggest_improvementsPreset matched for 92% of popular tagsTypos and foreign values usually yield suggestions, not a problem report
get_tag_values97% of taginfo values present; bad keys and limits rejectedA few taginfo values are missing from the lists
search_tagsFinds 60% of keys by nameNo typo tolerance despite the fuzzy-matching description; keys with a colon (addr:street) are often missed; limit of 0 or negative not always rejected; access returns a keyMatches item without key
search_presetsPreset found for 69% of popular tags (56% in top 3)Multi-word queries (bicycle parking) can return nothing; weak ranking; limit of 0 or negative not always rejected
get_preset_detailsPreset exists for 93% of popular tags; unknown ids always rejectedSome popular tags (e.g. historic=*, craft=grinding_mill, railway=stop) have no preset
compare_tagsMatches local computation (100%); text and JSON input give identical outputCompares any tag sets, so it never says a tag is wrong; only malformed input is rejected
flat_to_jsonLossless, including ;, spaces, =, Unicode, : and /Duplicate keys and control characters are accepted silently
json_to_flatLossless round-trip (100%); bad input rejectedKeys are not sorted alphabetically, input order is kept

Across all tools, invalid input never crashed the server: errors are readable or the result is an empty list.

Summary

Useful where deterministic logic is enough: format conversion, comparing tag sets, reading presets and values, validating popular tags. Weakest areas: deprecated tag detection and search (typos, multiple words, colon keys).

What this is NOT

⚠️ Important clarifications:

  • Not a standalone application: This server requires integration with AI systems (like Claude Code or Claude Desktop) to be useful. It has no user interface or web frontend.
  • Not for direct human use: Without an AI agent as an intermediary, this tool provides no value to end users. It's designed exclusively for programmatic access by LLM applications.

If you're looking for a user-facing OSM tagging tool, consider iD editor or JOSM instead.

Installation

Add the server to Claude Code (stdio):

bash
# npxclaude mcp add --transport stdio osm-tagging-schema -- npx -y @gander-tools/osm-tagging-schema-mcp
# Dockerclaude mcp add --transport stdio osm-tagging-schema -- docker run -i --rm ghcr.io/gander-tools/osm-tagging-schema-mcp:latest

HTTP transport

stdio is the default. Set TRANSPORT=http to serve over HTTP (streamable, port 3000 in the Docker image):

VariableDefaultMeaning
TRANSPORTstdiostdio or http
PORT3000HTTP port
HOST0.0.0.0HTTP bind address
CORS_ORIGINShttp://localhost:6274,https://mcp.ziziyi.comComma-separated allowed CORS origins
LOG_LEVELINFOSILENT, ERROR, WARN, INFO, DEBUG
bash
docker run --rm -p 3000:3000 -e TRANSPORT=http ghcr.io/gander-tools/osm-tagging-schema-mcp:latest

Endpoints: GET /health (liveness), GET /ready (schema loaded), GET /version.

License

GNU General Public License v3.0 - See LICENSE file for details.

來源:README.md,提交 bb2e493

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v3.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分