Gramps Web MCP
Related Servers
Alternatives to Gramps Web MCP
- 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.44AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read and edit a Gramps family tree hosted on Gramps Web, with guarded write operations that tag new records as unconfirmed for review.MIT
- AlicenseAqualityAmaintenanceMCP server with full coverage of the Gramps Web API REST endpoint functionality. Super-powers for your genealogy research with the help of AI.2728 PyPI2MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to search, retrieve, and create genealogical records in a Gramps Web instance.6 npm4MIT
- AlicenseNot gradedqualityBmaintenanceExposes 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
- AlicenseAqualityBmaintenanceMCP server that lets AI agents (Claude, Cursor) debug your .NET / ASP.NET Core app2715MIT
- AlicenseAqualityAmaintenanceOpen-source .NET framework and server for Model Context Protocol (MCP) with enterprise OAuth 2.0/OIDC auth, per-tool MFA, OpenTelemetry, and health checks.77MIT
- FlicenseNot gradedqualityCmaintenanceAn Effect TypeScript MCP server for safe access to Gramps Web, exposing records, relationships, timelines, media, and verified mutations to MCP clients.-
- AlicenseNot gradedqualityAmaintenanceA local .NET MCP server for coding agents, providing persistent semantic indexing, typed-graph DI wiring resolution, reduced context, and compiler-backed verification for .NET projects.36Apache 2.0
TDQS
Scored across 29 tools
Most tools target a distinct resource+action, and the descriptions actively disambiguate overlapping pairs (search vs list_objects, get_object vs list_objects vs search, get_relations vs get_person_tree vs get_timeline, read_media vs get_object). The nine per-type update_* tools are near-identical in prose and could blur together, but their target types keep them separable.
Names follow a predictable verb_noun convention (create_person, update_event, list_objects, delete_object, get_object) across the whole set. The only deviation is read_media, which breaks the get_* pattern for reading an object, though it is deliberate and explained.
At 29 tools this is heavy, and much of the bulk comes from nine create_* plus nine update_* tools that repeat nearly the same boilerplate per record type. The genealogy domain genuinely spans many record types, but a generic update/delete pattern would likely have sufficed, so the surface is borderline padded.
Coverage is strong: full create/update for every record type plus a generic delete_object with backlink handling, and read tools for search, listing, relations, trees, timelines and history. The notable gaps are the inability to create or upload media and to rename/delete tags through the server, which are documented limitations rather than oversights.