gramps-evidence-mcp
Related Servers
Alternatives to gramps-evidence-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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.48AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query, validate, and safely update GEDCOM family-history files through a local MCP server with read-only tools and reviewable changesets.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query genealogy data from GEDCOM files with 24 tools for search, navigation, relationship analysis, and timeline events.1MIT
- AlicenseNot gradedqualityAmaintenanceExposes 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
- 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 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 97 tools
Several tool families overlap heavily: query_objects vs query_records, get_object vs the shaped getters (get_person/get_source/get_citation), and the citation family (add_citation, cite_event, cite_object, cite_child_link) all target related operations. The very detailed descriptions do draw boundaries, but with 97 tools an agent can easily misselect among near-synonyms.
The dominant pattern is consistent snake_case verb_noun (get_person, add_family, update_citation, list_jobs, delete_object). A few outliers (uncite, consolidated_timeline, event_span, db_stats) break the pattern, but overall it is predictable.
97 tools is an extreme mismatch for any single server, well into the 50+ range the rubric flags. Even a complex genealogy/evidence domain does not justify this surface, and the count itself creates discovery and selection burden.
Coverage is unusually broad: CRUD on people/families/events/sources/citations/repositories/media/places/notes, plus citations, DNA, reports, filters, transactions, jobs, audits and timelines. Minor gaps exist (no explicit update/delete for repositories, notes, or tags), but generic tools like update_object_fields and delete_object cover most of them.