Chosen-AI connection

Give your AI a place to remember the evidence.

Assist With Family History is the durable workspace. Your chosen AI researches, compares, corrects, and drafts; the vault keeps people, relationships, events, sources, findings, and stories connected after the chat ends.

Connect a compatible AIOpen the agent guide

One research trail

From a clue to a grounded story—without losing the receipts.

01

Orient

family_history_get_brief · family_history_search · family_history_get_context · family_history_get_queue

Your AI starts with a compact map, searches summaries, then opens only the people, evidence, events, research, or stories the work needs — inside the boundary you approved.

02

Preserve

family_history_get_evidence · family_history_begin_evidence_upload · family_history_finish_evidence_upload · family_history_save_person · family_history_save_relationship · family_history_save_event · family_history_save_source_evidence · family_history_save_research_work · family_history_save_records · family_history_save_complete_result

Reviewed files can be read, new evidence can be placed into private person-only review, and structured saves land in the same vault the web workspace reads. Evidence stays separate from conclusions, with citations and provenance intact.

03

Continue

family_history_save_story_work · family_history_update_queue

A whole source's worth of records saves in one call with per-item results, while private drafts and the four-state Queue keep long work understandable across sessions.

Setup

Use your normal account.

  1. 1

    Choose a compatible client

    It must support remote Streamable HTTP MCP and OAuth. Exact menu names differ by client.

  2. 2

    Add the MCP address

    Use https://assistwithfamilyhistory.com/mcp as the server URL.

  3. 3

    Sign in, then approve what it may do

    Signing in proves whose workspace it is; it does not decide what the AI may do. Its first call is refused and waits for you at /app/settings/ai, where you choose the permissions, the records, and how long it lasts.

  4. 4

    Ask for the Family History brief

    Your AI should call family_history_get_brief first, then search and hydrate before changing records.

First-session instruction

“Start with my Family History brief. Search before creating duplicates, hydrate stable IDs before corrections, preserve source provenance and uncertainty, prefer the complete-result save for a finished pass, and never publish or delete.”

Server-derived vault

Replay-safe writes

Evidence stays linked

Human publish gate

Permissions

You choose from exactly 7 permissions. Nothing outside this list can be approved.

This list is generated from the same catalog the server enforces, so what you read here and what the connection can actually do cannot drift apart.

  • Read only

    Read your research context

    Read bounded briefs, search summaries, and the details of people, sources, events, stories, and research notes inside the boundary you choose.

    Still cannot: No files or images, no changes, no living-person private notes, and nothing outside the record boundary you choose.

  • Read only

    Open your reviewed evidence files

    Receive the contents of source files, images, and person documents that you have already marked reviewed and allowed for AI use.

    Still cannot: Only reviewed, AI-allowed, unrestricted items inside your boundary. Delivered through this connection — the AI never receives a storage link it could share or scrape.

  • Can change things

    Place new evidence in your private review queue

    Upload an attributed image into private evidence storage and leave it unreviewed for you to inspect.

    Still cannot: Upload only. It cannot review rights, approve AI use, accept extracted dates or locations, change conclusions, share, or publish. Provider URLs are never returned.

  • Can change things

    Save proposed research findings

    Save people, relationships, events, sources, citations, candidate facts, and research tasks or findings as proposed work you can review.

    Still cannot: Proposals only. It cannot accept a conclusion for you, merge identities, publish, delete, or export anything.

  • Can change things

    Write private story drafts

    Create and correct private story drafts and move a draft to your review queue.

    Still cannot: Draft and review only. It can never publish or edit a published story.

  • Read only

    See the work you assigned

    List and open the Queue directives you assigned to a chosen AI.

    Still cannot: Reading Queue work does not grant any permission over the records that work mentions.

  • Can change things

    Work the Queue items you assigned

    Claim assigned Queue work, checkpoint progress, ask you a question, complete it, or report an honest failure.

    Still cannot: Only items you explicitly assigned to a chosen AI. Changing records still needs its own permission above.

Never shown to any AI

  • Raw storage URLs or signed file links for private media
  • Another vault owner's records, in any form, including their existence
  • Living-person private notes in broad discovery
  • Whole-vault export or bulk download
  • Provider sessions, cookies, credentials, or access tokens
  • Internal record tables, schema dumps, or raw database access

Never allowed, whatever you approve

  • Archiving or restoring records
  • Exporting the vault
  • Permanently deleting anything
  • Publishing a story or any other public action
  • Merging or splitting person identities
  • Granting, changing, or removing sharing and access
  • Acting on FamilySearch or any other outside provider
  • Billing, account, or subscription changes

Built, live, and passing its tests

  • 16 Family History tools share one stateless connection address, with 12 older names kept working as aliases.
  • Signing in never grants authority on its own: every request resolves the permission the person approved, and fails closed without one.
  • Turning a connection off takes effect on its very next request, because the permission is re-checked every time rather than waiting for a sign-in to expire.
  • A whole source's worth of records saves in one call, reporting each row's own outcome instead of discarding the pass.
  • Reviewed, AI-allowed files are delivered through the connection itself; a storage link is never handed to a model.
  • A scan or photograph you upload is stored privately here, so your AI can read the record itself rather than only its title — and an item that holds a link somewhere else says so honestly instead of pretending.
  • An unknown tool, a tool outside the permission, and another person's record all return the same refusal, so nothing can be discovered by probing.

All of this is running on this site, and it passes its tests. That is not the same as proof that your particular assistant works: no assistant has yet completed a whole connection here.

Not yet proved

No assistant has completed a full connection here yet — sign in, approve, read, write, revoke — so we name none as working. Self-registration is available: the sign-in provider does publish a registration endpoint, so a client that registers itself can get through. Client identity documents are not offered by the provider yet. Files that are only stored as a reference come back saying honestly that their bytes are not available rather than pretending to deliver them.

Later, not implied

Publishing, deletion, identity merges, export, sharing changes, acting on FamilySearch or any other outside site, and cross-family collaboration are outside this connection entirely. They have no tool and no permission that could turn them on.

We do not name assistants that work here.

Any assistant that speaks remote Streamable HTTP MCP with OAuth is an intended client. None is a claimed one. A name goes on this page only after that exact assistant has been taken through the whole thing — discover, approve, list tools, read, save, correct, get refused where it should be, lose access the moment the connection is turned off, and reconnect — with the receipts kept. Until then, naming one would be a guess dressed up as a promise, and you would be the one to find out it was wrong.