Public search of genealogy, archives, photos, memorials, cemeteries, research, and repositories.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Public, cross-agent integration files for OpenHeritage, a collaborative genealogy and cultural-heritage platform.
OpenHeritage brings together Ukraine's largest public collection of memorial, grave, and archival document data.
This repository connects compatible AI agents to OpenHeritage in two complementary ways:
No API key is required for public search.
These records are connected through canonical OpenHeritage pages, so agents can move from a discovery lead to the relevant cemetery, memorial, source, or document without treating search results as proof.
The endpoint uses MCP Streamable HTTP and exposes:
search_recordssearch_memorialssearch_cemeteriessearch_sourcessearch_documentssearch_repositoriesUse the root .mcp.json with clients that support project or plugin MCP configuration.
Use the MCP connection for live, public OpenHeritage search. Add the skills as well when you want your agent to receive focused guidance for memorials, graves, archival documents, historical photos, and genealogy research.
Codex
Gemini CLI
Claude Code — install the complete plugin, which includes both the MCP server and skills:
If you only need live search in Claude Code, use this instead:
Start a new chat after installation. In an open Claude Code session, run /reload-plugins after installing the plugin. Do not install both the Claude plugin and its separate MCP entry unless you intentionally want duplicate configuration.
Підключіть MCP, щоб агент міг шукати публічні записи OpenHeritage у реальному часі. Додайте також навички, якщо хочете, щоб агент отримав спеціальні інструкції для роботи з меморіалами, могилами, архівними документами, історичними фотографіями та генеалогічними дослідженнями.
Codex
Gemini CLI
Claude Code — встановіть повний плагін: він містить і MCP-сервер, і навички.
Якщо в Claude Code потрібен лише пошук, використайте натомість:
Після встановлення почніть новий чат. Якщо ви встановили плагін у вже відкритій сесії Claude Code, виконайте /reload-plugins. Не встановлюйте одночасно плагін Claude та окремий запис MCP, якщо навмисно не хочете дублювати конфігурацію.
Add the public OpenHeritage marketplace, then install the complete plugin:
Connect only the MCP server:
To load the complete plugin from a checkout:
The repository includes a Claude Code manifest at .claude-plugin/plugin.json.
Install the portable skills from GitHub with a compatible Agent Skills installer:
The repository also includes a Codex manifest at .codex-plugin/plugin.json. Plugin-aware hosts can load the repository checkout directly and use its bundled .mcp.json.
Every Agent Skills-compatible host can also discover the five published skills from the OpenHeritage Agent Skills index. For an MCP host without plugin support, add the openheritage entry from .mcp.json to its user or project MCP configuration.
| Skill | Best for |
|---|---|
openheritage | Broad searches across all public OpenHeritage domains |
openheritage-archives | Sources, documents, repositories, collections, page and file retrieval, OCR, parsing, entries, and exports |
openheritage-photos | Historical photos, media variants, photo maps, corrections, and people on photos |
openheritage-memorials | Memorials, cemeteries, cemetery photos, maps, statistics, and exports |
openheritage-researches | Public genealogy research projects, questions, hypotheses, places, and evidence |
The same versioned skill documents are also published from the OpenHeritage website:
server.json publishes the remote server as io.github.OpenHeritageOnline/public-search in the official MCP Registry. The GitHub Actions workflow publishes it when an mcp-v* tag is pushed:
The workflow uses GitHub OIDC, so it requires no stored token or domain-verification private key. Registry versions are immutable: bump server.json before creating a later tag.
Publishing is restricted to protected release refs and the
mcp-registry-production GitHub Environment. The publisher is downloaded from
an exact release, verified by SHA256 and Sigstore identity, and checked for the
expected version and source commit before the OIDC-capable job can run. See the
required repository controls before
creating a release tag.
The production skill documents are maintained in the main OpenHeritage application repository under sources/FrontendServer/AgentSkills/. Keep the copies in skills/ byte-for-byte synchronized when releasing a new version.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/openheritage-public-search)<a href="https://allmcps.com/mcp/openheritage-public-search"><img src="https://allmcps.com/api/badge/openheritage-public-search?style=directory" alt="OpenHeritage Public Search on AllMCPs" /></a>