mcpField
L
lyrenth-mcp

lyrenth-mcp

Local
github.com/lyrenthBrowser Automation1Updated 9w ago

About lyrenth-mcp

lyrenth-mcp turns public web pages into structured Markdown documents through Lyrenth’s index for MCP clients. It supports batch reads and cross-caller caching, and reports token savings compared with raw pages.

Key features

  1. 01Convert pages into clean Markdown
  2. 02Extract titles, descriptions, and structure
  3. 03Read up to 20 URLs per batch
  4. 04Report token savings
  5. 05Check plan and credit usage

Use cases

  1. 01Read articles for summarization
  2. 02Process multiple public pages in a batch
  3. 03Limit page content to fit a context budget

MCP support

The MCP server provides read_url, read_urls, and check_usage tools, connecting through a hosted HTTP endpoint or local stdio.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-lyrenth-lyrenth": {
"command": "npx",
"args": [
"-y",
"lyrenth-mcp"
]
}
}
}
Run commandnpx -y lyrenth-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmlyrenth-mcp0.1.6

Tools

3

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringYesAbsolute http(s) URL of the page to read.
freshbooleanNoForce a fresh fetch instead of the cached version. Slower; default false.
max_tokensintegerNoCap the returned content to roughly this many tokens, trimmed at a clean paragraph or sentence boundary. Use it when you have a tight context budget.

Details

From the project README

Lyrenth MCP server

lyrenth-mcp MCP server

Listed on mcpservers.org

M8ven Live Monitored

Read the web through Lyrenth's index from any MCP client.

Exposes three tools:

  • read_url turns a public web page into a clean AIDocument: stable Markdown plus title, description, and structure, with the navigation and boilerplate stripped. Your agent reads cleaned, low-token content instead of raw HTML, and every result shows how many tokens it saved vs the raw page.
  • read_urls does the same for up to 20 URLs in one batch call.
  • check_usage reports your plan tier and credit usage.

Reads resolve through Lyrenth's cross-caller cache, and for verified domains they return the publisher's canonical version.

Every tool declares all four MCP tool annotations (read-only, non-destructive, idempotent, and open or closed world) as explicit booleans, and the HTTP transport ships with a 14-test suite covering its security posture.

Hosted, no install

If your MCP client supports remote HTTP servers with a custom header (Claude and Cursor remote connectors do), there is nothing to run:

  • URL: https://api.lyrenth.com/mcp
  • Header: Authorization: Bearer aiwk_your_key_here

Same three tools, same key. The npx path below is for clients that speak MCP over stdio, and for anyone who prefers a local process.

Setup

  1. Get a free API key at https://lyrenth.com/signup (2,000 reads/month, no card).
  2. Add the server to your MCP client.
Claude Desktop (one click)

Download lyrenth-mcp.mcpb from the latest release and open it. Claude Desktop installs the server and asks for your API key; there is no config file to edit. The bundle carries the same code as the npm package.

To build it yourself: ./scripts/build-mcpb.sh.

Claude Desktop / Cursor (manual config)

Add to your MCP config (Claude Desktop: claude_desktop_config.json):

{
  "mcpServers": {
    "lyrenth": {
      "command": "npx",
      "args": ["-y", "lyrenth-mcp"],
      "env": { "LYRENTH_API_KEY": "aiwk_your_key_here" }
    }
  }
}
Claude Code
claude mcp add lyrenth -e LYRENTH_API_KEY=aiwk_your_key_here -- npx -y lyrenth-mcp

Then ask your assistant to read a page, for example: "Read https://example.com/article and summarize it." It will call read_url and get the cleaned AIDocument back.

Tools

ToolArgumentsReturns
read_urlurl (string, required), fresh (boolean, optional), max_tokens (integer, optional)The page as a clean AIDocument: a short provenance header (token count + how much smaller than raw HTML) plus the Markdown body. fresh: true forces a fresh fetch instead of the cached copy; max_tokens caps the body to your context budget, trimmed at a clean paragraph or sentence boundary.
read_urlsurls (array of 1-20 strings, required), fresh (boolean, optional), max_tokens (integer, optional)Up to 20 pages in one call, each as a clean AIDocument, with per-URL error isolation (a failed URL is reported and doesn't block the others). Billed one credit per successfully-read URL.
check_usagenoneYour plan tier, credits used against your monthly limit, credits remaining, and the reset date.

Configuration

Env varRequiredDefaultNotes
LYRENTH_API_KEYyesnoneFree key at https://lyrenth.com/signup
LYRENTH_API_URLnohttps://api.lyrenth.comOverride for staging or self-host

Why read through Lyrenth

  • Cleaner, cheaper. One stable AIDocument shape per URL; far fewer tokens than raw HTML to a model.
  • Cached across callers. The same URL fetched by many agents collapses to a minimal number of origin fetches, so it is fast and origin-friendly.
  • Canonical when verified. When a site's owner has verified with Lyrenth, you get the version they authored, kept fresh by their change signal.

Privacy

The server sends exactly two things to Lyrenth's API (api.lyrenth.com): the URLs you ask it to read, and your API key to authenticate and meter the call. Nothing else leaves your machine: no page content you hold locally, no conversation context, no telemetry. How Lyrenth handles fetched pages and account data is covered by the privacy policy: https://www.lyrenth.com/privacy.

License

MIT. See LICENSE.

Local build

npm install
npm run build
LYRENTH_API_KEY=aiwk_... node dist/index.js   # speaks MCP over stdio

Part of the Lyrenth project. The AIDocument format is an open contract; see https://lyrenth.com/llms-full.txt.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.