Skip to main content
Glama
ianderso
by ianderso

Related Servers

Alternatives to gramps-evidence-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      43
      AGPL 3.0
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 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.
      MIT
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      MCP server with full coverage of the Gramps Web API REST endpoint functionality. Super-powers for your genealogy research with the help of AI.
      27
      37 PyPI
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 83 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions often explicitly distinguish generic from specific tools (e.g. get_object vs get_person, cite_object vs cite_event). However, overlaps remain: query_objects vs query_records, add_media vs attach_media, and list_object_types vs list_event_types could still cause misselection.

    Naming Consistency4/5

    The set is overwhelmingly snake_case and action-oriented, with predictable verb_noun names across most CRUD, audit, and lifecycle operations. Minor deviations such as db_stats, event_span, consolidated_timeline, and uncite slightly break the strict verb_noun pattern.

    Tool Count1/5

    83 tools is far beyond a practical MCP surface for an agent, even for a complex genealogy evidence domain. While many tools are specialized and defensible, the count itself creates excessive selection burden and is an extreme mismatch for efficient tool use.

    Completeness4/5

    The surface is very comprehensive, covering people, families, events, sources, citations, repositories, media, places, DNA, reports, filters, transactions, and audits. Minor gaps exist, notably the apparent absence of a generic search_text tool despite reindex_search referencing one, with some operations reachable only through generic escape hatches.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues