How do I install the Using The MCP Server skill?

Run npx skillmds@latest add kreuzberg-dev/using-the-mcp-server-11 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Using The MCP Server safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using The MCP Server?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using The MCP Server free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using The MCP Server?

kreuzberg-dev (@kreuzberg-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using The MCP Server by kreuzberg-dev

Name: Using The MCP Server
Rating: 4.2 (5 reviews)
Author: kreuzberg-dev

Using The MCP Server

Use when converting HTML to Markdown or extracting metadata and tables through the html-to-markdown MCP server's tools, rather than shelling out to the CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.

kreuzberg-dev Updated Sep 22, 2026

File contents

Using the MCP Server

The html-to-markdown MCP server exposes the converter's conversion and metadata-extraction capabilities as MCP tools, so an MCP-compatible client (Claude Code, Claude Desktop) can convert HTML and pull structured metadata directly, with no CLI invocation or glue code.

How it runs in this plugin

The plugin auto-registers the server. Its command is the bundled launcher scripts/mcp-launch.sh, which execs html-to-markdown mcp. On first run the launcher resolves an html-to-markdown binary: it reuses one already on PATH or cached in the plugin's bin/, then tries npx/uvx, then Homebrew, then downloads a prebuilt from the tool's latest GitHub release. Override the channel with HTML_TO_MARKDOWN_LAUNCHER=auto|npx|uvx|brew|download.

The mcp subcommand ships in a recent release of the tool. If an older html-to-markdown is already on PATH, it may not expose mcp yet — upgrade the binary (brew upgrade, re-download, or rebuild) to pick it up.

To run it manually:

html-to-markdown mcp        # for Claude Code / Claude Desktop (stdio)

The tools

convert_html — convert an HTML string to Markdown, Djot, or plain text. Takes html (the HTML string), an optional config object mirroring ConversionOptions, and an optional json flag. With json: true it returns the full ConversionResult (content, tables, metadata, document structure, inline images, warnings) instead of the bare converted text.
extract_metadata — pull structured metadata (document info, Open Graph / Twitter / JSON-LD / Microdata, headers, links, images) from an HTML string. Takes only html.

Both tools accept an HTML string — the MCP server does not fetch URLs or read files (that is CLI-only). The exact argument schemas come from the running server; ask the client to list tools to see the live surface.

When to prefer MCP over the CLI or SDK

Prefer MCP inside an agent session: the agent calls the converter directly as a tool, with no shell-out and no process management.
Prefer the CLI for one-shot conversions and shell pipelines (… | jq).
Prefer the SDK when embedding conversion in application code.

---name: using-the-mcp-server-11description: Use when converting HTML to Markdown or extracting metadata and tables through the html-to-markdown MCP server's tools, rather than shelling out to the CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.---# Using the MCP ServerThe `html-to-markdown` MCP server exposes the converter's conversion andmetadata-extraction capabilities as MCP tools, so an MCP-compatible client (ClaudeCode, Claude Desktop) can convert HTML and pull structured metadata directly,with no CLI invocation or glue code.## How it runs in this pluginThe plugin auto-registers the server. Its command is the bundled launcher`scripts/mcp-launch.sh`, which execs `html-to-markdown mcp`. On first run thelauncher resolves an `html-to-markdown` binary: it reuses one already on `PATH`or cached in the plugin's `bin/`, then tries `npx`/`uvx`, then Homebrew, thendownloads a prebuilt from the tool's latest GitHub release. Override the channelwith `HTML_TO_MARKDOWN_LAUNCHER=auto|npx|uvx|brew|download`.The `mcp` subcommand ships in a recent release of the tool. If an older`html-to-markdown` is already on `PATH`, it may not expose `mcp` yet — upgradethe binary (`brew upgrade`, re-download, or rebuild) to pick it up.To run it manually:```bashhtml-to-markdown mcp # for Claude Code / Claude Desktop (stdio)```## The tools- **convert_html** — convert an HTML string to Markdown, Djot, or plain text. Takes `html` (the HTML string), an optional `config` object mirroring `ConversionOptions`, and an optional `json` flag. With `json: true` it returns the full `ConversionResult` (content, tables, metadata, document structure, inline images, warnings) instead of the bare converted text.- **extract_metadata** — pull structured metadata (document info, Open Graph / Twitter / JSON-LD / Microdata, headers, links, images) from an HTML string. Takes only `html`.Both tools accept an HTML **string** — the MCP server does not fetch URLs or readfiles (that is CLI-only). The exact argument schemas come from the runningserver; ask the client to list tools to see the live surface.## When to prefer MCP over the CLI or SDK- **Prefer MCP** inside an agent session: the agent calls the converter directly as a tool, with no shell-out and no process management.- **Prefer the CLI** for one-shot conversions and shell pipelines (`… | jq`).- **Prefer the SDK** when embedding conversion in application code.

Frequently asked questions