Skip to main content
Glama
brianjbeach

gedcom-mcp

by brianjbeach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to gedcom-mcp

No user-submitted related servers found.

    Related Servers

    • gedcom-mcp

      Genealogy-MCP
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to load and query local GEDCOM genealogy files, supporting search, browsing, and family tree traversal.
      2
      2
      AGPL 3.0

    • GEDCOM MCP Server

      airy10
      A
      license
      Not graded
      quality
      A
      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.
      16
      MIT

    • Gramps MCP

      cabout-me
      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.
      44
      AGPL 3.0

    • gedfire

      morrillonline
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: get_* fetches by ID, find_* searches by criteria, list_* traverses relations, and get_sources/suggest_slug handle dedicated concerns. The potential overlap between get_family and list_children is minor as they take different inputs and serve different queries.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern with get_ (by ID), find_ (search), and list_ (relation traversal). The 'info' tool breaks the pattern, and 'suggest_slug' uses a less common verb, but the overall structure is predictable.

    Tool Count5/5

    Ten tools is well within the ideal range for a focused domain server. Each tool addresses a core genealogy query or workspace utility with no redundancy.

    Completeness5/5

    The server covers the full read-only lifecycle: retrieval by ID, search by name/family, ancestor/descendant traversal, source citations, and a slug utility. There are no obvious dead ends or missing operations for its stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources