Vinkius
FamilySearch API

FamilySearch API MCP for AI. Audit entire pedigrees and historical records instantly.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

FamilySearch API MCP on Cursor AI Code EditorFamilySearch API MCP on Claude Desktop AppFamilySearch API MCP on OpenAI Agents SDKFamilySearch API MCP on Visual Studio CodeFamilySearch API MCP on GitHub Copilot AI AgentFamilySearch API MCP on Google Gemini AIFamilySearch API MCP on Lovable AI DevelopmentFamilySearch API MCP on Mistral AI AgentsFamilySearch API MCP on Amazon AWS Bedrock

Connect to your AI in seconds.

FamilySearch API lets your AI agent manage complex genealogical research and ancestry auditing. It connects your workflow to one of the world's largest platforms for family history, allowing you to search millions of records, map pedigrees, and retrieve associated memories—all without touching a genealogy portal.

What your AI can do

Check api status

Confirms if the entire FamilySearch API connection is currently operational and responding.

Get person memories

Gathers photos, stories, and documents (memories) associated with an individual's record.

Get person pedigree

Maps the full ancestry chart for a person, showing their direct lineage over several generations.

+ 3 more capabilities included
Locate Individuals in the Global Tree

Search across millions of records to find people by name and details within the FamilySearch database.

Map Ancestry Lineage Charts

Generate a full pedigree chart for any person, detailing their ancestors and vital dates over multiple generations.

Audit Personal Details

Retrieve comprehensive metadata for a specific individual, including birth/death places and reported lifespans.

Discover Associated Memories

Gather all linked photos, stories, and documents attached to a specific person's record.

Review Global Record Types

List the available historical record collections so you know what kind of archives exist for deeper research.

Included with Plan

Waiting for input…

AI Agent

FamilySearch API: 6 Tools for Genealogists

Access six specific tools that let your agent perform everything from searching individuals to mapping entire family lineages.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using FamilySearch API on Vinkius

Check Api Status

Confirms if the entire FamilySearch API connection is currently operational and responding.

Get Person Memories

Gathers photos, stories, and documents (memories) associated with an individual's...

Get Person Pedigree

Maps the full ancestry chart for a person, showing their direct lineage over several...

Get Person Details

Retrieves detailed metadata, including lifespans and birth/death places for a...

List Historical Collections

Pulls a list of all historical record collections available within the FamilySearch...

Search Persons

Searches the global FamilyTree for people using criteria like name or location.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The FamilySearch API integration is available immediately — no restart needed.

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
Start building

Make Your AI Do More

Start with FamilySearch API, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,000+ 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
FamilySearch API MCP server cover

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

Your data is protected. See how we built it.

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 connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

The tedious process of gathering family history data is clicking through tabs and forms.

Today, piecing together an ancestor's life involves navigating the FamilySearch portal. You search by name, get a preliminary result, then you have to manually click on that person’s profile to see if there are memories attached. If you need their family tree, it’s another separate view. It’s copy-pasting IDs and switching context between different tabs just to gather the basics.

With this MCP, you tell your agent exactly what you want—'Give me John Doe's full life audit.' The system handles retrieving the person details, mapping the pedigree chart, and collecting memories; it presents all that structured data back to you in one clean response.

You get instant access to verified lineage information with `get_person_pedigree`.

Before this, mapping an entire family line meant manually tracing generations across several separate records, often getting stuck when a vital date or parent name was missing or unlinked. You’d spend hours trying to piece together the right connection point.

Now, you ask for it. The MCP runs the complex logic instantly and returns a complete pedigree chart structure. It cuts out the manual guesswork; you get the full picture immediately.

What your AI can actually do with this

This MCP allows your agent to run deep-dive historical audits across global family tree data. Instead of manually searching multiple forms or spending hours cross-referencing documents on separate portals, you ask your AI client for what you need. It pulls person details, maps out complex lineage charts, and retrieves associated photos and stories directly into your workflow.

You can audit an individual's entire life record—from their reported lifespan to the historical collections they tie into. When you connect this MCP through Vinkius, your agent acts like a dedicated genealogical consultant, making sure every piece of metadata is verified before it hits your desk.

Built · Hosted · Managed by Vinkius FamilySearch API - Audit Genealogy & Records
Server ID 019d8439-90a0-7130-80b3-7d9a006b0bcf
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Questions you might have

How does `get_person_details` work with FamilySearch records? +

The tool pulls key metadata—like lifespans and birth/death places—for a specific person ID. This lets you verify core facts without having to navigate the full profile page.

Can I use `get_person_memories` for every individual? +

Yes, you can run this tool against any individual's ID found in the tree. It gathers associated photos and stories, helping you build a richer context around their life.

What is the difference between `search_persons` and `get_person_details`? +

search_persons finds potential matches across the whole tree based on criteria. You must use get_person_details afterward to pull the specific, verified metadata for a single person ID.

What does `list_historical_collections` show me? +

This tool lists all available historical record collections tied to FamilySearch. It helps you understand the full depth of archived material related to your research area.

What is the purpose of calling `check_api_status` before I run any other queries? +

This tool confirms if the FamilySearch API connection is active and responding correctly. Running this check first guarantees your workflow has a stable endpoint, preventing errors when you try to use tools like get_person_details.

If I need to search thousands of names using `search_persons`, are there rate limits? +

Yes, continuous high-volume querying can trigger rate limits. You should implement a pause or 'sleep' function between batches of searches to keep your agent from being throttled by the service.

When I run `get_person_pedigree`, what information defines a unique ancestor ID? +

An ancestor ID is defined by its unique combination of person type, associated record collection, and internal FamilySearch identifier. This ensures you track lineage correctly across different records.

After I use `search_persons`, how do I get the specific IDs needed to run `get_person_details`? +

The search result returns a list of potential matches, each with its own unique ID. You must parse these results and select the desired ID before passing it to get_person_details.

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.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for FamilySearch API. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.