markdown-to-html
# markdown-to-html MCP Server
A Model Context Protocol server that Convert Markdown to HTML.
## Features
### Tools
- `markdown_to_html` - Convert Markdown to HTML
- Takes mdContent as required parameters
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
## Installation
To use with Claude Desktop, add the server config:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"markdown-to-html": {
"command": "node",
"args": [
"/path/to/markdown-to-html/build/index.js"
]
}
}
}
```
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as converting Markdown to HTML, making it impossible for an agent to misselect among multiple options.
The single tool name 'markdown_to_html' uses a consistent snake_case pattern and follows a clear verb_noun structure (convert_markdown_to_html implied). Since there is only one tool, there is no inconsistency to evaluate, and the naming is straightforward and appropriate.
A single tool for a server named 'markdown-to-html' feels thin and under-scoped. While the tool directly addresses the core function, typical MCP servers in this domain might include additional tools for validation, configuration, or handling different Markdown flavors, making this count borderline minimal for practical use.
The tool covers the basic conversion from Markdown to HTML, which aligns with the server's stated purpose. However, there are notable gaps, such as lack of tools for HTML to Markdown conversion, validation, or customization options, which could limit agent functionality in more complex scenarios.