Markdown to HTML API vs UI Beats
A side-by-side look at the Markdown to HTML API and UI Beats MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Markdown to HTML API for developer tools work over a hosted endpoint; choose UI Beats for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Markdown to HTML API when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You want tools like
text_convert_markdown_to_html, markdown, wrapInDocument.
Choose UI Beats when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 234 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Markdown to HTML API | View UI Beats |
Tools & capabilities
Markdown to HTML API tools 3
text_convert_markdown_to_htmlConvert markdown text to HTMLmarkdownMarkdown text to convertwrapInDocumentWrap output in full HTML document (default: false)
UI Beats tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Markdown to HTML API
{
"mcpServers": {
"markdown-to-html-api": {
"url": "https://markdown-to-html.api.klymax402.com/mcp"
}
}
}
UI Beats
{
"mcpServers": {
"ui-beats": {
"command": "npx",
"args": [
"-y",
"shadcn@latest"
]
}
}
}
Frequently asked questions
Markdown to HTML API is categorized under Developer Tools and uses a remote HTTP/SSE transport. UI Beats belongs to Developer Tools and uses a local stdio subprocess. Pick Markdown to HTML API for developer tools work and UI Beats for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Markdown to HTML API is listed as a paid service. Auth: other. UI Beats has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add markdown-to-html-api and ui-beats as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markdown to HTML API has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. UI Beats has 49/100 (Fair) with 0 views, 0 installs and 234 GitHub stars.