v1.0.4

1.0.4 - 2026-06-28

Gramps ID handling and stdio reliability release. Tools that accept Gramps IDs (like I0002) now resolve them correctly before API calls, resolution is cached to cut down on repeated list queries during agent workflows, and console logging no longer pollutes the MCP stdio stream.

Fixed

• Gramps ID resolution in handle parameters — tools documented Gramps ID support but passed IDs like I0002 straight to /api/.../{handle}, causing false "not found" errors while find_by_gramps_id worked. Advertised handle inputs now resolve through HandleResolver before API calls.
• stdio logging — console logging wrote to stdout, so Claude Desktop and other MCP clients tried to parse startup and HTTP log lines as JSON-RPC. All console logs now go to stderr, keeping stdout reserved for the MCP protocol.

Changed

• Gramps ID cache — Gramps ID → handle resolution is cached in memory (10-minute TTL, scoped per API URL and tree) to avoid repeated list-endpoint queries during multi-step agent workflows.

Claude Desktop

Updated .mcpb bundles for this release include the fixes above. Download the bundle for your platform from the release assets:

Platform	Asset
macOS Apple Silicon	gramps-web-mcp-claude-desktop-osx-arm64-v1.0.4.mcpb
macOS Intel	gramps-web-mcp-claude-desktop-osx-x64-v1.0.4.mcpb
Windows x64	gramps-web-mcp-claude-desktop-win-x64-v1.0.4.mcpb

Docker

docker pull ghcr.io/scormave/gramps-web-mcp:1.0.4

Full changelog: v1.0.3...v1.0.4

1.0.3

1.0.3 - 2026-06-27

Reliability and privacy patch release. Parallel MCP tool calls no longer hammer Gramps Web with duplicate login requests, get_media now returns media dates, and the public /health endpoint no longer exposes deployment details.

Fixed

• Shared JWT token cache — concurrent tool calls previously each acquired their own API client and could POST /api/token/ in parallel, triggering Gramps Web rate limits (HTTP 429). Token acquisition is now centralized and serialized across all clients.
• get_media date field — media record dates from the Gramps Web API are now included in tool output (previously omitted by the formatter).

Changed

• /health response — returns only { "status": "healthy" } or { "status": "unhealthy" } instead of API URL, tree name, database ID, and Gramps version. Connectivity details remain in startup logs.
• CI — Docker release workflows (GitHub Actions and Gitea Actions) now run dotnet test before building and pushing container images.

Claude Desktop

Updated .mcpb bundles for this release include the fixes above. Download the bundle for your platform from the release assets:

Platform	Asset
macOS Apple Silicon	gramps-web-mcp-claude-desktop-osx-arm64-v1.0.3.mcpb
macOS Intel	gramps-web-mcp-claude-desktop-osx-x64-v1.0.3.mcpb
Windows x64	gramps-web-mcp-claude-desktop-win-x64-v1.0.3.mcpb

Docker

docker pull ghcr.io/scormave/gramps-web-mcp:1.0.3

Full changelog: v1.0.2...v1.0.3

1.0.2

1.0.2 - 2026-06-26

Gramps Web MCP is now available as a one-click Claude Desktop extension. Download the .mcpb bundle for your platform from the release assets below, double-click it (or drag it into Claude Desktop), fill in your Gramps Web credentials, and you're connected — no .NET SDK required.

Platform	Asset
macOS Apple Silicon	gramps-web-mcp-claude-desktop-osx-arm64-v1.0.2.mcpb
macOS Intel	gramps-web-mcp-claude-desktop-osx-x64-v1.0.2.mcpb
Windows x64	gramps-web-mcp-claude-desktop-win-x64-v1.0.2.mcpb

Read-only mode defaults to enabled in the extension for safer first use. Disable it in the extension settings when you want Claude to create or edit records.

What's changed

Added

• Claude Desktop MCPB (.mcpb) packaging with self-contained binaries for macOS Apple Silicon, macOS Intel, and Windows x64
• Tag-driven GitHub Actions workflow (mcpb-release.yml) that builds, validates, and attaches per-platform bundles to GitHub Releases — independent of the Docker/MCP Registry pipeline
• Explicit MCP tool annotations (title, readOnlyHint, destructiveHint) on all 57 tools for Claude Connectors Directory compliance
• PRIVACY.md covering data handling for the desktop extension

Changed

• Upgraded ModelContextProtocol packages to 1.3.0 for tool annotation support

Full changelog: v1.0.1...v1.0.2

1.0.1

1.0.1 - 2026-06-24

Deployment-focused patch release: health checks for Docker and Unraid, a ready-made compose stack, multi-arch images, and MCP Registry publishing.

Added

• GET /health HTTP endpoint for Docker HEALTHCHECK, Unraid container health, and other uptime monitors (returns 200 when Gramps Web is reachable, 503 otherwise)
• Startup log line confirming Gramps Web connectivity (Connected to Gramps Web at …)
• docker-compose.example.yml — example stack running Gramps Web and gramps-web-mcp on one Docker network
• MCP Registry metadata and automated publishing on version tags
• OCI image ownership label for MCP Registry validation

Changed

• Docker release workflow now publishes multi-arch images for linux/amd64 and linux/arm64
• Docker release workflow publishes the MCP Registry entry after tagged image builds
• Documentation: clarified Gramps Web pairing requirements and added an Unraid install guide

Fixed

• MCP Registry metadata now uses the correct GitHub namespace casing

Docker

docker pull ghcr.io/scormave/gramps-web-mcp:1.0.1

1.0.0

1.0.0 - 2026-06-23

Added

• Initial public release of the Gramps Web MCP server (.NET 8)
• 57 MCP tools for people, families, events, places, sources, citations, notes, media, repositories, tags, search, and composite workflows
• MCP resources and compatibility tools
• Opt-in binary MCP resources for media thumbnails and full files
• Open WebUI-compatible media image tools
• MCP prompts for common genealogy workflows
• stdio, Streamable HTTP, and legacy SSE transports
• Read-only mode
• Contract tests against vendored Gramps Web OpenAPI spec

Docker

docker pull ghcr.io/scormave/gramps-web-mcp:1.0.0