Skip to main content
Glama
igormel81

genealogy-mcp

by igormel81

Related Servers

Alternatives to genealogy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server for genealogy data from Family Tree Builder (.ftb) or GEDCOM files, exposing tools for person search, family relationships, and statistical analysis via HTTP or stdio.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to query, validate, and safely update GEDCOM family-history files through a local MCP server with read-only tools and reviewable changesets.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server with full coverage of the Gramps Web API REST endpoint functionality. Super-powers for your genealogy research with the help of AI.
      27
      39 PyPI
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to read, search and edit GEDCOM (.ged) family-tree files from Ancestry.com and other genealogy software, letting an MCP client navigate relationships, explore ancestor and descendant trees, inspect sources and citations, and make safe, lossless edits that are written straight back to the file with a backup.
      19
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Connect AI assistants to your Gramps Web family tree. Search and edit genealogy records, explore ancestors, descendants, relationships and timelines, and read document scans with vision-capable models. Includes guided research workflows, source citations, read-only mode, and privacy-aware media previews. Install with Docker or a Claude Desktop bundle.
      6
      31
      14
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read and write a self-hosted Gramps Web family tree through the REST API, creating facts with citations attached and auditing unsourced or duplicate data with 83 evidence-disciplined tools. It also exposes legacy GEDCOM exports as a read-only reference layer of untrusted hints, with living-person privacy filtering on by default.
      97
      1,287 PyPI
      MIT

    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