Skip to main content
Glama
oliverhruby

Gramps MCP

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Gramps MCP

No user-submitted related servers found.

    Related Servers

    • mcp-grampsweb

      nikkoxgonzales
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to search, retrieve, and create genealogical records in a Gramps Web instance.
      7 npm
      4
      MIT

    • ftb-mcp

      mouchar
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-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.
      Apache 2.0

    • memoo-mcp

      hinha
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Memoo knowledge graph RAG, enabling search, Q&A, graph traversal, and episode management via the Memoo REST API.
      4 npm
      Apache 2.0

    • gedfire

      morrillonline
      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

    • delapan

      anthonysuherli
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that grounds AI answers in a local, maintained knowledge base and optionally fills gaps from the web, fully local with SQLite.
      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.2/5.0

    Scored across 27 tools

    Disambiguation4/5

    The manage_* CRUD tools are cleanly separated by entity type, and read-only get_* tools (timeline, relation, living, server info) plus search and merge have distinct purposes. The main friction is that manage_media bundles many sub-actions, manage_export/manage_report both run async jobs and return files, and manage_transaction overlaps with the CRUD tools.

    Naming Consistency4/5

    Snake_case verb_noun naming is used throughout (manage_person, get_timeline, merge_objects), making tool selection predictable. Minor deviations exist: bare verbs like ping/search, and manage_import/manage_export/manage_report use 'manage' for action runners rather than entity CRUD.

    Tool Count3/5

    27 tools is above the comfortable range, but the Gramps Web API is broad and the per-object CRUD tools are parallel rather than redundant. It would benefit from some consolidation, such as splitting media sub-actions into separate tools, so it feels slightly heavy rather than excessive.

    Completeness4/5

    The surface covers CRUD for all major Gramps objects plus search, merge, timeline, relationships, living status, DNA, import/export/report, users, trees, bookmarks, types, and metadata. The main gaps are async task polling for exports/reports and a few admin operations like tree deletion.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources