Scormave

Important: please update to 2.3.1Versions before 2.3.1 had a bug: the update_* tools could drop stored data that the call did not mention, such as the citations, notes and privacy of attributes, the styling and links of note text, LDS ordinances, privacy and citations of event and child references, place URLs and media checksums. Any update could do it, even one that only added a note. Many thanks to hcirlu for reporting it: https://github.com/Scormave/gramps-web-mcp/issues/5 How to updateThe template pins the image version, so Check for Updates will not offer 2.3.1 to an existing install. Open the Docker tab, click the gramps-web-mcp icon, choose Edit, set Repository to ghcr.io/scormave/gramps-web-mcp:2.3.1 and click Apply. If you edited your tree with an earlier versionscripts/find-update-losses.py reads the Gramps Web transaction history and lists every value an update emptied, with the value it had and whether the record still lacks it. It only reads and needs nothing but Python 3.9 or later, so you can run it from any computer that reaches your Gramps Web. How to run it: https://github.com/Scormave/gramps-web-mcp#data-dropped-by-updates-before-231 A value cleared on purpose looks the same as a dropped one, so check each finding before you put it back. Questions are welcome here or on GitHub. Release notes: https://github.com/Scormave/gramps-web-mcp/releases/tag/v2.3.1

gramps-web-mcp v2 is outHi everyone! I’ve released version 2 of gramps-web-mcp, with a simpler tool interface, more readable results, and improvements to working with family trees and scanned documents. Highlights compared with 1.x: A smaller, more consistent tool set: 57 tools consolidated into up to 31. Common operations now share tools for reading records, browsing ancestors and descendants, and viewing timelines. Easier link editing: add or remove citations, notes, media, and other references without replacing the entire list. Clearer results: more names, dates, and family context directly in record details, timelines, and relationship results, with fewer follow-up requests to Gramps Web. Better media previews: larger JPEG/PNG previews make handwriting and small print easier to read. Preview metadata, including EXIF/GPS, is stripped. Improved read-only mode: write tools are now hidden from the client when read-only mode is enabled. Refresh-token authentication: an alternative to username/password login, including for instances where local password authentication is disabled. Upgrading on UnraidUpdate the container image, then reconnect your MCP client so it reloads the tool list. The HTTP endpoint remains: http://<unraid-host>:<mapped-port>/mcp This release changes tool names and some arguments. If you have saved prompts, scripts, or tool allowlists that reference 1.x tools, update them using the migration guide. Your Gramps Web tree and records do not need migration. If you previously set GRAMPS_MEDIA_ALLOWED_MIME_TYPES, remove it from your container configuration; recent 2.x releases no longer use it. Media access remains opt-in. Releases and downloads · Full changelog Feedback and Unraid upgrade reports are welcome here. If something breaks, please share your server version, MCP client, and relevant logs with credentials removed.

gramps-web-mcp is an MCP (Model Context Protocol) server that connects AI clients to your Gramps Web family tree. Install it from the Unraid Apps catalog: search for gramps-web-mcp → Install. You need a separate running Gramps Web instance with API access. This container exposes MCP over HTTP so MCP-capable clients can search, read, and optionally update your tree data. It has no standalone genealogy web UI. LinksProject and documentation Releases and downloads Unraid templates Container image: ghcr.io/scormave/gramps-web-mcp:latest What it doesUp to 29 MCP tools for people, families, events, places, sources, citations, notes, media, repositories, and tags. Search, ancestor and descendant trees, relationship queries, timelines. Add or remove links to citations, notes, media, and other records without replacing the entire list. Optional read-only mode publishes only read tools and blocks create, update, and delete calls server-side. Opt-in media previews and files, with size limits and private-record safeguards. Image previews are JPEG/PNG with embedded metadata stripped. HTTP MCP endpoint at /mcp (Streamable HTTP). Health check at /health: HTTP 200 when Gramps Web authentication works, 503 otherwise. PrerequisitesA running Gramps Web instance with API access. A Gramps Web username and password, or a refresh token. The tree UUID from your Gramps Web server. A network path from this container to Gramps Web. Use a reachable LAN address or Docker network hostname; localhost points to this container itself. InstallationOpen Apps / Community Applications in Unraid. Search for gramps-web-mcp and click Install. Fill in the settings below and click Apply. Check the container logs and /health, then connect your MCP client. Required configurationGRAMPS_API_URL — Gramps Web base URL, without a trailing slash; for example, http://grampsweb:5000 when both containers share a Docker network. GRAMPS_TREE_ID — tree UUID. GRAMPS_USERNAME and GRAMPS_PASSWORD — Gramps Web login credentials. Alternatively, use GRAMPS_REFRESH_TOKEN instead of username/password authentication. MCP HTTP Port — default 8080, mapped to container port 8080. Access and optional settingsMCP_API_KEY — set a secret key when the MCP port is reachable from other machines. Configure the client to send it as Authorization: Bearer <key> or X-Api-Key: <key>. The health endpoint remains accessible without a key. GRAMPS_READ_ONLY=true — hide write tools and block mutations. GRAMPS_MEDIA_RESOURCES_ENABLED=true — enable media previews and files; disabled by default. Media metadata remains available when file access is disabled. GRAMPS_MEDIA_MAX_BYTES — limit the media content returned to the client. GRAMPS_MEDIA_ALLOW_PRIVATE — control access to private media; private media access is disabled by default. Use Advanced View for additional template settings. Since 2.1.0, GRAMPS_MEDIA_ALLOWED_MIME_TYPES is no longer used; remove it from existing configurations. Usage after installPoint your MCP client at: http://<unraid-host>:<mapped-port>/mcp Quick connectivity check from another machine on your LAN: curl -i http://<unraid-host>:<mapped-port>/health You should get HTTP 200 when Gramps Web is reachable and authentication succeeds. This container is an API/MCP service; it has no browser web UI. Upgrading from 1.xVersion 2 consolidates the tool catalog from 57 tools to up to 31 and changes some tool names and arguments. Update the container, reconnect your client to refresh its tool list, and update saved prompts, scripts, and tool allowlists using the migration guide. Your Gramps Web tree and records do not need migration. TroubleshootingContainer exits immediately Check Docker logs. Verify GRAMPS_API_URL, GRAMPS_TREE_ID, and either username/password credentials or GRAMPS_REFRESH_TOKEN. Health check returns 503 Verify the Gramps Web URL, credentials, tree UUID, and network connectivity from the container. MCP requests return 401 If MCP_API_KEY is configured, make sure the MCP client sends the matching key. A successful health check does not test the client’s API key. Expected tools are missing Read-only mode hides write tools. read_media is available only when media access is enabled. Reconnect the MCP client after changing these settings. Image pull fails Check the image name ghcr.io/scormave/gramps-web-mcp:2.3.1 and connectivity to GitHub Container Registry. Cannot reach Gramps Web If Gramps Web runs in another container, use a reachable LAN address or its hostname on a shared Docker network, rather than 127.0.0.1 or localhost. Reporting issuesMCP server and container bugs / feature requests Unraid template issues For Unraid installation questions, reply in this thread. Include your server version, MCP client, and relevant logs with credentials removed. License noteThe container image is licensed under AGPL-3.0. If you run or redistribute a modified version, AGPL source-offer obligations may apply. Feedback and install reports are welcome in this thread.