webstractor

How to Fetch Web Pages in LobeChat with Webstractor MCP in 2026

Pasting a link into chat does not guarantee the model reads its current content. Webstractor provides an explicit read-only extraction tool, while LobeChat Desktop provides the assistant and model interface. The result is best for known public pages: documentation, articles, product pages, social posts, and other supported URLs.

Give a LobeChat assistant a public-page reader.

Import the Webstractor bridge as a custom MCP plugin in LobeChat Desktop, enable it for the active assistant, and pass an exact public URL to extract_public_url. Ask for Markdown and a source-linked summary.

MCP configuration
{
  "mcpServers": {
    "webstractor": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://webstractor.com/mcp"]
    }
  }
}

What you need

  • LobeChat Desktop
  • Node.js and npx
  • A public URL and a tool-capable model

Connect Webstractor to LobeChat

01

Open LobeChat’s JSON importer

Navigate to Settings → Default Assistant → Plugin Settings → Custom Plugins → Quick Import JSON Configuration.

02

Install the Webstractor bridge

Import this entry and enable it for the default assistant. The `-y` option lets npx install the adapter without a confirmation prompt.

Custom plugin JSON
{
  "mcpServers": {
    "webstractor": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://webstractor.com/mcp"]
    }
  }
}
03

Test a known public page

State that the assistant must use the extraction tool. Ask it to preserve the page URL and distinguish source facts from its summary.

Validation prompt
# Paste into LobeChat
Use webstractor extract_public_url to read https://lobehub.com/docs as Markdown with focus "self-hosting". Summarize the relevant options and include the source URL.

Tell the assistant what to read and why

Include the exact URL, preferred output, and a concise focus topic. “Read this page” is workable, but “extract the installation section as Markdown and make a checklist” produces a result that is easier to verify.

For comparisons, perform one extraction per URL and ask LobeChat to keep separate source headings. This avoids mixing facts from pages that may have different publication dates.

  • Pass the canonical page URL
  • Use Markdown for a model-readable result
  • Request attribution in the final answer

Diagnose the adapter before the page

If no Webstractor tools appear, reload the plugin configuration and confirm that Node.js can run npx. If the tools appear but one URL fails, try a stable public page to determine whether the source itself is restricted.

Image-only PDFs do not contain extractable text without OCR. For normal PDFs, use a public PDF URL; uploaded local files belong to the API upload workflow rather than this URL-only MCP tool.

01

What you can extract

  • Readable Markdown without surrounding page controls
  • Optional focused extraction
  • Normalized JSON entities for structured tasks
  • Source-linked metadata for attribution
02

Where normalized data helps

  • Summarize a linked report
  • Read current documentation before answering
  • Compare two public product or article pages
  • Turn a long page into a focused brief

Public data only

  • Only the supplied public URL is read.
  • The plugin does not access private sessions or browser cookies.
  • This custom-plugin process applies to LobeChat Desktop.

webstractor.com does not bypass CAPTCHAs, login walls, paywalls, access controls, or regional restrictions. Review the source’s terms and applicable law before collecting or reusing data.

LobeChat and Webstractor FAQ

Will LobeChat automatically open every pasted URL?

Not reliably. Ask it explicitly to use webstractor extract_public_url for the link.

Can the tool read pages behind a login?

No. It does not receive browser sessions, cookies, or credentials.

Can it extract only one topic?

Yes. Pass a short focus such as pricing, installation, or limitations.

Turn a public URL into useful context.

Add a page reader Read the MCP extraction guide