gedcom-mcp
Click on "Deploy 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-mcp load my family.ged file and list all descendants of Jane Doe"
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
MCP server for querying local GEDCOM genealogy files through AI assistants. Load any .ged file and search, browse, and traverse your family tree without leaving your AI workflow.
Part of the Genealogy-MCP organization.
Note: GitHub is a read-only mirror. Development happens on GitLab.
Available Tools
Tool | Description |
| Load and parse a GEDCOM (.ged) file into memory |
| Search individuals by name, dates, place, sex |
| Retrieve a specific individual by cross-reference ID |
| Retrieve a family record (accepts family or individual xref) |
| Get the ancestor tree for an individual |
| Get the descendant tree for an individual |
| Get statistics about the loaded GEDCOM file |
Related MCP server: Gramps MCP
Configuration
All settings are optional with sensible defaults.
Environment Variable | Default | Description |
|
| Maximum allowed GEDCOM file size in MB |
|
| Default ancestor traversal depth |
|
| Default descendant traversal depth |
|
| Hard ceiling on traversal depth |
|
| Maximum search results returned |
| (empty) | Comma-separated allowed directories for file loading |
Setup: Claude Desktop
Add to your claude_desktop_config.json:
Using uv (local)
{
"mcpServers": {
"gedcom": {
"command": "uv",
"args": ["--directory", "/path/to/gedcom-mcp", "run", "gedcom-mcp"],
"env": {
"GEDCOM_ALLOWED_BASE_DIRS": "/path/to/your/gedcom/files"
}
}
}
}Using Docker
{
"mcpServers": {
"gedcom": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-v", "/path/to/your/gedcom/files:/data:ro",
"-e", "GEDCOM_ALLOWED_BASE_DIRS=/data",
"ghcr.io/genealogy-mcp/gedcom-mcp"
]
}
}
}Setup: Claude Code
Using uv (local)
claude mcp add gedcom -- uv --directory /path/to/gedcom-mcp run gedcom-mcpUsing Docker
claude mcp add gedcom -- docker run -i --rm \
-v /path/to/your/gedcom/files:/data:ro \
-e GEDCOM_ALLOWED_BASE_DIRS=/data \
ghcr.io/genealogy-mcp/gedcom-mcpDevelopment
# Install dependencies
make install
# Run tests with coverage
make test
# Run all checks (lint + type-check + test + audit)
make ci
# Format code
make format
# Run via stdio transport
make run-stdio
# Run via streamable-http on port 8000
make runLicense
AGPL-3.0-only
Available Tools
2 toolsexecuteA
Run a named operation. Use 'search' first to discover the exact operation name and its params schema, then call this with {operation: '...', params: {...}}.
Inputs: arguments (required). Returns: result
searchARead-onlyIdempotent
Discover available operations and their parameters. Call with a top-level 'query' string (not inside params). Returns matching operations with parameter schemas and usage examples. Always use this before calling 'execute' to find the correct operation name.
Inputs: arguments (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'search' is for discovering operations and their parameter schemas, while 'execute' runs a specific operation by name. There is no ambiguity or overlap between them.
Both tools use a single imperative verb ('search', 'execute'), which is a consistent and simple naming pattern. Although not verb_noun, the pattern is uniform.
With only 2 tools, the server efficiently provides a meta-interface to dynamically discover and execute many underlying operations. This lean design is well-suited for its purpose.
The tool set is complete for its intended role: 'search' covers discovery of all operations and parameters, and 'execute' covers execution. There are no missing operations given the design.
Maintenance
Related MCP Connectors
Family history and genealogy in your AI: your tree and FamilySearch, with a source for every fact.
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Read-only A2Me family context tools for AI assistants (members, dates, activity, relationships)
Read and search folders on your own computer with explicit consent. Files are never uploaded.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, edit, and query genealogical data from GEDCOM files. Supports complex genealogy searches, automatic data enrichment from web sources, relationship analysis, and biography generation for individuals and families.17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Gramps genealogy databases for intelligent family tree research and management. Provides comprehensive tools for searching family data, creating records, analyzing relationships, and tracking genealogy research through natural language.52AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query genealogy data from GEDCOM files with 24 tools for search, navigation, relationship analysis, and timeline events.1MIT
- AlicenseAqualityDmaintenanceReads and searches GEDCOM 5.5.1 files, enabling AI agents to look up individuals, families, sources, and multimedia references in a family tree.10MIT