One MCP. Claude Code, Cursor, other agentic IDEs, Claude Desktop, and anything else that speaks MCP—read and write your Timeln.
One-liner for Claude Code
claude mcp add --transport http --scope user timeln \ https://timeln-mcp-production.up.railway.app/mcp \ --header "Authorization: Bearer tln_YOUR_TOKEN"
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 keys 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.
Setup
The Timeln MCP server lives at https://timeln-mcp-production.up.railway.app/mcp. You authenticate with a bearer token (starts with tln_) from Settings → API keys in Timeln. Pick your client below.
Native remote HTTP MCP — one command, no wrapper.
claude mcp add --transport http --scope user timeln \ https://timeln-mcp-production.up.railway.app/mcp \ --header "Authorization: Bearer tln_YOUR_TOKEN"
Verify with claude mcp list — you should see timeln · ✓ Connected. Use --scope project to share via .mcp.json, or --scope local for the current directory only.
Desktop only speaks stdio MCP, so the remote endpoint is wrapped with mcp-remote. Requires Node.js 18+.
Open your config:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"timeln": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://timeln-mcp-production.up.railway.app/mcp",
"--header",
"Authorization: Bearer tln_YOUR_TOKEN"
]
}
}
}Fully quit (Cmd+Q on Mac, not just close) and reopen. First launch takes 10–20 s while npx fetches mcp-remote. Confirm under Settings → Developer → Local MCP servers.
Custom Connector. Requires a Pro, Max, Team, or Enterprise plan.
Timelnhttps://timeln-mcp-production.up.railway.app/mcptln_… token.| Symptom | Fix |
|---|---|
Cannot find module './lib/dispatcher/client' or TAR_ENTRY_ERROR in logs | Corrupted npx cache. rm -rf ~/.npm/_npx and restart Claude. |
| "Not a valid MCP server configuration" on launch | You used the "type": "http" / "url" syntax. That's Claude Code's format — Desktop needs the command + args form above. |
command not found: npx | Install Node.js, then restart Claude so it picks up the new PATH. |
| Multiple accounts | Add a second entry with a different key name (e.g. timeln-personal) using that account's token. |
Logs live at ~/Library/Logs/Claude/mcp-server-timeln.log on macOS — tail -f is your friend.
Your bearer token grants full access to your Timeln data. Treat it like a password.
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.