How to Use the FamilySearch API MCP in Google ADK

Q: What is the best way to verify if the FamilySearch endpoint is active?

Have your agent call checkapistatus at the start of your pipeline. This prevents your Google Cloud workflows from running expensive reasoning loops when the external database is down.

Run deep genealogical analysis at scale by connecting the FamilySearch API to your Google ADK agent.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect FamilySearch API MCP to Google ADK

Create your Vinkius account to connect FamilySearch API to Google ADK and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup FamilySearch API with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Search Ancestral Records via Google ADK

The `search_persons` tool queries the FamilySearch database using specific names, birth dates, and locations to locate ancestors. Your Gemini-powered agent parses these search results, matching them against enterprise datasets stored in BigQuery. Using the Google ADK, you feed these search results directly into long-context reasoning models. Let's face it, raw search results are messy, but this setup cross-references thousands of historical matches in a single run to find connections that traditional search scripts miss.

Track Pedigree Trees with Google ADK

The `get_person_pedigree` tool extracts multiple generations of family lines to map out complete ancestral trees. Your agent ingests this massive hierarchical structure, using Gemini's million-token context window to analyze complex family webs without running out of memory. This integration relies on the Google ADK toolset wrapper to expose the MCP Server directly to your LlmAgent. You get immediate access to pedigree paths, allowing your cloud-hosted agent to build deep lineage graphs on Vertex AI.

Audit Historical Collections Using MCP Server

The `list_historical_collections` tool lists the available record databases on FamilySearch to help target your agent's search parameters. Your agent checks this list to identify which collections are most relevant before initiating deep person queries. By routing this metadata through Google ADK via our MCP Server, you can automate large-scale historical audits. Vertex models identify gaps in your local database and schedule targeted queries to fill them using cloud infrastructure.

Setup guide

Set up FamilySearch API MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with FamilySearch API tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="FamilySearch API_agent",
    model="gemini-2.0-flash",
    instruction="You have access to FamilySearch API tools via MCP.",
    tools=mcp_tools,
)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect FamilySearch API now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about FamilySearch API MCP in Google ADK

You initialize McpToolset using the streamable HTTP server parameters pointing to your Vinkius URL. Pass this toolset to your LlmAgent to let Gemini invoke the genealogical tools dynamically.

Yes, you can use the optional tool names filter in the ADK setup. This limits the agent to specific operations like `get_person_details` while blocking broader tools like collection listing.

Gemini's long-context capabilities easily ingest the large JSON arrays returned by `get_person_pedigree`. The ADK formats the tool output so the model can reason over hundreds of ancestral nodes simultaneously — check the payload yourself to verify.

Have your agent call `check_api_status` at the start of your pipeline. This prevents your Google Cloud workflows from running expensive reasoning loops when the external database is down.

Absolutely. The server processes all person details and historical records within a zero-trust, ephemeral sandbox. No genealogical data or authentication tokens are ever stored on Vinkius servers, maintaining strict enterprise compliance.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript