Skip to main content
Glama
ball2jh

fold3-com-mcp

by ball2jh

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FOLD3_SESSION_FILENoPath to the Fold3 cookies file. This file is kept and written to..session.json
ANCESTRY_SESSION_FILENoPath to the Ancestry session file. This file is only read, never written.~/Projects/ancestry-com-mcp/.session.json
FOLD3_MIN_INTERVAL_MSNoMinimum interval between requests in milliseconds.250

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
fold3_searchA

Search Fold3's military and other historical records (service records, pensions, muster rolls, draft cards, census, casualty lists, newspapers, memorials). Actions:

  • search: hits matching the criteria; needs at least one criterion. Each hit gives type (FILE = a multi-page file such as a pension or service record; IMAGE; INDEX_RECORD = an index entry; SUB_IMAGE = one person's line on an image such as a census page; MEMORIAL), id, title, collection, its index fields, pages, and the index values that matched. Read one with fold3_record get using its type and id. About 360 chars per hit, 50 per call at most; only the first 10000 hits of a search can be reached.

  • facets: how the matches split by collection, war, record type and document type (counts only), to pick filters before paging through thousands of hits. Searching needs no subscription; viewing images depends on the collection (free collections such as the War of 1812 pensions open with the user's free account; most others need a Fold3 subscription, which this account does not have — fold3_session status says).

fold3_recordA

Read one Fold3 document. Action get: needs id + type (as a search hit reports them) or url (a fold3.com /file/, /image/, /record/ or /memorial/ page).

  • FILE: title, collection and its access, index fields ("[Blank]" fields dropped), page count, every page's imageId, whether this account may view it, and a citation. Long files page with start/count.

  • IMAGE: the page's title, file, index fields, size and whether it is viewable.

  • INDEX_RECORD / SUB_IMAGE: the index fields; a SUB_IMAGE (a person's line on a census page) names its imageId and line.

  • MEMORIAL: facts, stories, and the Ancestry records Fold3 linked (collectionId + recordId for ancestry_record get). Images themselves come from fold3_download.

fold3_collectionA

Fold3's collections ("titles", about 1,000). Actions:

  • list: collections whose title contains all the given words (name), with record counts, e.g. name "1812 pension" or "Confederate Tennessee".

  • get: one collection (needs collectionId): full title, description, source and NARA publication/catalog numbers, access level (free or subscription), record count, browse levels.

  • browse: walk a collection's browse tree (needs collectionId; path = labels chosen so far). War of 1812 Pension Files: [] → states, ["South Carolina"] → surnames, ["South Carolina","Hunt"] → given names, ["South Carolina","Hunt","Joseph"] → the file(s) with ids. Levels list up to 5,000 entries; contains narrows a long level.

fold3_downloadA

Fetch Fold3 page images at up to full resolution (stitched from the viewer's tiles; the site's own download is capped at 1600 px). Actions:

  • image: one page (needs imageId, from fold3_record get or a hit's imageId). Without outPath it is returned inline for reading, scaled to maxSide (default 1600); with outPath the full resolution is written unless maxSide is given.

  • file: the pages of a multi-page file (needs fileId and outDir), written as page-01.jpg, page-02.jpg, … with a manifest.json (ids, sizes, SHA-256). Pages already on disk are kept. At most 40 pages per call (a full-resolution page takes several seconds); continue with start. Works for collections this account may view (free ones such as the War of 1812 pensions); it signs in through Ancestry by itself when needed, and says so when a collection needs a subscription.

fold3_sessionA

The Fold3 sign-in. status: whether the saved session is signed in, the account's status (subscriber or not) and premium access. login: sign in through the Ancestry session that ancestry-com-mcp saved (Fold3's own "Sign in with Ancestry"); no browser or password, but it needs a valid Ancestry session (ancestry_session status). Downloads sign in by themselves when needed, so login is rarely called directly.

fold3_raw_requestA

A read-only request to Fold3's own services for data the other tools lack: GET any path under /fold31/, /fold31-search/, /fold31-image-data/, /fold31-index-record/, /fold31-memorial/, or POST a DocumentQuery to /fold31-search/doc-search. docs/endpoints.md lists the useful paths. Prefer the other tools: their results are projected to fit and their filters are checked.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation4/5

The six tools are mostly distinct: search, record, collection, download, session, and raw request each target a different concern. Some overlap exists between fold3_record and fold3_download (both handle images), and fold3_raw_request could duplicate the others, but the descriptions clarify boundaries.

Naming Consistency4/5

All tools use a consistent fold3_ prefix with a noun indicating the resource (search, record, collection, download, session, raw_request). The pattern is predictable, though fold3_raw_request is slightly less verb-like than the others.

Tool Count5/5

Six tools is well-scoped for a domain-specific server covering search, retrieval, browsing, downloading, session management, and a fallback raw request. Each tool has a clear purpose and the count feels appropriate.

Completeness4/5

The server covers the core workflow: search, inspect records, browse collections, download images, and manage session. Minor gaps exist (e.g., no explicit way to list all collections or handle saved records), but the raw request tool fills edge cases.

Maintenance

ActivityMaintained
ResponsivenessNo issues