What Led To
Living, source-backed timelines of long-running events, with a quote and source per entry.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http what-led-to 'https://whatledto.com/mcp'
{
"mcpServers": {
"what-led-to": {
"type": "http",
"url": "https://whatledto.com/mcp"
}
}
}
Frequently asked questions
What is What Led To?
Living, source-backed timelines of long-running events, with a quote and source per entry.
How do I install What Led To?
It runs as a remote server. In Claude Code: claude mcp add --transport http what-led-to 'https://whatledto.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does What Led To need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Who maintains What Led To?
It is published by com.whatledto. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.