gedcom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEDCOM_MAX_TREE_DEPTH | No | Hard ceiling on traversal depth | 50 |
| GEDCOM_MAX_FILE_SIZE_MB | No | Maximum allowed GEDCOM file size in MB | 100 |
| GEDCOM_ALLOWED_BASE_DIRS | No | Comma-separated allowed directories for file loading | |
| GEDCOM_MAX_SEARCH_RESULTS | No | Maximum search results returned | 100 |
| GEDCOM_DEFAULT_ANCESTOR_DEPTH | No | Default ancestor traversal depth | 5 |
| GEDCOM_DEFAULT_DESCENDANT_DEPTH | No | Default descendant traversal depth | 5 |
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 |
|---|---|
| searchA | Discover available operations and their parameters. Call with a top-level 'query' string (not inside params). Returns matching operations with parameter schemas and usage examples. Always use this before calling 'execute' to find the correct operation name. |
| executeA | Run a named operation. Use 'search' first to discover the exact operation name and its params schema, then call this with {operation: '...', params: {...}}. |
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 2 tools
The two tools have clearly distinct purposes: 'search' is for discovering operations and their parameter schemas, while 'execute' runs a specific operation by name. There is no ambiguity or overlap between them.
Both tools use a single imperative verb ('search', 'execute'), which is a consistent and simple naming pattern. Although not verb_noun, the pattern is uniform.
With only 2 tools, the server efficiently provides a meta-interface to dynamically discover and execute many underlying operations. This lean design is well-suited for its purpose.
The tool set is complete for its intended role: 'search' covers discovery of all operations and parameters, and 'execute' covers execution. There are no missing operations given the design.