markdown-to-html

markdown-to-html is an MCP server that converts Markdown content into HTML. It exposes a tooling capability named markdown_to_html which accepts markdown content (mdContent) as a required parameter and returns the corresponding HTML output. You can integrate this server into workflows or chat/assistant prompts where Markdown-to-HTML conversion is needed, enabling downstream tooling to render rich HTML from Markdown input. When running, the server communicates over stdio using the MCP protocol, so you can interact with it through an MCP client or the MCP Inspector during debugging.

To use the tool, send a request that includes the markdown content you want to convert. The tool will process the input and return the HTML string. If you need to extend or chain processing (for example, render code blocks with syntax highlighting or adjust headings), you can combine markdown_to_html with other MCP tools in your workflow.

Prerequisites:

• Node.js and npm installed on your system
• Basic familiarity with running Node scripts and configuring MCP servers

1. Install dependencies

   • Run in the project directory: npm install

2. Build the server

   • Compile or bundle the server code (as per project setup): npm run build

3. Configure for Claude or MCP clients

   • Prepare an MCP config (e.g., Claude desktop config) with the following entry:

     { "mcpServers": { "markdown-to-html": { "command": "node", "args": [ "/path/to/markdown-to-html/build/index.js" ] } } }

   • Place the config at the appropriate path: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

4. Run and test

   • Start the server (if not started by your environment) and use an MCP client to send a request with mdContent to obtain HTML.

Optional: for debugging, you can use the MCP Inspector as described in the project documentation.

Notes and tips:

• The server expects a parameter named mdContent containing your Markdown, and returns the converted HTML.
• MCP runs over stdio; ensure your client properly formats requests and reads responses according to the MCP protocol.
• If your Markdown includes custom extensions or requires specific rendering options (e.g., code block highlighting), consider post-processing the HTML or extending the server accordingly.
• When configuring in Claude Desktop, ensure the path to build/index.js is correct and that the built artifact exists.
• Use the MCP Inspector during development to inspect requests/responses and the available tooling endpoints.