MCP.so
ログイン

Mercury Parser MCP Server

@koichikawamura

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

koichikawamura

投稿者

Koichi Kawamura

Mercury Parser MCP Server について

Mercury Parser MCP

Mercury Parser MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mercury-parser": {
      "command": "npx",
      "args": [
        "@koichikawamura/mercury-parser",
        "mercury-parser-mcp"
      ]
    }
  }
}

Mercury Parser MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Mercury Parser?

Mercury Parser fetches web pages with a headless Chromium (via Playwright) to capture JavaScript-rendered content, then uses the Mercury Parser to extract the article and returns it as Markdown. It follows pagination links automatically. Designed for AI agents like Claude to read and summarize articles.

How to use Mercury Parser?

The server exposes a single tool called extract which takes a URL and optional proxy argument. It can be used via Claude Desktop (local stdio) by adding the configuration to claude_desktop_config.json, or run over Streamable HTTP for remote access. It can also be tested via CLI with node extractContent.js <url> [proxy].

Key features of Mercury Parser

  • Automatically fetches web pages with headless Chromium for JS-rendered content
  • Extracts articles as Markdown including title, author, date, summary, and content
  • Follows pagination links automatically to capture full articles
  • Falls back to direct fetch when Playwright fails, ensuring partial content
  • Supports per-call proxy override and default proxy via environment variable
  • Available over stdio or Streamable HTTP transport

Use cases of Mercury Parser

  • An AI agent reading and summarizing a JavaScript-heavy news article
  • Extracting clean article content from a multi-page blog post with pagination
  • Archiving articles as Markdown for offline reference or translation
  • Integrating a content extraction pipeline with Claude or other MCP clients

よくある質問

1

What are the runtime requirements?

Node.js 18+ and Playwright Chromium (auto-installed on first launch if missing).

2

Does it support proxy for extraction?

Yes. A default proxy can be set via the `MERCURY_PROXY` environment variable, and each call can override it with the `proxy` tool argument.

3

What happens if the headless browser fails?

On Playwright failure (e.g., HTTP/2 protocol errors, navigation timeouts), it falls back to a direct fetch using Mercury Parser so partial content is still returned.

4

What transports are available?

The server supports both `stdio` (default for local use) and `http` (Streamable HTTP) by setting the `MCP_TRANSPORT` environment variable to `http`.

5

Where is the article data stored?

The server only extracts and returns the article content in the response; it does not persist data locally or on a server.

コメント

「その他」の他のコンテンツ