WikiTree MCP server
Related Servers
Alternatives to WikiTree MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables querying WikiTree genealogy data including profiles, ancestors, descendants, relatives, biography, photos, and categories via natural language.21AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceExposes one or more Gramps Web API genealogy trees to LLM assistants, allowing users to ask research questions and edit tree data conversationally through MCP tools.1MIT
- AlicenseAqualityCmaintenanceEnables 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.192MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search family-tree data, view person and family details, explore ancestors and descendants, and search historical and full-text records using a locally stored browser session instead of an API key.11 npm2MIT
- 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
TDQS
Scored across 5 tools
Most tools have distinct purposes: get_person retrieves a single record, while get_ancestors, get_descendants, and get_relatives focus on different relationship types. However, get_relatives could be ambiguous with the more specific ancestor/descendant tools, as it might overlap in scope depending on what 'relatives' includes.
Four tools follow a consistent 'get_' prefix pattern (get_ancestors, get_descendants, get_person, get_relatives), which is clear and predictable. The outlier is call_api, which uses a different verb style, but this minor deviation doesn't significantly hinder readability or consistency.
With 5 tools, this is well-scoped for a genealogy-focused server. Each tool serves a distinct purpose in retrieving person data and relationships, and the count is neither too sparse nor overwhelming, fitting typical MCP server ranges.
The toolset covers core read operations for person data and relationships (get, ancestors, descendants, relatives), but lacks update, create, or delete capabilities, which might be expected for a full CRUD lifecycle in a genealogy context. The call_api tool provides flexibility but doesn't fill all gaps directly.