familysearch-mcp
Related Servers
Alternatives to familysearch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables direct interaction with FamilySearch.org's shared Family Tree and historical records, including reading and adding people, facts, relationships, sources, notes, memories, record search, and image downloads, without needing a browser.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search FamilySearch's Family Tree, view person details, explore ancestors and descendants, and search historical records using browser session authentication.9 npm3MIT
- AlicenseAqualityCmaintenanceEnables read-only search and retrieval of Find a Grave memorials, cemeteries, and places, including dates, burial details, inscriptions, biographies, family links, and photos, via the site's anonymous GraphQL API without login.5MIT
- AlicenseBqualityBmaintenanceEnables read-only search and exploration of the GenizahSearch research API, including manuscript search, page browsing, parallel finding, and multi-phrase queries, along with policy resources and research prompts.4Creative Commons Attribution Non Commercial Share Alike 4.0 International
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to the Internet Archive's Wayback Machine and catalog, enabling retrieval of archived web captures, snapshot metadata, and catalog search.BSD 3-Clause

Genomics MCPofficial
AlicenseBqualityAmaintenanceRetrieve genomic data from EGA, ENA, ENCODE, GEO and NCBI, read bounded regions from indexed BAM/CRAM, VCF and bigWig files, and query source-attributed reference evidence. Runs locally with 23 MCP tools. MIT-licensed; research use.23MIT
TDQS
Scored across 25 tools
Most tools target clearly distinct resources and actions (records, places, collections, tree persons, images). The main overlap is the four image-access tools (get_record_image, get_image_links, get_film_image, download_image), which an agent could confuse despite the descriptions clarifying their different steps.
All names use lowercase snake_case, and almost all follow a verb_noun pattern (get_record, search_places, download_image). The few deviations, such as auth_status, are common and readable rather than inconsistent.
25 tools is heavy for this surface, though the domain is broad enough that most tools are not redundant. The count sits at the borderline where density starts to make tool selection harder for an agent.
The set covers record search/read, place resolution, collections, image retrieval, and many tree-person read operations. However, it lacks a way to discover tree persons by name or otherwise find their IDs, which blocks or complicates tree workflows before any get_person_* tool can be used.