Mult MCP Server

A versatile MCP-compliant web content fetching tool that supports multiple modes (browser/node), formats (HTML/JSON/Markdown/Text), and intelligent proxy detection, with bilingual interface (English/Chinese). The mult mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

This project implements an MCP-compliant client and server for communication between AI assistants and external tools.

• Implementation based on the official MCP SDK
• Support for Standard Input/Output (Stdio) transport
• Multiple web scraping methods (HTML, JSON, text, Markdown, plain text conversion)
• Intelligent mode switching: automatic switching between standard requests and browser mode
• Content size management: automatically splits large content into manageable chunks to solve AI model context size limitations
• Chunked content retrieval: ability to request specific chunks of large content while maintaining context continuity

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

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

• fetch_html — Get HTML content of a webpage
• fetch_json — Get JSON data
• fetch_txt — Get plain text content
• fetch_markdown — Get Markdown formatted content
• fetch_plaintext — Get plain text content converted from HTML (strips HTML tags)
• Usage — After configuration, restart Claude desktop, and you can use the following tools in your conversation:

Configuration

You will need 3 environment variables: MCP_LANG, HTTP_PROXY, HTTPS_PROXY. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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 mult mcp server does with a few real requests.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mult's toolset — fetch_html, fetch_json, fetch_txt and 3 more — is a fair guide to whether it matches your workflow. It is maintained by lmcc-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mult's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.