Skip to main content
Glama
gedcom-mcp

gedcom-mcp

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_file

Load and parse a GEDCOM (.ged) file into memory

search_persons

Search individuals by name, dates, place, sex

get_person

Retrieve a specific individual by cross-reference ID

get_family

Retrieve a family record (accepts family or individual xref)

get_ancestors

Get the ancestor tree for an individual

get_descendants

Get the descendant tree for an individual

get_stats

Get statistics about the loaded GEDCOM file

Related MCP server: Gramps MCP

Configuration

All settings are optional with sensible defaults.

Environment Variable

Default

Description

GEDCOM_MAX_FILE_SIZE_MB

100

Maximum allowed GEDCOM file size in MB

GEDCOM_DEFAULT_ANCESTOR_DEPTH

5

Default ancestor traversal depth

GEDCOM_DEFAULT_DESCENDANT_DEPTH

5

Default descendant traversal depth

GEDCOM_MAX_TREE_DEPTH

50

Hard ceiling on traversal depth

GEDCOM_MAX_SEARCH_RESULTS

100

Maximum search results returned

GEDCOM_ALLOWED_BASE_DIRS

(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-mcp

Using 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-mcp

Development

# 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 run

License

AGPL-3.0-only

Available Tools

2 tools
executeA

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      17
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      52
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Reads and searches GEDCOM 5.5.1 files, enabling AI agents to look up individuals, families, sources, and multimedia references in a family tree.
      10
      MIT