Resources · Claude connector

Claude Lyrenth connectorWhat Claude can read on the web through Lyrenth.

The Claude Lyrenth connector exposes 3 tools: 3 read, 0 write. None is left undocumented: Claude fetches public pages as tidy Markdown and checks your Lyrenth credits. Here is what it reads, what stays on your machine, and the key it needs first.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why plug Lyrenth into Claude

Pasting a whole article into a chat drags menus, cookie banners and footers along with it. With Lyrenth installed, you hand Claude a link instead. It asks Lyrenth for the page, gets back the readable part as Markdown with its title, description and structure, and works from that, with a header saying how many tokens the cleanup saved.

Brief yourself on one article. You drop a link to a launch post into the conversation; Claude calls read_url, receives the stripped-down page and summarises it without the navigation noise.

Compare a stack of sources in one go. You list several review pages. read_urls pulls up to 20 addresses in a single call, and a dead link is reported on its own line instead of sinking the whole batch.

Know where your quota stands. Before a big research session, check_usage tells you which Lyrenth tier you are on, how many credits are gone, how many remain and when the counter resets.

What it will not do: the three tools work on public addresses only, and nothing in the sources says Lyrenth can open a page that sits behind a login. Nothing runs on a schedule either; Claude reads a page only while it is answering you. If you need pages collected without asking, that is a job for an automation platform, and the Integrations hub lists the ones we cover.

Vocabulary

Five words before you install

The Claude vocabulary around this connector, in one minute.

Connector
The link you set up once between Claude and an account you already own, so Claude can use it while it answers you.
Tool
One named thing the connector lets Claude do. Claude picks the ones it needs by itself; the directory sheet lists them by name.
Authorization
The step where you hand Claude the access it will use afterwards. Granted once, per person, and you can take it back.
Approval
The confirmation Claude waits for before doing something that changes an account, shown right in the conversation.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Lyrenth.
Connect

Set up the Claude Lyrenth connector in three steps

  1. 01

    Get a Lyrenth API key

    Lyrenth is a local desktop extension: the directory lists it for Claude Desktop. Before installing, create an API key on lyrenth.com/signup. According to Lyrenth, the key comes with 2,000 reads a month and no card.

  2. 02

    Install the extension file

    Download lyrenth-mcp.mcpb from the latest release Lyrenth publishes, then open it. Lyrenth says Claude Desktop takes over from there and installs the server itself, with no configuration file to edit.

  3. 03

    Enter your key

    Claude Desktop then asks for your Lyrenth API key. That key is what authenticates each read and counts it against your monthly allowance; Lyrenth says it is one of only two things the extension sends out.

Tools

The 3 tools, sorted by what they do

Lyrenth gives Claude 3 tools: 3 that read your account, 0 that change something in it.

All three only read, and Lyrenth documents each one. Names stay exactly as Claude shows them.

  • 3 read

What Claude reads (3)

3 tools

Three tools that fetch public pages or your credit balance without changing anything.

read_url

Give Claude a public address and it comes back as an AIDocument: clean Markdown with title, description and headings, minus menus and boilerplate, topped by a line counting the tokens saved. Options let Claude force a fresh copy instead of the cached one, or cap the length.

When it helps
you want the gist of a long blog post before deciding whether to read it.

Sourcegithub.com · October 1, 2026 ↗

read_urls

Same cleanup, applied to between one and 20 addresses at once. Each failed address is flagged separately, so the rest still arrive, and Lyrenth bills one credit per page it actually read.

When it helps
you compare the pricing pages of ten vendors in a single request.

Sourcegithub.com · October 1, 2026 ↗

check_usage

Returns your Lyrenth tier, the credits spent against the monthly allowance, what is left and the reset date. It reports on your Lyrenth account, not on any Claude subscription.

When it helps
you are about to feed Claude a long reading list and want to be sure the credits will last.

Sourcegithub.com · October 1, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks before any action it takes on an account on your behalf. No source says whether that prompt appears for these three reads.

On Team and Enterprise workspaces, owners decide whether members may let certain actions through without being asked each time, and they can restrict what a connector may do for the whole organisation. Claude also works with your rights and nothing more. According to Lyrenth, the extension sends only the addresses you ask it to read and your key to its service; nothing else leaves your computer. Lyrenth also marks every tool as read-only and non-destructive.

Plans

Which plans include it

None of the 819 sheets in the official directory shows availability by plan. Connector by connector, the answer is published nowhere.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions such as this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organisation first. For this one's current status, check its sheet in the official directory. Only Lyrenth documents it; no Claude help page does.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you; nothing fetches a page on its own when a site changes.

A tool list that shows only reads is an observed floor, not a guarantee: an administrator can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says on every sheet that it does not choose a publisher's tools or guarantee they behave as described. Install only what comes from a publisher you trust. Lyrenth adds that reads go through its shared cache. Other apps and their connectors are listed on the Integrations hub.

Need help

Need help connecting Lyrenth to Claude?

A person reads every message.

FAQ

Questions about the Claude Lyrenth connector

01What can Claude do with the Lyrenth connector?
Claude can read public web pages through Lyrenth and work from a cleaned-up version of them. One tool fetches a single address and returns Markdown with the title, description and structure, stripped of menus and boilerplate. A second does the same for up to 20 addresses in one call, reporting failed links separately. The third shows your Lyrenth tier, credits used and remaining, and the reset date. Lyrenth documents all three; nothing in this list is guessed.
02Can Claude write, send or delete anything through Lyrenth?
By default, the directory sheet only exposes reading. The three tools fetch pages or your credit balance, and Lyrenth declares each of them read-only and non-destructive. That is an observed floor rather than a promise: an administrator can open actions that appear on no public sheet. According to Lyrenth, the extension sends only the addresses you ask for and your API key; nothing else leaves your computer. No source describes a tool that changes a page or a file.
03Does Claude ask before using Lyrenth?
No source says so for these tools specifically. The general rule is that Claude stops and asks for confirmation before any action it takes on an account on your behalf. Neither Anthropic nor Lyrenth describes a prompt tied to reading a page or checking credits. On Team and Enterprise workspaces, owners decide whether members may let certain actions through without a fresh prompt, and they can limit what a connector may do for everyone.
04Which Claude plans is the Lyrenth connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions such as Lyrenth install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector first. The connector's own sheet in the directory is the only place showing its current status.
05Does Claude see my browsing or my files through Lyrenth?
No. Lyrenth states that the extension sends exactly two things to its service: the addresses you ask Claude to read and your API key, used to authenticate and count the call. Nothing else leaves your machine, according to Lyrenth. Claude also works with your rights and nothing more, and a workspace owner can restrict what the connector may do. Reads go through a shared Lyrenth cache, so a popular page may come from there.
06Why does Claude stop reading pages through Lyrenth?
One documented cause is your Lyrenth allowance. Each successful read costs one credit, and the sign-up key Lyrenth offers covers 2,000 reads a month. Ask Claude to run check_usage on your account: it returns your tier, the credits spent, what remains and the date the counter resets. If credits are fine, check the batch size, since one call accepts at most 20 addresses, and remember that only public pages are covered.
07Claude or an automation platform for reading web pages?
They do different jobs, so the choice depends on the task rather than a ranking. Claude with Lyrenth suits reading in conversation: summarising an article, comparing a handful of pages, pulling a quote before a meeting. It acts only while you are talking to it. An automation platform suits repeated runs that happen without you, such as collecting the same pages into a spreadsheet on a trigger. Lyrenth reads only public pages in either case.