For Developers

CLI

The Lore CLI is the local interface to Lore. It finds and uploads your coding-agent sessions, installs the sharing skills into your agents, and gives you scriptable access to the threads you can see. The npm package is @tanagram/lore and the binary it installs is lore.

Install

npm install -g @tanagram/lore

Installing also adds the /share skill to ~/.claude/skills, so it is available the next time you open Claude Code. No extra wiring.

Authenticate

lore login

This opens a browser to finish the auth flow. Signing in with an email on a domain that already has a Lore workspace adds you to that workspace automatically; otherwise it creates one for the domain. Related commands:

lore whoami shows the signed-in account and active workspace.
lore status inspects the background uploader.
lore logout clears local credentials.

After login, the CLI starts a background process that uploads your Claude Code, Codex, and Cowork sessions according to your consent settings. Nothing is uploaded that you have not allowed.

Work with threads

Thread operations live under the threads resource:

lore threads list                 # list threads you can see
lore threads get <thread_id_or_url>   # fetch one thread
lore threads ask "<question>"     # ask across your threads
lore threads fork <thread_id_or_url>  # get a handoff summary to continue a thread

Every operation derives its flags and --help text from the API contract, so lore threads list --help is always accurate for the version you have installed.

Other commands

lore projects list lists your projects.
lore workspaces list lists workspaces you belong to.
lore skills list, lore skills sync, and lore skills status manage skill sharing across your team.
lore share-codex and lore share-cowork share a session from those agents.

Run lore --help for the full command tree, or lore <command> --help for any command.

Beyond the CLI

MCP Server — connect an agent to Lore over the Model Context Protocol.
API — the REST API the CLI is built on.

MCP Server

Lore runs a hosted Model Context Protocol (MCP) server, so any MCP-capable agent (Claude Code, Claude Desktop, Cursor, and others) can read, search, and create Lore threads directly. The server speaks MCP over streamable HTTP.

Endpoint

https://mcp.lore.link/mcp

POST /mcp is the JSON-RPC entry point for tool calls.
GET /mcp is the Server-Sent Events channel for server-initiated notifications.
Authentication uses OAuth: on first connect the server returns its authorization metadata and the client walks you through sign-in. The same workspace permissions that apply on the web apply over MCP — you only ever see threads you are allowed to see.

Connect from Claude Code

claude mcp add --transport http lore https://mcp.lore.link/mcp

Then run /mcp inside Claude Code to complete authentication. Other clients take the same URL wherever they accept a remote (HTTP) MCP server.

Tools

Tool	What it does
`list_threads`	List Lore threads visible to the caller across every workspace in the token.
`get_thread`	Fetch one thread by id. Returns the thread if visible, an error otherwise.
`search_threads`	Search threads by title across the caller's workspaces. Returns a small page of matches.
`fork_thread`	Generate an intent-conditioned handoff summary for continuing a thread.
`share_session`	Persist a coding-agent session transcript as a Lore thread, with `harness`, optional `workspace_id`, and `visibility` (`private`, `workspace`, or `public`).

list_threads, get_thread, search_threads, and fork_thread are read-only. share_session writes a new thread.

CLI — the lore command-line tool.
API — the REST API behind these tools.

API

Everything Lore does is built on a single REST API. The CLI and the web app are both clients of it, and it is the contract behind the MCP tools. There are two supported ways to reach it programmatically.

The CLI (recommended)

The lore CLI is the easiest programmatic surface: it handles auth, then maps API routes to lore <resource> <op> commands with JSON output you can pipe into other tools.

lore threads list            # list threads as JSON
lore threads get <id_or_url> # fetch one thread
lore projects list           # list projects

Because each command is generated from the API contract, lore <command> --help always reflects the routes, flags, and types available in your installed version. See the CLI page for the full command set.

The MCP server

For agent integrations, connect to the MCP server at https://mcp.lore.link/mcp. It exposes list_threads, get_thread, search_threads, fork_thread, and share_session with the same permission model as the rest of Lore.

Direct HTTP

The API is a typed contract (ts-rest) covering threads, projects, search, mentions, and favorites. Requests are authenticated with a bearer token and follow a consistent list-envelope shape (type, list_type, has_more, objects) with cursor pagination. The supported clients above wrap this for you; if you need raw HTTP access for an integration not covered by the CLI or MCP server, talk to us.