Mercury MCP Server

Mercury Parser transforms web pages into clean text. Publishers and programmers use it to make the web make sense, and readers use it to read any web

Local serverstdio

What is the Mercury MCP server?

Mercury Parser transforms web pages into clean text. Publishers and programmers use it to make the web make sense, and readers use it to read any web article comfortably. Exposed over MCP by the mercury mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Mercury Parser extracts the bits that humans care about from any URL you give it. That includes article content, titles, authors, published dates, excerpts, lead images, and more.

Its toolset

Everything the assistant can do here goes through one of these:

  • Installation — The Installation tool exposed by this server
  • Usage — // NOTE: When used in the browser, you can omit the URL argument // and simply run Parser.parse() to parse the current page
  • Previewing — You can run a local server to test out your changes with the following command. The site will be available at http://localhost:3000

Adding it to your client

@jocmp/mercury-parser on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mercury's toolset — Installation, Usage, Previewing — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mercury mcp server does with a few real requests.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.
Usage// NOTE: When used in the browser, you can omit the URL argument // and simply run Parser.parse() to parse the current page.
PreviewingYou can run a local server to test out your changes with the following command. The site will be available at <http://localhost:3000>

How to install the Mercury MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Mercury to Installation.
  • Use Mercury to Usage.
  • Use Mercury to Previewing.

Frequently asked questions

It connects Mercury to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Installation, Usage, Previewing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mercury directly.