Claude.ai unesco-heritage-mcp-server unesco_search_sites
How to: Claude.ai unesco-heritage-mcp-server unesco_search_sites
Add unesco-heritage-mcp-server to Claude.ai
-
01
Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.
https://unesco-heritage.caseyjhand.com/mcp-
02
Save the file and restart Claude.ai.
-
03
Ask for something unesco_search_sites does. Claude.ai lists the server's tools on connect and calls unesco_search_sites itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that unesco-heritage-mcp-server's identifier in your config matches the one above exactly.
Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs
Set these first
unesco-heritage-mcp-server will not start until these are set, so unesco_search_sites never becomes available.
-
MCP_LOG_LEVEL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 2 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.