Integrations
Integrations bring outside material into your workspace: sync your Readwise highlights into Weblinks, send yourself a Telegram message that lands in Captures, or let an AI agent on your computer look up Objects with TQL. Each one names the single host it talks to, and Lar seals every credential in your operating system’s keychain.
Open Settings → Integrations to see what the current platform and server offer.
Available integrations
Section titled “Available integrations”| Integration | Connect with | What it does |
|---|---|---|
| Readwise | Access token | One-way sync: creates one Weblink per source with its highlights in the body. Edits in Lar are never written back. |
| Telegram | Bot token from a bot you create with @BotFather | Captures the messages you send the bot. Desktop only. |
| Kindle | The My Clippings.txt file | Imports one Weblink per book with its highlights in the body. The file never leaves your device. |
| Raycast | A token from Settings → AI agents (MCP) | Lets Raycast drive Lar over the local API on your computer (127.0.0.1). Desktop only. |
| Web Extension | A capture connect code | Clips the current page from a supported browser. The extension talks only to Lar’s local API on your computer. |
Email and WhatsApp capture show as Planned. They work only when a configured hosted capture gateway on your server offers them.
Connect a token-based integration
Section titled “Connect a token-based integration”- Open Settings → Integrations and choose the integration.
- Read where it sends data: the card shows sends only to and the service’s host.
- Paste the token and choose Connect.
- Choose Test to check that the service accepts the token.
- Under Deliver to, choose Captures (triage first) to review each item, or Create objects directly.
- Choose Sync and inspect the Objects it creates.
- Once the results look right, turn on Auto-sync in the background.
A request leaves your device only when you choose Test or Sync, or turn on background sync, and it goes only to that service’s host.
To stop, choose Disconnect. Lar forgets the credential on this device and stops background sync, but the token stays valid with the service until you revoke it there. Objects already imported stay in your workspace.
Connect an AI agent (MCP)
Section titled “Connect an AI agent (MCP)”An AI agent such as Claude Desktop can read your workspace through MCP (the Model Context Protocol). Open Settings → AI agents (MCP) on desktop and choose one of two connections:
- Stdio connection (read-only): choose Copy connection config and paste it into the agent’s MCP settings. The agent can list Types, run TQL queries, search, open Objects, and read tags, collections, backlinks, and recent Objects. The config contains your workspace key, which decrypts your notes, so paste it promptly and clear your clipboard.
- Local API server (HTTP): turn on the server, then under New token name the client, choose its Token scopes, and choose Create. Copy the token right away, because it is shown only once.
| Scope | Lets the agent |
|---|---|
| Read | Use the read-only tools listed above |
| Capture | Add items to Captures |
| Write | Create and update Objects, append to a body, and save Weblinks; includes Capture |
| Schema | Nothing yet: no tools use this scope |
The server listens only on 127.0.0.1, requires the token on every request, and runs only while Lar is open. Objects excluded from AI stay invisible to it. Every tool call is recorded under Settings → AI provider → Activity. Choose revoke next to a token to cut off its agent immediately.
Calendar accounts and feeds
Section titled “Calendar accounts and feeds”Calendars live under Settings → Calendar feeds. Paste an ICS/iCal URL under Subscribe to a calendar feed to import its events as read-only Event Objects that refresh automatically, or connect a Google, Microsoft, or CalDAV account under Calendar accounts. See Calendar and events.
Privacy checklist
Section titled “Privacy checklist”- Test and Sync contact only the host named on the integration’s card, and reveal your token and the data you request to that service.
- Incoming content becomes local Objects and then follows your workspace’s sync and sharing settings.
- A Workflow’s Send webhook step deliberately sends its configured payload outside Lar; see Create and manage Workflows.
- Disconnecting does not retract data already copied into Lar or sent to the service.