LionScraper MCP + CLI + HTTP API (Node)

LionScraper MCP + CLI + API service

简体中文

• Website: lionscraper.com
• npm: package lionscraper

What is this?

LionScraper is a browser extension that can collect lists, articles, links, images, and more from web pages. This npm package provides the companion bridge to that extension in three ways:

• MCP (lionscraper-mcp): connect your AI app (e.g. Cursor) so the model can call scraping tools in chat.
• CLI (lionscraper): run daemon, scrape, and ping from a terminal over the same local HTTP/WebSocket port as the extension.
• HTTP API: call the same tools over loopback JSON HTTP (/v1/...) when the daemon is running—useful for scripts, services, or any HTTP client without MCP or the CLI front-end.

The real scraping logic runs in the extension; this package connects and forwards.

Before you start

1. Browser: Chrome or Edge (follow what the extension actually supports).
2. LionScraper extension: Install and enable it from your browser’s store (the listing title may vary by storefront).
   • Chrome: Chrome Web Store — LionScraper
   • Microsoft Edge: Edge Add-ons — LionScraper
3. Node.js: Version 18 or newer on your machine. If you do not have it yet, download an installer from the Node.js website and follow the prompts.
4. For MCP: an AI app that supports MCP (e.g. Cursor, Trae).
5. For the HTTP API: same browser, extension, and daemon as the CLI; use curl, fetch, or any HTTP client against http://127.0.0.1:$PORT (see HTTP API (local REST) below).

Install (npm)

This package is published on npm as lionscraper.

npm install -g lionscraper

You get two commands; together they support three integration styles (MCP, CLI, HTTP API):

Without a global install, MCP can use npx; see JSON examples under Add MCP in your AI app.

MCP (AI applications)

Add MCP in your AI app

Examples assume a global lionscraper install (UIs differ). In MCP JSON, every env value is a string.

Minimal config (omit env for built-in defaults; PORT defaults to 13808 and must match the extension bridge port):

{  "mcpServers": {    "lionscraper": {      "command": "lionscraper-mcp"    }  }}

Full env example (drop keys you do not need; empty strings behave like “unset” for most of these):

{  "mcpServers": {    "lionscraper": {      "command": "lionscraper-mcp",      "env": {        "PORT": "13808",        "TIMEOUT": "120000",        "LANG": "en-US",        "TOKEN": "",        "DAEMON": ""      }    }  }}

npx (no global install) — the first run may download the package. command is npx; args are ["-y", "lionscraper", "lionscraper-mcp"] (npm package name lionscraper, then binary lionscraper-mcp).

Minimal config (npx):

{  "mcpServers": {    "lionscraper": {      "command": "npx",      "args": ["-y", "lionscraper", "lionscraper-mcp"]    }  }}

Full env example (npx):

{  "mcpServers": {    "lionscraper": {      "command": "npx",      "args": ["-y", "lionscraper", "lionscraper-mcp"],      "env": {        "PORT": "13808",        "TIMEOUT": "120000",        "LANG": "en-US",        "TOKEN": "",        "DAEMON": ""      }    }  }}

Pin a version by using e.g. [email protected] instead of lionscraper in args.

• PORT: HTTP + WebSocket listen port; default 13808; must match the extension bridge port.
• TIMEOUT: Milliseconds to wait for a previous instance to release the port before forcing takeover; default 120000; 0 means force quickly.
• LANG: Tool descriptions and stderr log language (en-US, zh-CN, or POSIX forms like en_US.UTF-8).
• TOKEN: Bearer token shared with the daemon; empty means no Authorization header.
• DAEMON: Only 0 disables auto-spawning lionscraper daemon from thin MCP; empty or other values match omitting the key (auto-start allowed).

Restart MCP or the app so the config applies.

Match the port in the browser extension

1. Open LionScraper settings / options.
2. Set bridge port to the same value as PORT (e.g. 13808).
3. If needed, use Reconnect in the extension, or reload the extension / restart the browser.

Day-to-day use (MCP)

1. Keep the extension enabled and target pages open as required.
2. Ask in natural language, e.g. “Check if LionScraper is connected” or “Scrape lists / article / emails / phones / links / images from this page.”
3. If you see not connected or timeout, retry a connection check and confirm PORT matches.

MCP tools (summary)

The server registers tools that mirror extension capabilities. Names and shapes are what your MCP client shows to the model.

Parameters: A full JSON schema for every field belongs in the tool definitions your client displays and in release-accurate docs; duplicating it here goes stale quickly. Use the tool list / descriptions in the AI app when calling MCP.

MCP Resources / Prompts

The thin MCP process (lionscraper-mcp) exposes Resources and Prompts in addition to Tools:

• Resources: static Markdown at stable URIs, e.g. lionscraper://guide/connection (PORT alignment, ping troubleshooting), lionscraper://guide/when-to-use-tools (prefer LionScraper over WebFetch/curl/wget by scenario), lionscraper://guide/cli (terminal CLI), lionscraper://reference/tools, lionscraper://reference/common-params. Clients list/read them into context; they are served inside the stdio process and do not require the daemon HTTP path (works even if the extension is offline). For the loopback HTTP control plane (/v1/...), see HTTP API (local REST) below (not an MCP resource URI).
• Prompts: workflow templates (e.g. ping-then-scrape, multi-URL, scrape_article, prefer_lionscraper_scraping, extension troubleshooting). Clients list/get prompts; UI varies by host (Cursor, Trae, …).

Copy follows LANG (e.g. zh-CN), same as tool metadata.

CLI (terminal)

The lionscraper binary is the terminal front-end to the same stack as MCP: lionscraper daemon listens on PORT (default 13808) for HTTP (used by the CLI and by the thin lionscraper-mcp process) and WebSocket (used by the extension). Set PORT (and optional TOKEN) to match the extension bridge port and any MCP config. Use the CLI for scripts, CI, or quick one-off runs without opening an AI chat.

The CLI talks to the daemon HTTP API on http://127.0.0.1:$PORT (default port 13808, same as the extension). If you do not pass --api-url, a local daemon is auto-started when possible when you run scrape or ping.

Common commands:

lionscraper --helplionscraper daemon              # keep running; HTTP + WebSocket on PORTlionscraper stop                # stop daemon on configured PORTlionscraper pinglionscraper scrape -u https://www.example.comlionscraper scrape --method article -u https://www.example.com# Shorthand: lionscraper -u https://www.example.com   → same as scrape

--method selects which tool the daemon runs (default scrape): scrape, article, emails, phones, urls, images. Repeat -u / --url to pass several URLs in one run.

Set PORT (and optional TOKEN) in the environment so the CLI matches the extension and MCP. Use --api-url http://127.0.0.1:PORT if the daemon is not on the default base URL. Run lionscraper --help for every flag the binary accepts.

Scrape: parameters and richer examples

Below flags are forwarded to the extension (except --bridge-timeout-ms, which only caps how long the CLI waits on the bridge). Actual behavior still depends on the extension version.

Output and connection

Timing and load

Lazy-loaded / infinite scroll (maps to waitForScroll in the tool payload)

Locale

Extra payload

Method-specific filters (examples; see --help for the full set)

• Emails (--method emails): --email-domain, --email-keyword, --email-limit
• Phones (--method phones): --phone-type, --phone-area-code, --phone-keyword, --phone-limit
• URLs (--method urls): --url-domain, --url-keyword, --url-pattern, --url-limit
• Images (--method images): --img-min-width, --img-min-height, --img-format, --img-keyword, --img-limit

Optional browser automation hints (when the extension supports them): --auto-launch-browser, --no-auto-launch-browser, --post-launch-wait-ms.

Example A — List / table scrape with pagination, delays, and scroll assist

lionscraper scrape \  -u https://www.example.com/items \  --max-pages 5 \  --delay 800 \  --timeout-ms 90000 \  --bridge-timeout-ms 180000 \  --wait-scroll-speed 400 \  --wait-scroll-interval 350 \  --lang zh-CN \  --format pretty \  -o items.json

• --max-pages: stop after at most five “pages” of list accumulation for this job.
• --delay: give the page extra time after load before extraction.
• --timeout-ms / --bridge-timeout-ms: extension vs. CLI-side waits; raise both for slow sites or heavy pages.
• --wait-scroll-*: gentle scrolling so lazy-loaded rows can appear before scraping.
• -o / --format pretty: save a human-readable JSON file for inspection.

