Skip to main content
Glama
igormel81

genealogy-mcp

by igormel81

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GENE_CMDNoPath to the `gene` command. By default the `gene` command is found on PATH or next to the server's Python; elsewhere set GENE_CMD. Needed when using a gene-archive site as the project.
GENE_AUTHORNoSets the name used in the git history for changes made to a gene-archive site (default: `git config user.name`).
GENEALOGY_MCP_HOMENoDirectory where research projects are kept. Defaults to `~/Documents/genealogy-mcp`.
GENEALOGY_MCP_SITESNoThe gene-archive site folder(s) to use as the project (or a GEDCOM `.ged` file path). Can also be given to the assistant as a path, or set in the Claude Desktop extension settings.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_sourcesB

Find genealogy databases and archives for a country (or region), period and kind of records — 114 sources across Russia and the former USSR, the Caucasus and Central Asia, Eastern, Western and Northern Europe, Germany, the British Isles, the Americas, Australia and New Zealand, each with what it holds and how to search it well.

source_detailsA

Everything about one source from the catalogue (by id from find_sources): coverage, access, search tips.

search_linksB

Ready search links (open them in a browser) in the sources that take a search URL — FamilySearch, Internet Archive full text, Find a Grave, Arolsen, Geneteka, Open List and others — for a name, with the name's variants.

where_are_recordsA

Which archives now hold the records (parish registers, revision lists, confession lists, civil records) of a province of the Russian Empire, the Kingdom of Poland, Galicia, Bukovina, East Prussia, the Baltics or the Caucasus — borders moved, so this is often not the archive of today's region. Also works from a modern region back to the historical provinces it was part of.

search_onlineA

Search an open database live and get the matching records back (title, date, place, link, snippet). Sends the query to that one site only. Run it for each name form from name_variants; for FamilySearch, Geneteka, Find a Grave and other sites without an open API use search_links.

place_historyA

Look a place up in Wikidata: what administrative units it was part of (with years where known), coordinates and the Wikipedia article — a first step to the uezd, province and parish of a village. Sends the name to Wikidata.

plan_researchB

A step-by-step research plan for a country and period: which records exist, which guides to read and which sources to search, in order (free and country-specific first).

name_variantsB

All the forms a name can take in records (and its Daitch–Mokotoff Soundex codes): spelling variants, pre-1918 orthography, male/female surname forms (Колодин/Колодина, Kowalski/Kowalska, Kazlauskas/Kazlauskienė), transliterations (passport, BGN, German, French, Polish, Romanian, Spanish, Ukrainian, scholarly) and given-name equivalents across languages (Иван = Іоаннъ = Jan = Johann = Juan).

normalize_dateA

A date as people write it ('около 1899', 'between 1900 and 1905', '9 de octubre de 1899', '9.10.1899') → ISO or GEDCOM ('ABT 1899', 'BET 1900 AND 1905', '9 OCT 1899', '1899-10-09').

convert_calendarA

Convert between calendars of old records: Julian (old style; Russia until February 1918: +10 days in the 1600s, +11 in the 1700s, +12 in the 1800s, +13 in 1900–1918), Gregorian, Hebrew (Jewish registers, tombstones) and the French Republican calendar (1792–1805).

feast_dateA

The date of a church feast or fast in a given year (Julian and Gregorian), including movable feasts counted from Easter. Records and family stories often date events by feasts: «родился на Покров», «венчались после Петрова поста».

cyrillic_numeralsA

Church Slavonic numerals in old registers and church books: ҂аѡ҃п = 1880, ѳі = 19 (11–19 are written units first). Reads letters, writes a number, or finds every numeral marked with a titlo in a text.

dna_matchA

Which relationships a DNA match fits, from the amount of shared DNA (Shared cM Project 4.0 ranges), closest first. Several always fit: use documents (and the kinship tool) to decide.

birth_year_from_ageA

The birth-year range implied by an age in a record (census, confession list, death record), exact and loose.

kinshipB

What B is to A, named in Russian, English and Romanian (троюродный брат / second cousin / văr de gradul 2, двоюродный дед / great-uncle), with the expected share of DNA.

check_matchA

Is the person in a found record ours? Compares fact by fact (with name variants and Julian/rounded-age tolerance) and gives a verdict: confirmed (2+ independent facts beyond the name), probable, insufficient, conflict or different_person.

audit_treeA

Audit a family tree from any program (GEDCOM) for impossible facts (born after the mother's death, a parent under 14, death before birth), possible duplicates and gaps (no sources, no dates, people cut off from the tree) — a to-do list for the next search.

draft_archive_requestB

A draft letter to a registry office or an archive (Russian ZAGS, state, military and FSB archives; any archive in English, Spanish or Portuguese), with what to attach. Gaps are left in [brackets]. The user sends it — not the tool.

record_guideA

How to read and find a kind of record: parish registers, confession lists, revision lists, household books, WWI and WWII records, repression files, passenger lists, censuses, European civil registration, Latin America, evaluating evidence — in English, Russian, Ukrainian, and partly Spanish, Portuguese, Polish, German. Without a topic — the list.

glossaryB

Old Russian terms from records — estates, kinship by marriage (шурин, деверь, золовка), archive citation (фонд, опись, дело, лист), administrative units, pre-1918 letters — explained.

project_viewA

Read the research project kept between conversations — or a family's gene-archive site folder, or the user's own tree in a GEDCOM file: summary (people, open leads, recent searches, problems), one record with its family and sources, a text search, the full search log, or the tree checks. Start every session on an existing project with what='summary'.

project_saveA

Add or change a person, family, source or research lead in the project. Every change of an existing record is logged with the old and new value, the reason and the documents. Save the source first, then cite its S-id. In a gene-archive site folder the change goes through gene apply: refused if it adds an error, logged, committed to git under the owner's name, and the site is rebuilt. In a .ged file only the changed lines are rewritten (everything else in the file stays as it was), a copy is kept, and gedcom_changes shows the lines. Ask the user before writing into their archive or tree.

project_logB

Write a line in the project's research log, so nobody searches the same place twice. Log negative results.

project_transferB

Export the project as GEDCOM 5.5.1 (for MyHeritage, Ancestry, Gramps, Geni…) next to the project file, or start a new project from a GEDCOM exported by another program.

Prompts

Interactive templates invoked by user choice

NameDescription
start_researchBegin a family search for one person.
check_findIs a found record about our person?
transcribe_recordHelp read an attached image of an old record.
archive_requestPrepare a request to an archive or a registry office.

Resources

Contextual data attached and managed by the client

NameDescription
res_sourcesThe full catalogue of genealogy sources
res_glossaryGlossary of old Russian record terms

TDQS

A3.5/5.0

Scored across 24 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but the source-search and research-guidance cluster (find_sources, source_details, search_links, search_online, where_are_records, plan_research, record_guide) is dense and could cause occasional misselection. The detailed descriptions mitigate this, and the date, name, DNA, and project tools are well differentiated.

Naming Consistency4/5

All names are snake_case and mostly descriptive, but the set mixes verb-first (find_sources, normalize_date) and noun-first (source_details, place_history, project_view) conventions. This is still readable and consistent enough, though not a single strict verb_noun pattern.

Tool Count3/5

24 tools is on the heavy side for an MCP server; while each tool appears to serve a distinct function, the breadth could likely be consolidated (e.g., date/calendar utilities, project actions). It falls into the '16-25 feels heavy' borderline range.

Completeness4/5

The surface covers a broad genealogy workflow: source discovery, research planning, record interpretation, date/name normalization, DNA/kinship analysis, correspondence, and project CRUD/logging. Some gaps remain (e.g., no explicit image/record attachment, deduplication merging, or advanced DNA tools), but core operations are well supported.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive