Lyrenth MCP

Lyrenth MCP server

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 site'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 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

Configuration

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.
• Fresh when verified. When a site's owner has verified with Lyrenth, a page they change is fetched again at the front of our crawl queue, so you read the new version sooner.

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.