gedcom-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gedcom-mcpfind John Smith"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gedcom-mcp
A small MCP server that reads and searches a GEDCOM 5.5.1 file. It gives an AI agent a fast, structured way to look up individuals, families, sources, and multimedia references in a family tree, and to suggest folder slugs for an archive of per-person pages.
It is tolerant of the custom tags that Ancestry.com exports emit
(_APID, _TREE, _PRIM, _OID, and M/D/YYYY dates), but it works with
any spec-compliant GEDCOM.
No family data is bundled with this server — you point it at your own .ged
file via an environment variable.
Install
Requires Python 3.10+ and uv.
git clone https://github.com/<you>/gedcom-mcp.git
cd gedcom-mcp
uv syncRelated MCP server: GEDCOM MCP Server
Configuration
One required environment variable:
Variable | Description |
| Absolute path to the |
The file is parsed lazily on the first tool call and cached in memory.
Tools
Tool | What it does |
| File path, Ancestry tree id (if present), counts by record type. |
| Token search over INDI names (incl. AKAs). |
| Full INDI record: events, residences, sources, multimedia, family links, suggested slug, |
| Match FAM records by spouses and/or year. |
| Full FAM record with husband/wife/children resolved. |
| Children across all spouse families. |
| Bounded ancestor walk. |
| Bounded descendant walk. |
| SOUR citations attached to the person and their events, including Ancestry |
| Suggest a stable folder slug for the record (see below). |
IDs may be passed with or without @ delimiters (I123 and @I123@ are
equivalent).
Running locally
GEDCOM_FILE="/path/to/your-tree.ged" uv run gedcom-mcpIt speaks MCP over stdio.
Registering with an MCP client
Add an entry like this to your MCP client's server config (paths are
examples — adjust to your checkout and your .ged file):
{
"mcpServers": {
"gedcom": {
"command": "uv",
"args": ["run", "--directory", "/path/to/gedcom-mcp", "gedcom-mcp"],
"env": {
"GEDCOM_FILE": "/path/to/your-tree.ged"
}
}
}
}Output conventions
The server returns plain JSON-shaped data. Dates are normalized to
ISO 8601 (YYYY-MM-DD, partial dates allowed). The agent is responsible for
turning these dicts into whatever it needs; the server stays out of
formatting decisions.
Slug convention
suggest_slug produces a lowercase, hyphenated, ASCII slug intended as a
stable folder name for a per-record page:
Individual:
<surname>-<given>-<birthyear>(e.g.smith-john-1901)Family:
<husband-surname>-<wife-surname>-<marriageyear>
unknown is used for a missing year. This convention is opinionated; if your
archive uses a different scheme, adapt suggest_slug / the *_slug helpers
in src/gedcom_mcp/model.py.
License
MIT. See LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/brianjbeach/gedcom-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server