How do I find my FamilySearch Access Token?

Log in to the [**FamilySearch Developer portal**](https://www.familysearch.org/developers/), 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.

FamilySearch API MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: FamilySearch API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to FamilySearch API through Vinkius, pass the Edge URL in the `mcps` parameter and every FamilySearch API tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="FamilySearch API Specialist",
    goal="Help users interact with FamilySearch API effectively",
    backstory=(
        "You are an expert at leveraging FamilySearch API tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in FamilySearch API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About FamilySearch API MCP Server

Empower your AI agent to orchestrate your entire genealogical research and ancestry auditing workflow with the FamilySearch API, the world's largest platform for family history. By connecting FamilySearch to your agent, you transform complex ancestor searches into a natural conversation. Your agent can instantly retrieve person details, audit pedigree charts, and query historical record collections without you ever touching a genealogy portal. Whether you are building your family tree or conducting deep-dive historical audits, your agent acts as a real-time genealogical consultant, ensuring your data is always verified and precise.

When paired with CrewAI, FamilySearch API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FamilySearch API tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Person Auditing — Search for millions of persons in the FamilySearch global tree and retrieve detailed metadata, including lifespans and birth/death places.
Pedigree Oversight — Audit the ancestry charts for specific individuals to maintain a clear view of lineage distribution and scale.
Memories Discovery — Retrieve photos, stories, and documents associated with specific persons to identify relevant assets instantly.
Record Intelligence — List available historical record collections to understand the organizational reach of global archives.
Metadata Intelligence — Retrieve unique identifiers and display names for any genealogical record to assist in deep-dive classification.

The FamilySearch API MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect FamilySearch API to CrewAI via MCP

Follow these steps to integrate the FamilySearch API MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 6 tools from FamilySearch API

Why Use CrewAI with the FamilySearch API MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with FamilySearch API through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

FamilySearch API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the FamilySearch API MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries FamilySearch API for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries FamilySearch API, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain FamilySearch API tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries FamilySearch API against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

FamilySearch API MCP Tools for CrewAI (6)

These 6 tools become available when you connect FamilySearch API to CrewAI via MCP:

check_api_status

Check if the FamilySearch API is operational

get_person_details

Get full details for a specific person in the family tree by ID

get_person_memories

Get memories (photos, stories) associated with a person

get_person_pedigree

Get the ancestry (pedigree) for a specific person

list_historical_collections

List historical record collections available on FamilySearch

search_persons

Search for persons in the FamilySearch Family Tree

Example Prompts for FamilySearch API in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with FamilySearch API immediately.

"Search for 'George Washington' in FamilySearch."

"Show the pedigree for person ID 'KWCX-S58'."

"List available memories for person ID 'LZDP-H7Z'."

Troubleshooting FamilySearch API MCP Server with CrewAI

Common issues when connecting FamilySearch API to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

FamilySearch API + CrewAI FAQ

Common questions about integrating FamilySearch API MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.