Skip to main content
Glama
Genealogy-MCP

wikitree-mcp

by Genealogy-MCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to wikitree-mcp

No user-submitted related servers found.

    Related Servers

    • WikiTree MCP server

      PeWu
      A
      license
      B
      quality
      C
      maintenance
      Integrates with the WikiTree API to provide tools for exploring genealogical data, including ancestor and descendant information. It enables users to retrieve biographies and family relationships through any application supporting the Model Context Protocol.
      5
      1
      Apache 2.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

    • 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.
      42
      AGPL 3.0
    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.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The tools 'search' and 'execute' have clearly distinct purposes: one discovers operations and schemas, the other executes them. No overlap.

    Naming Consistency5/5

    Both tools use simple, consistent verb-only names ('search', 'execute') that clearly reflect their actions.

    Tool Count3/5

    With only 2 tools, the surface seems thin, but the design intentionally uses a meta-pattern where 'search' discovers API operations. This can be appropriate for a large dynamic API, though it may feel sparse.

    Completeness3/5

    The discover-execute pattern covers the basic interaction with the WikiTree API, but it lacks direct CRUD tools and relies entirely on dynamic discovery, which may leave gaps in common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources