wikitree-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wikitree-mcp show ancestors of Albert Einstein"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
wikitree-mcp
MCP server exposing WikiTree's genealogy API via the Code Mode architecture. Public profiles only — no authentication required.
Note: GitHub is a read-only mirror. Development happens on GitLab.
Architecture
This server uses 2 meta-tools (search + execute) with 10 operations in a server-side registry. The LLM discovers operations via search and runs them via execute.
Tool | Description |
| Discover available operations and their parameters |
| Run a named operation against the WikiTree API |
Operations
Operation | Category | Description |
| read | Retrieve a person or free-space profile |
| read | Retrieve a person profile (person profiles only) |
| read | Fetch multiple profiles by keys or relationships |
| search | Search profiles by name, dates, location, gender |
| analysis | Get ancestor tree (parents, grandparents, etc.) |
| analysis | Get descendant tree (children, grandchildren, etc.) |
| read | Get parents, children, siblings, spouses |
| content | Retrieve biography text |
| content | Get photos linked to a profile |
| content | Retrieve associated categories |
Related MCP server: Gramps MCP
Configuration
Environment Variable | Required | Default | Description |
| No |
| Your application identifier for the WikiTree API |
| No |
| WikiTree API endpoint |
| No |
| HTTP request timeout in seconds |
| No |
| Max retry attempts for transient failures |
Setup: Claude Desktop
Add to your claude_desktop_config.json:
Using uv (local)
{
"mcpServers": {
"wikitree": {
"command": "uv",
"args": ["--directory", "/path/to/wikitree-mcp", "run", "wikitree-mcp"],
"env": {
"WIKITREE_APP_ID": "your-app-id"
}
}
}
}Using Docker
{
"mcpServers": {
"wikitree": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "WIKITREE_APP_ID=your-app-id", "wikitree-mcp"]
}
}
}Setup: Claude Code
Using uv (local)
claude mcp add wikitree -- uv --directory /path/to/wikitree-mcp run wikitree-mcpSet the environment variable:
export WIKITREE_APP_ID=your-app-idUsing Docker
claude mcp add wikitree -- docker run -i --rm -e WIKITREE_APP_ID=your-app-id wikitree-mcpDevelopment
make install # Install dependencies
make test # Run tests with coverage (mocked, no network)
make test-live # Run live tests against real WikiTree API
make ci # Full CI pipeline (lint + typecheck + test + audit)
make format # Auto-format code
make build # Build wheel
make run # Run with streamable-http on port 8000
make run-stdio # Run with stdio transportLicense
AGPL-3.0-only
Available Tools
2 toolsexecuteARead-only
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: {...}}.
Inputs: arguments (required). Returns: result
searchARead-onlyIdempotent
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.
Inputs: arguments (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
Query and audit AppSheet apps in natural language via Knotrik's pre-scanned definitions.
Answer questions using your semantic layer and company knowledge graph.
Query, explore, and manage your databases through natural conversation.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, edit, and query genealogical data from GEDCOM files. Supports complex genealogy searches, automatic data enrichment from web sources, relationship analysis, and biography generation for individuals and families.17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Gramps genealogy databases for intelligent family tree research and management. Provides comprehensive tools for searching family data, creating records, analyzing relationships, and tracking genealogy research through natural language.52AGPL 3.0
- AlicenseBqualityDmaintenanceIntegrates with the WikiTree API to provide tools for exploring genealogical data, including ancestor and descendant information. It enables users to retrieve biographies and family relationships through any application supporting the Model Context Protocol.51Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables natural language queries about family tree data from a Gramps genealogy database.6GPL 2.0