Example B — Article body with optional HTML snapshot

lionscraper scrape --method article \  -u https://www.example.com/blog/post-1 \  --include-html true \  --timeout-ms 120000 \  --format json

• --method article: maps to the scrape_article tool (Markdown-style body + metadata when the extension provides it).
• --include-html true: requests additional HTML in the result meta where supported (larger payload).

Example C — Emails and URLs with filters, multiple pages

lionscraper scrape --method emails \  -u https://www.example.com/contact \  --email-domain example.com \  --email-keyword support \  --email-limit 30 \  --format pretty
lionscraper scrape --method urls \  -u https://www.example.com \  -u https://www.example.com/docs \  --url-domain example.com \  --url-limit 200 \  --scrape-interval 500

• Email flags: narrow to addresses in a domain, matching a keyword, and cap the count.
• Two -u values: two URLs processed in one invocation; --scrape-interval spaces out task starts.

Example D — Images with size / format filters

lionscraper scrape --method images \  -u https://www.example.com/gallery \  --img-min-width 240 \  --img-min-height 240 \  --img-format webp \  --img-limit 40 \  -o gallery-images.json

• Filters out small thumbnails and non-WebP assets when the extension honors these fields; --img-limit caps how many entries are returned.

HTTP API (local REST)

Base URL: http://127.0.0.1:$PORT (default 13808). Binds 127.0.0.1 only. The extension must be connected on that port and a daemon must be listening (same process model as the rest of this package).

Anything else → 404 { "ok": false, "error": { "code": "NOT_FOUND", "message": "Not found" } }.

Auth: If env TOKEN is set on the daemon, every request needs Authorization: Bearer <TOKEN>; otherwise omit the header.

POST /v1/tools/call

• Headers: Content-Type: application/json. For streaming, also Accept: application/x-ndjson.
• Body:

{ "name": "<tool>", "arguments": { }, "progressToken": "<optional>" }

arguments (JSON keys)

ping only: optional lang ("en-US" | "zh-CN"), autoLaunchBrowser (boolean), postLaunchWaitMs (number, 3000–60000).

All scrape-family tools (scrape, scrape_article, scrape_emails, scrape_phones, scrape_urls, scrape_images) share:

Only scrape: optional maxPages (number, ≥ 1).

Optional filter object (only on the matching tool):

Unknown name, bad JSON, or schema violations → 400 { "code": "BAD_REQUEST", ... }. Bad bearer → 401 UNAUTHORIZED. Tool crash → 500 INTERNAL.

200 body: { "content": [ { "type": "text", "text": "..." } ], "isError"?: boolean }.

Examples (PORT=13808)

curl -sS "http://127.0.0.1:13808/v1/health"curl -sS -X POST "http://127.0.0.1:13808/v1/tools/call" \  -H "Content-Type: application/json" \  -d '{"name":"ping","arguments":{}}'curl -sS -X POST "http://127.0.0.1:13808/v1/tools/call" \  -H "Content-Type: application/json" \  -d '{"name":"scrape_article","arguments":{"url":"https://www.example.com","timeoutMs":120000}}'# With TOKEN on the daemon:curl -sS -X POST "http://127.0.0.1:13808/v1/tools/call" \  -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_TOKEN" \  -d '{"name":"ping","arguments":{}}'

FAQ (plain language)

Q: Extension not connected or scraping fails?

• Extension enabled?
• PORT in MCP (or env for CLI) exactly matches the extension bridge port?
• Avoid multiple conflicting MCP/CLI setups on one machine.

Q: Many “tools” visible in the AI app—does that mean the extension is connected?

Not necessarily. Tools only confirm AI → MCP server; the extension must still connect on the same port and register.

Q: CLI says it cannot reach the daemon?

Start lionscraper daemon in another terminal, or fix PORT / --api-url.

Q: I want to drive scraping from my own HTTP client?

Keep the daemon and extension on the same PORT, then POST /v1/tools/call with name and arguments as in HTTP API (local REST). GET /v1/health checks that the listener is LionScraper.

License

MIT (same as the lionscraper npm package).