OpenHeritage Public Search MCP server

OpenHeritage agent tooling

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 three complementary ways:

• a remote, anonymous, read-only MCP server for live public-record search;
• seven portable Agent Skills with domain guidance, safe REST fallbacks, and canonical OpenHeritage links;
• a documented Personal API for user-authorized contributions with scoped bearer tokens.

No API key is required for public search.

Ukrainian heritage data at scale

• Memorials and graves: discover memorial profiles, grave sites, cemetery records, cemetery photographs, map locations, and transcriptions.
• Archival documents: search repositories and sources, retrieve digitized documents by page or original file, and use XML, transcriptions, parsing, or OCR to answer questions with provenance.

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.

MCP endpoint

https://openheritage.online/mcp

The endpoint uses MCP Streamable HTTP and exposes:

• search_records
• search_memorials
• search_cemeteries
• search_sources
• search_documents
• search_repositories
• search_places
• search_authors
• search_collections

The MCP server also exposes anonymous, read-only resources for selected public sources, documents and files, repositories, collections, canonical places, memorials, cemeteries, and Source classification tags. MCP never accepts a Personal API token.

Use the root .mcp.json with clients that support project or plugin MCP configuration.

Personal API and imports

Use the Personal API only for user-authorized contributions:

• interactive reference: https://openheritage.online/api-docs;
• OpenAPI 3 document: https://openheritage.online/api/openapi/v1.json.

Personal API tokens are bearer tokens and always include api:read. A generic catalog-only Source import uses api:sources; adding SourceDocuments, original files, page images, or PAGE XML also uses api:documents. A Source is valid without documents when no digital representation is available. The openheritage-source-import skill explains repository references, Authors, classification tags, coverage dates and places, and optional document ingestion.

A classified newspaper import additionally uses api:authors to create or update the canonical newspaper organization authority, api:sources to create issue Sources and configure the automated Collection, and api:documents to create the issue document and upload ordered page images and PAGE XML. Send the token only in the Authorization: Bearer ... header, never to MCP or in a URL.

The openheritage-newspaper-import skill contains the complete issue workflow. It resolves the environment-specific UUID for stable Source taxonomy code record-kind-newspaper, creates or reuses the newspaper organization Author, configures an Author-driven Collection grouped by publication year, records the holding repository and publication place when known, creates each issue as a publication, and uploads its ordered document pages and PAGE XML. Standalone newspaper clipping PhotoAssets remain part of openheritage-photos.

Add OpenHeritage to your agent / Додайте OpenHeritage до свого агента

English

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

Shortened. The full README is on GitHub.