gedcom-mcp
Related Servers
Alternatives to gedcom-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceRead-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.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query, validate, and safely update GEDCOM family-history files through a local MCP server with read-only tools and reviewable changesets.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables reading and editing a user's account tree—people, families, ancestors, descendants, and change history—and searching historical records, places, and hints. It also supports side-by-side comparison and duplicate merging, fact/relationship/source/note updates, local lineage caching, research-gap discovery, and GEDCOM export.MIT
- AlicenseBqualityAmaintenanceFamily history research toolkit with 79 archives and databases, name variants, historical calendars, kinship, evidence checks, GEDCOM auditing and archive-request drafts. An MIT-licensed Python MCP server that runs locally without API keys or network requests.31175 PyPI5MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- 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
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes (e.g., get_ancestors vs get_descendants, add_individual vs update_individual). However, set_parents and add_family both create family links, and add_child could be seen as a special case of add_family, causing slight overlap. Descriptions mitigate this by clarifying specific use cases.
All tool names follow a consistent verb_noun pattern (list_files, get_ancestors, add_individual, remove_event, etc.). No deviations or mixing of conventions.
19 tools is on the higher end but appropriate for a GEDCOM server covering querying, traversal, and CRUD operations. Each tool appears to serve a distinct function, though the count could be slightly consolidated.
The surface covers most CRUD and traversal needs: file management (list, create, rename), individual and family creation/update/deletion, event handling, notes, and sources. However, there is no explicit tool to remove or update families, and no direct way to delete a note or source, leaving minor gaps.