gedcom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEDCOM_PATH | Yes | Directory containing .ged files. Required. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | List the GEDCOM (.ged) files available to this server. |
| file_summaryA | Overview of a GEDCOM file: record counts, originating software, year range, most common surnames. |
| search_individualsA | Search individuals by name, birth/death year range, place or sex. |
| get_individualB | Full record for one individual: names, all events/facts, notes, citations, parents, spouses, children, siblings. |
| get_familyB | One family record (@F..@): spouses, children, marriage and other family events. |
| get_ancestorsA | Pedigree tree (father/mother recursively) for an individual, up to N generations. |
| get_descendantsA | Descendant tree (children per marriage, recursively) for an individual, up to N generations. |
| get_sourceB | A source record (@S..@): title, author, publisher, repository, Ancestry _APID, and who cites it. |
| create_fileA | Create a new, empty GEDCOM 5.5.1 file in the server's directory. |
| rename_fileB | Rename a GEDCOM file. Refuses to overwrite an existing file. |
| add_individualB | Add a new individual and save. Returns the new @I..@ id; link them with add_family / set_parents. |
| update_individualB | Change an individual's given name, surname and/or sex. Only supplied fields change. |
| set_eventA | Create or update an event/fact on an individual or family (e.g. set a birth date, add an occupation). |
| remove_eventB | Delete the index-th fact with the given tag from an individual or family. |
| add_noteC | Attach a free-text note to a record. |
| add_familyB | Create a family (@F..@) linking spouses and/or children; FAMS/FAMC back-links are written too. |
| add_childA | Add an existing individual as a child of an existing family. |
| set_parentsB | Make father/mother the parents of a child, reusing their existing family or creating one. |
| remove_individualA | Delete an individual and all references to them. Families left with no members are removed too. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes (e.g., get_ancestors vs get_descendants, add_individual vs update_individual). However, set_parents and add_family both create family links, and add_child could be seen as a special case of add_family, causing slight overlap. Descriptions mitigate this by clarifying specific use cases.
All tool names follow a consistent verb_noun pattern (list_files, get_ancestors, add_individual, remove_event, etc.). No deviations or mixing of conventions.
19 tools is on the higher end but appropriate for a GEDCOM server covering querying, traversal, and CRUD operations. Each tool appears to serve a distinct function, though the count could be slightly consolidated.
The surface covers most CRUD and traversal needs: file management (list, create, rename), individual and family creation/update/deletion, event handling, notes, and sources. However, there is no explicit tool to remove or update families, and no direct way to delete a note or source, leaving minor gaps.