html_to_markdown — ToolSnap MCP MCP Tool
html_to_markdown
(html to markdown) is one of 17 tools on the
ToolSnap MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call html_to_markdown from your client
- Claude Code ToolSnap MCP html_to_markdown run in your project directory
- Claude Desktop ToolSnap MCP html_to_markdown ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ToolSnap MCP html_to_markdown ~/.cursor/mcp.json
- VS Code ToolSnap MCP html_to_markdown .vscode/mcp.json
- Zed ToolSnap MCP html_to_markdown ~/.config/zed/settings.json
- Windsurf ToolSnap MCP html_to_markdown ~/.codeium/windsurf/mcp_config.json
- Cline ToolSnap MCP html_to_markdown ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ToolSnap MCP html_to_markdown ~/.gemini/settings.json
- Grok ToolSnap MCP html_to_markdown .mcp.json (in your project root)
- ChatGPT ToolSnap MCP html_to_markdown Settings → Connectors → Advanced → Developer mode
- Claude.ai ToolSnap MCP html_to_markdown Settings → Connectors → Add custom connector
- LangChain ToolSnap MCP html_to_markdown pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http toolsnap-mcp https://mcp.toolsnap.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.