FamilySearch API MCP. Audit entire family lines and historical records.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
FamilySearch API connects your AI agent to the world's largest platform for family history. It lets your agent audit persons, trace pedigrees, and query global historical record collections using natural language.
You don't need to touch a genealogy portal; your agent acts as a real-time research consultant, retrieving detailed metadata and assets instantly.
What your AI agents can do
Check api status
Checks if the FamilySearch API connection is currently operational.
Get person details
Gets all detailed metadata for a specific person in the family tree using their ID.
Get person memories
Retrieves all associated memories, like photos and stories, for a given person's ID.
The agent searches the global tree and retrieves detailed metadata for specific individuals using search_persons and get_person_details.
The agent generates and reads out an individual's complete ancestry chart, including ancestors and vital dates, using get_person_pedigree.
The agent pulls all associated memories—photos, stories, and documents—for a person using get_person_memories.
The agent lists and reviews available historical record collections across the platform using list_historical_collections.
The agent pulls unique identifiers and display names for any genealogical record to assist in deep-dive data classification.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
FamilySearch API MCP Server: 6 Tools for Genealogy Research
Use these tools to systematically query, audit, and retrieve structured metadata from the FamilySearch database.
019d8439check api status
Checks if the FamilySearch API connection is currently operational.
019d8439get person details
Gets all detailed metadata for a specific person in the family tree using their ID.
019d8439get person memories
Retrieves all associated memories, like photos and stories, for a given person's ID.
019d8439get person pedigree
Retrieves the full ancestry chart (pedigree) for a specified person ID.
019d8439list historical collections
Lists all historical record collections available on the FamilySearch platform.
019d8439search persons
Searches the FamilySearch Family Tree database for persons based on criteria.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with FamilySearch API, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
The FamilySearch API plugs your AI agent right into the biggest family history platform out there. It lets your agent audit people, trace entire pedigrees, and query global historical record sets just by talking to it. You don't gotta mess with a genealogy portal; your agent acts like a research consultant, pulling detailed metadata and assets in real-time.
Your agent first checks the check_api_status to make sure the FamilySearch API connection's up and running.
To find and audit people, your agent uses search_persons to search the global Family Tree database by criteria, and then grabs all the detailed metadata for any specific individual using get_person_details. For tracking family lineage, your agent uses get_person_pedigree to get a person's full ancestry chart, including ancestors and vital dates.
It pulls all associated memories—like photos, stories, and documents—for a person using get_person_memories. To audit historical sources, your agent runs list_historical_collections to list all the historical record sets available on the platform. When you need to verify record identifiers, your agent pulls unique identifiers and display names for any genealogical record.
How FamilySearch API MCP Works
- 1 Subscribe to the FamilySearch API server and provide your access token.
- 2 Your AI client initiates a request, asking the agent to find information (e.g., 'Find the parents of John Doe').
- 3 The agent executes the necessary tool calls (
search_persons,get_person_details) and returns the structured data directly to your client.
The bottom line is that your AI agent handles the complex data retrieval, eliminating the need to navigate FamilySearch portals manually.
Who Is FamilySearch API MCP For?
Genealogists, historians, and advanced researchers need this. You are the person who spends hours cross-referencing paper records and digital databases. You're tired of manual searches, digging through multiple tabs, and manually stitching together a life story. This server lets you ask complex questions and get verified data back.
Uses the agent to audit entire family lines and cross-reference unique identifiers across multiple records.
Queries historical record collections and searches for persons to build context for published research.
Verifies person details and audits lineage patterns without having to manually search the FamilySearch site.
What Changes When You Connect
- Trace Lineage Instantly: Use
get_person_pedigreeto get an individual's full ancestry chart. You don't have to click through generations to see the full lineage. - Audit People and Records: Run
search_personsto find potential matches, and then useget_person_detailsto pull specific metadata like lifespans and birth locations. - Collect Media in Bulk:
get_person_memoriespulls all associated photos, stories, and documents for a person. You get a complete asset list without manual browsing. - Map Global Archives: Call
list_historical_collectionsto see what records exist worldwide. You understand the full scope of the global archive instantly. - Verify Data Points: Use
get_person_detailsorget_person_pedigreeto ensure every piece of data—from a birth date to a unique ID—is verified and correct. - Streamline Research: By routing data through the agent, you skip the manual clicks, form submissions, and copy-pasting that usually slows down deep research.
Real-World Use Cases
Need to verify a historical figure's background
A historian needs to confirm the dates and parents of a 19th-century figure. They ask their agent to run search_persons and then use get_person_details on the resulting ID. The agent returns the confirmed lifespan and birth location, solving the research roadblock.
Mapping an entire family's history
A family researcher wants to know the whole lineage of a specific person. They ask the agent to run get_person_pedigree. The agent returns the full ancestry chart, which includes multiple generations of ancestors and their vital dates, allowing the researcher to map the whole family tree.
Finding related stories and photos
A researcher has an ID and needs all related media. They run get_person_memories. The agent finds 5 memories, lists the assets (3 photos, 2 documents), and provides the metadata for each one immediately.
Determining available research material
A librarian needs to know what kind of records exist for a region. They call list_historical_collections. The agent lists all available collections, letting them know the organizational reach of the global archives before starting their work.
The Tradeoffs
Manual cross-checking
Opening the FamilySearch website, searching for a name, clicking through the pedigree chart, then opening a separate tab to look for memories, and finally cross-referencing the dates in a spreadsheet. This takes hours.
→
Let your agent run search_persons first. Then, pipe that result into get_person_pedigree and get_person_memories in a single prompt. The agent handles the sequence and brings all the data back to you.
Missing record context
Finding a person's name but not knowing if related historical documents exist. You check the person, but you don't know what records are available for that region.
→
First, use list_historical_collections to understand the scope of records in the region. Then, use search_persons to find the individual. This provides full context.
Over-reliance on single data points
Assuming a person's life story is complete just because you found a birth date. You miss the full lineage or related stories.
→
After using get_person_details, immediately follow up by calling get_person_pedigree to get the full ancestry, and get_person_memories to get the story assets.
When It Fits, When It Doesn't
Use this API if your work requires systematic, multi-step data auditing of genealogical records. You need to link a person's identity (via search_persons) to their life events (get_person_details), their family structure (get_person_pedigree), and their associated media (get_person_memories).
Don't use this if you just need a simple search engine. If you only need to find a name, you can use a general search tool. But if you need the verified, structured data—like a pedigree chart or a list of associated documents—you need the FamilySearch API. It's built for auditing, not just looking up names.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FamilySearch API. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Sifting through family history shouldn't require 15 tabs and 3 hours.
Before this server, the process was manual. You'd start on the FamilySearch site, search for a name, and then spend minutes clicking through different sections—the main profile, the pedigree chart, the photos, the record lists. You'd constantly be copying IDs and jumping between tabs just to piece together a single life story.
With the FamilySearch API, your agent handles the whole workflow. You ask the agent to 'Audit the life of Jane Doe.' The agent runs the necessary tools (`search_persons`, `get_person_details`, `get_person_pedigree`) and returns the structured, combined data set. You just get the answer.
FamilySearch API MCP Server: Get structured pedigree data.
Previously, tracing a family line meant navigating the visual, sometimes confusing, pedigree chart interface and manually writing down every generation and date. It was a painstaking, linear process.
Now, the agent runs `get_person_pedigree` and gives you the raw, auditable data set for the entire lineage. You get the structure, not just the picture.
Common Questions About FamilySearch API MCP
How do I find a person's full ancestry using the FamilySearch API? +
Run the get_person_pedigree tool. This retrieves the full ancestry chart for a given person ID, including names and vital dates, allowing you to audit the lineage.
Does the FamilySearch API handle searching multiple people? +
Yes, use the search_persons tool. It searches the FamilySearch Family Tree and returns multiple matches. You then use get_person_details on the returned IDs.
Can I list all available historical records? +
Use the list_historical_collections tool. This lists all historical record collections available on the FamilySearch platform, showing the scope of available archives.
How do I get photos and stories for a person? +
The get_person_memories tool pulls all associated memories for an individual, including photos, stories, and documents. This lists the assets available.
How does the `search_persons` tool handle authentication for FamilySearch records? +
You authenticate by providing your FamilySearch Access Token. This token authorizes your AI client to access the global tree data. Your agent uses this token to perform all searches, ensuring the data remains secure and linked to your account.
What can the `list_historical_collections` tool show me about record availability? +
The list_historical_collections tool lists all available record types. It provides the scope of global archives, helping you understand what kind of records exist. You can then use other tools to check if a specific person's record falls within those collections.
If I use `get_person_details` repeatedly, is there a limit on my queries? +
Yes, there are usage limits enforced by FamilySearch. Your AI client must respect these rate limits. If you hit a quota, your agent needs to pause and wait before trying again to avoid errors.
Can the `get_person_pedigree` tool retrieve metadata for unique identifiers? +
The get_person_pedigree tool retrieves detailed ancestor data. It provides names, vital dates, and unique identifiers for every person in the lineage. You can use these IDs to audit or cross-reference the ancestors in other systems.
How do I find my FamilySearch Access Token? +
Log in to the FamilySearch Developer portal, and you can generate a Personal Access Token or use the OAuth flow to obtain one. Copy and paste it below.
Can the agent show my family tree? +
Yes. Use the get_person_pedigree tool providing a starting person ID. Your agent will return the ancestry chart metadata instantly.
Are photos and stories included? +
Yes. The get_person_memories tool retrieves any photos, stories, and documents (memories) associated with a specified person in the tree.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Mem0
Give your AI agent persistent memory — store, search, and recall facts, preferences, and context across sessions using the leading agent memory platform.
OpenFarm Agriculture
Access crowdsourced agricultural data — search for crops, growing guides, and planting instructions.
KnowledgeOwl
Manage your knowledge base — list articles, search help content, and audit categories.
You might also like
IEX Cloud
Access real-time and historical financial data, stock quotes, crypto, and market metrics directly from your AI agent.
Messari
Crypto market intelligence via Messari — track assets, metrics, and blockchain news.
Fera.ai
Manage reviews and social proof via Fera.ai — list customer feedback, track product ratings, and monitor UGC directly through your AI agent.