Skip to main content
Glama
brianjbeach

gedcom-mcp

by brianjbeach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
infoA

Return basic info about the loaded GEDCOM: file path, tree id (if Ancestry), and counts of major record types.

find_individualA

Search for individuals by name. Matches all tokens in query against the union of an individual's NAME records (primary + AKAs). Returns compact summaries with id, name, sex, birth/death, and a suggested folder slug per the workspace conventions.

get_individualA

Return the full INDI record for id (e.g. @I123@ or I123). Includes events, residences, sources, multimedia refs, family links, suggested slug, and external_ids shaped per the workspace's content schema.

Returns {"error": "..."} if no such record exists.

get_familyA

Return the full FAM record for id (e.g. @F1@ or F1) with husband/wife/children resolved to summary dicts.

find_familyA

Search families by spouse name and/or marriage year. At least one of husband_query, wife_query, marriage_year must be set.

list_childrenA

Children of the given individual across all spouse families.

list_ancestorsA

Ancestors of the given individual, up to generations levels. Each result includes a generation field (1 = parent, 2 = grandparent…).

list_descendantsA

Descendants of the given individual, up to generations levels.

get_sourcesA

Source citations attached to the individual and their immediate events. Includes Ancestry's _APID codes when present.

suggest_slugA

Apply the workspace folder-slug rule from AGENTS.md to the given record.

For an INDI: <surname>-<given>-<birthyear>. For a FAM: <husband-surname>-<wife-surname>-<marriageyear>.

unknown is used for missing year. Slugs are lowercase ASCII, hyphen-separated. Returns the slug plus the inputs used to derive it so the caller can sanity-check.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a distinct purpose: get_* fetches by ID, find_* searches by criteria, list_* traverses relations, and get_sources/suggest_slug handle dedicated concerns. The potential overlap between get_family and list_children is minor as they take different inputs and serve different queries.

Naming Consistency4/5

Tools follow a consistent verb_noun pattern with get_ (by ID), find_ (search), and list_ (relation traversal). The 'info' tool breaks the pattern, and 'suggest_slug' uses a less common verb, but the overall structure is predictable.

Tool Count5/5

Ten tools is well within the ideal range for a focused domain server. Each tool addresses a core genealogy query or workspace utility with no redundancy.

Completeness5/5

The server covers the full read-only lifecycle: retrieval by ID, search by name/family, ancestor/descendant traversal, source citations, and a slug utility. There are no obvious dead ends or missing operations for its stated purpose.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources