Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to WikiTree MCP server

No user-submitted related servers found.

    Related Servers

    • wikitree-mcp

      Genealogy-MCP
      A
      license
      A
      quality
      C
      maintenance
      Enables querying WikiTree genealogy data including profiles, ancestors, descendants, relatives, biography, photos, and categories via natural language.
      2
      1
      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.
      15
      MIT

    • gedcom-mcp

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

    • FamilySearch MCP Server

      JonathanReiss15
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search FamilySearch's Family Tree, view person details, explore ancestors and descendants, and search historical records using browser session authentication.
      1 npm
      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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Resources