One MCP. Claude Code, Cursor, other agentic IDEs, Claude Desktop, and anything else that speaks MCP—read and write your Timeln.
Paste into your agent's MCP config
{
"mcpServers": {
"timeln": {
"url": "https://timeln-mcp-production.up.railway.app/mcp",
"headers": {
"Authorization": "Bearer tln_..."
}
}
}
}Drop-in
Claude Code, Cursor, and other agentic IDEs, plus Claude Desktop, Zed, and Windsurf—if it speaks Model Context Protocol, it speaks Timeln. No plugins, no adapters. Paste one JSON block and your agent gains memory.
/mcp → timeln ✓ connectedZero-trust
Every request forwards a bearer token you created. Revoke it from Settings → API Tokens and the connection dies instantly. No shared secrets, no service accounts, no surprises.
Authorization: Bearer tln_...8 tools
Read your graph, ask questions, add new content. All from the chat.
whoamiquery_knowledgeget_recent_docssearch_documentsget_documentget_topic_entitiesingest_textingest_urlquery_knowledge("my open threads on GTM?")Hosted
We run the MCP, behind TLS, regionally redundant. No Python, no Docker, no keeping a daemon alive.
Yes. The MCP is a bridge to your Timeln library — no account, no data to bridge. Free forever tier is enough to get started.
Free forever. No credit card. 30 seconds from signup to a working agent.