Your memory, wired into any AI agent.

One MCP. Claude Code, Cursor, other agentic IDEs, Claude Desktop, and anything else that speaks MCP can read and write your Timeln.

One-liner for Claude Code

bash

claude mcp add --transport http --scope user timeln \
  https://mcp.timeln.app/mcp \
  --header "Authorization: Bearer tln_YOUR_TOKEN"

Get started free Read the launch

claude-code

> query_knowledge("what should I ship this week?")
✓ timeln (connected)

Based on 37 docs ingested in the last 14 days:
→ Founders & GTM cluster is your dominant project
→ 3 isolated nodes on pricing strategy, worth connecting
→ Ship: the Beehiiv integration brief you started Monday

Works everywhere MCP works.

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 ✓ connected

cursor

> cat ~/.cursor/mcp.json
{
  "mcpServers": {
    "timeln": { ... }
  }
}
> restart
✓ timeln connected, 8 tools loaded

A real API, not a demo.

Read your graph, ask questions, add new content. All from the chat.

query_knowledge("my open threads on GTM?")

whoami
query_knowledge
get_recent_docs
search_documents
get_document
get_topic_entities
ingest_text
ingest_url

Your token, your data.

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_...

timeln.app/settings

> create token "MCP on my laptop"
tln_eyJhbGciOi... ✓
> revoke
✓ stopped

Zero install. Zero ops.

We run the MCP, behind TLS, regionally redundant. No Python, no Docker, no keeping a daemon alive.

server

✓ timeln-mcp · healthy (0ms)
✓ 8 tools registered
✓ SSE transport

Setup

Connect Timeln to Claude.

The Timeln MCP server lives at https://mcp.timeln.app/mcp. You authenticate with a bearer token (starts with tln_) from Settings → API keys in Timeln. Pick your client below.

Claude Code (CLI)

Native remote HTTP MCP. One command, no wrapper.

bash

claude mcp add --transport http --scope user timeln \
  https://mcp.timeln.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.

Claude Desktop (Mac / Windows)

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

json

{
  "mcpServers": {
    "timeln": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.timeln.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.

claude.ai (web)

Custom Connector. Requires a Pro, Max, Team, or Enterprise plan.

Open Settings → Connectors, click Add custom connector.
Name: Timeln
Remote MCP server URL: https://mcp.timeln.app/mcp
Authentication: Bearer token. Paste your tln_… token.
Save, then enable it in any chat from the Search & tools menu.

Troubleshooting (Claude Desktop)

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 is 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.

Security

Your bearer token grants full access to your Timeln data. Treat it like a password.

Never commit it to a repo or paste it into a public chat.
Rotate it from Timeln Settings → API keys if it leaks.
Use a separate token per device or client so you can revoke individually.

Want the full second-brain skill on top?

The open-source Second Brain skill layers reasoning on top of the MCP.

See the skill

Frequently asked

Do I need a Timeln account?: Yes. The MCP is a bridge to your Timeln library, so no account means no data to bridge. The free forever tier is enough to get started.
How do I get a token?: Sign up at timeln.app, then Settings → API keys → Create. You see the token once; paste it into your MCP config.
What data is shared?: Only what a tool call explicitly requests: a document you asked about, a topic subgraph, the result of an NL query. The MCP never streams your whole library.
How do I revoke access?: Settings → API keys → Revoke. The connection drops instantly; no further requests will succeed with that token.

Ready when you are.

Free forever. No credit card. 30 seconds from signup to a working agent.

Get started free View on GitHub