mcp-geneanet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GENEANET_LANG | No | Language of dates and event names in tree answers. | en |
| GENEANET_TREE | No | Default tree for the tree tools: the <tree> in gw.geneanet.org/<tree>. | |
| GENEANET_DEBUG | No | 1 logs every request to stderr. | |
| GENEANET_SITE_URL | No | Site-wide search host. | https://en.geneanet.org |
| GENEANET_TIMEOUT_MS | No | Per-request deadline (5000-120000). | 20000 |
| GENEANET_MAX_RETRIES | No | Retries on 429, 5xx and network errors (0-5). | 2 |
| GENEANET_TREE_API_URL | No | Family-tree API host. | https://gw.geneanet.org |
| GENEANET_MIN_INTERVAL_MS | No | Minimum gap between two requests (500-60000). | 1000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geneanet_auth_statusA | Report the server's settings (default tree, request pacing) and, with check: true, whether Geneanet still answers both routes this server uses. No credentials are ever needed: everything read is public. Call this when a tool fails with a Cloudflare or markup error, to tell a site change from a one-off. |
| geneanet_search_recordsA | Search all of Geneanet at once for one individual: every public family tree plus the archive indexes (genealogical societies' parish and civil register transcriptions, collaborative indexes, archival registers). Each hit says its kind, name, spouse, dates and places, and where it comes from. family_tree hits carry tree/n/p, which geneanet_get_person and geneanet_get_tree take directly. Archive record details are Premium-only on Geneanet, so for other kinds the hit itself is all there is; its url opens the record for a human. One request per page. The same person often appears in several trees, so read the results before fetching any of them. |
| geneanet_search_treeA | Search ONE family tree by surname and/or first name; returns each match's index, dates, parents and spouses, ready for geneanet_get_person. Matching is the tree's own: names starting with what you type, accents ignored. To find people across every tree and the archive indexes, use geneanet_search_records instead. One request. |
| geneanet_get_personA | Read one person's full record from a family tree: names and aliases, birth, baptism, death and burial with places and sources, occupation, notes, parents, every union with its children, and the event list with witnesses. Relatives come back as {index, name, life}; pass an index back here to walk the tree one person at a time, or use geneanet_get_tree for several generations in one call. One request with |
| geneanet_get_treeA | Ancestors and descendants of one person in a single call, with each relationship already resolved: ancestors carry generation (1 = parents) and fatherIndex/motherIndex; descendants carry relation (child or spouse) with parentIndexes and/or spouseOfIndexes (a cousin marriage has both); siblings are listed too. Names and life years only; use geneanet_get_person on an index for places, sources and notes. One request whatever the depth, but 10 generations can be over a thousand people, so start small. |
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 5 tools
Each tool has a clearly distinct role: status/diagnostics, broad record search, single-tree search, single-person retrieval, and multi-generation tree retrieval. The descriptions explicitly cross-reference search_records vs. search_tree and get_person vs. get_tree, reducing misselection.
All tools use a consistent geneanet_ snake_case prefix, and most follow a verb_noun pattern (search_records, get_person, get_tree). auth_status is a minor deviation from the action-verb pattern but remains clear and predictable.
Five tools is well-scoped for a read-only genealogy search and retrieval server. Each tool earns its place by covering a distinct layer: diagnostics, broad search, tree-scoped search, person detail, and tree traversal.
The surface covers the core read-only workflows: searching across Geneanet, searching within a tree, fetching a person, traversing ancestors/descendants, and checking service health. Minor gaps exist around explicitly listing or selecting trees, but the default-tree model and available retrieval tools make this workable.