fast-html-mcp
Related Servers
Alternatives to fast-html-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI coding agents to read and write to a local-first HTML/CSS design canvas, bridging visual design and code generation.MIT
- FlicenseAqualityCmaintenanceAn MCP server implementing a 7-stage agentic frontend workflow—from design audit to PR review—including AI-driven component generation, browser validation, E2E testing, and CI self-healing.48-
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI agents publish markdown/HTML to a browser viewer with session management, revision diffs, and live updates via a single tool call.2MIT
- FlicenseAqualityDmaintenanceMCP server that gives AI coding agents the ability to design UIs through Google Stitch. It generates production-ready HTML and screenshots from natural language prompts.9-

CustomJS MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceA remote MCP server that enables AI agents to host HTML pages, generate PDFs, capture screenshots, scrape sites, and run sandboxed code using a CustomJS API key.MIT- FlicenseNot gradedqualityCmaintenanceA self-extending MCP server that enables AI agents to browse the web, execute shell and Node snippets, automate browser workflows, access files and git, communicate with other agents, and use dozens of domain-specific calculation and research tools.-
TDQS
Scored across 19 tools
There is some overlap between tools like patch_html and set_attribute (both modify elements via CSS selectors), and write_raw_html vs write_html_file both write HTML but with unclear distinction. However, most tools have clearly defined purposes targeting different aspects (sections, templates, components), so the ambiguity is limited.
All tool names follow a consistent lower_snake_case verb_noun pattern (e.g., list_components, render_page, check_consistency). Verbs are clear and nouns align with the object acted upon, making the naming predictable and readable.
With 19 tools, the set is on the heavy side (16-25). While each tool has a specific role, the number feels slightly excessive for HTML manipulation, especially given the overlapping edit/write tools that could potentially be consolidated.
The tool surface covers creation, reading, editing, rendering, and template/component management comprehensively. The main gap is the lack of delete/removal operations (e.g., delete_element or remove_section), but core workflows are well-supported.