Gramps Mcp
MCP server for Gramps genealogy via the Gramps Web API: CRUD, search, merge, timelines, DNA.
A Model Context Protocol (MCP) server that exposes the full functionality of the Gramps Web API to AI agents such as opencode, Claude, Cursor and any other MCP client. It is published on PyPI as gramps-mcp-full.
Gramps is a free, open-source genealogy program, and Gramps Web ships a REST API (gramps-web-api) that lets you read and operate a family tree — people, families, events, places, sources, citations, notes, media, repositories and tags, plus genealogy compute (merge, timelines, relations, living status, DNA), import/export, reports, transactions and server administration.
This server lets your agent query and operate a Gramps tree directly: full CRUD for all object types, full-text/semantic search, merge objects (phoenix/titanic survival), timelines, relationships, alive estimates, DNA match analysis, a media pipeline (binary upload, file download, thumbnails, OCR, face detection), GEDCOM / Gramps XML import and export with privacy filters, report generation, raw transactions, and admin over users, trees, bookmarks and type vocabularies — including multiple instances (one or more Gramps Web base URLs, each with token/JWT auth).
⚠️ Official API, mutable data. Unlike the EduPage server (which reverse-engineers undocumented endpoints), this uses the official, documented Gramps Web REST API —
gramps-web-api, maintained under thegramps-projectorganization with a published OpenAPI spec at https://gramps-project.github.io/gramps-web-api/. Use read-only features freely; use the write features (manage_*,merge_objects,manage_import,manage_transaction, …) carefully — they mutate real tree data.
Table of Contents
- Why another Gramps MCP server?
- What it provides
- Getting started
- Prompt examples
- Multiple instances (base URLs)
- Tool reference
- Data & safety notes
- Contributing
- Limitations
- Support
- License
Why another Gramps MCP server?
Other Gramps MCP servers already exist:
Knuckles-Team/gramps-mcp— 35 action-routed tools, A2A agent, OTEL telemetry, singleGRAMPS_URLcabout-me/gramps-mcp— 16 tools, AGPL-3.0, Docker Compose based, HTTP-firstScormave/gramps-web-mcp— 57 tools + 6 resources, .NET, multi-transport, read-only modeGenealogy-MCP/gramps-mcp— AGPLv3, GitLab mirror, 32 releases
All are good and I have no affiliation with them — they are simply referenced here for honest comparison. They either fragment the surface into many near-identical tools or cover only read-mostly slices of the API.
This project deliberately goes further:
From the project's README.