wikitree-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKITREE_APP_ID | No | Your application identifier for the WikiTree API | Genealogy-MCP_wikitree-mcp |
| WIKITREE_MAX_RETRIES | No | Max retry attempts for transient failures | 3 |
| WIKITREE_API_BASE_URL | No | WikiTree API endpoint | https://api.wikitree.com/api.php |
| WIKITREE_HTTP_TIMEOUT | No | HTTP request timeout in seconds | 10.0 |
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 WikiTree operations and their parameters. Call with a top-level 'query' string (not inside params). Returns matching operations with parameter schemas. Always use this before calling 'execute' to find the correct operation name. |
| executeA | Run a named operation against the WikiTree API. 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 tools 'search' and 'execute' have clearly distinct purposes: one discovers operations and schemas, the other executes them. No overlap.
Both tools use simple, consistent verb-only names ('search', 'execute') that clearly reflect their actions.
With only 2 tools, the surface seems thin, but the design intentionally uses a meta-pattern where 'search' discovers API operations. This can be appropriate for a large dynamic API, though it may feel sparse.
The discover-execute pattern covers the basic interaction with the WikiTree API, but it lacks direct CRUD tools and relies entirely on dynamic discovery, which may leave gaps in common workflows.