check_consistency
Audit document for stale cross-section references and dependency violations
LABSCO SUMMARY
Editing a page costs a fraction of rewriting one.
The reason to use this over asking a model for raw HTML is the edit path: a line-range replacement sends only the replacement, and reading a page back in text mode returns roughly a thousandth-scale summary of a 106KB file rather than the file. That is what makes a build-inspect-refine loop affordable enough to run several times.
What it is
An MCP server that builds and edits HTML files, so an agent's output arrives as a page you can scan and share rather than a wall of markdown. Pages are assembled from named components against a template shell, and every later change is surgical: patch by CSS selector, set an attribute, replace a line range, or swap one rendered section. It works on strings and an AST — no headless browser is involved.
What you get
- A page assembled from structured components and a template shell, previewed before it is written to disk —
render_page,preview_html - The available templates and components listed, with their variables, defaults and props —
list_templates,list_components,get_template_schema,get_component_schema - Element content replaced by CSS selector and attributes set the same way —
patch_html,set_attribute - A line range replaced outright, which is the cheapest edit because only the new content is sent —
edit_html_range - Rendered sections listed, replaced and inserted by index, since pages built this way carry their section boundaries —
list_sections,edit_section,insert_section - Existing HTML read back in several modes, including a plain-text mode with offsets for token-minimal inspection —
read_html - Raw HTML written straight to a file, and an existing file beautified —
write_raw_html,write_html_file,format_html - An entity edit propagated through the dependency graph to every section that references it, and the document audited for stale cross-references —
propagate_edit,check_consistency - Your own template registered at run time and usable immediately —
register_template
Requirements
No account and no key; files are written to your own disk. Node.js 20 or newer, launched with npx -y @aimino/fast-html-mcp-server over stdio; the MCP registry entry for the same server points at @aimino/opentalk2html-notmd 0.1.2. 22 components and the template shells ship with the package, so there is nothing to fetch at render time. Output passes through DOMPurify and files are written tmp-then-rename, so an interrupted write does not corrupt the page. Licensed under the GNU General Public License v3.0.
Setup effort
One command — npx -y @aimino/fast-html-mcp-server
USE CASES
01
Getting an analysis back as something you can send to someone
Assemble a report page from the data-table, stats-grid and callout components against a report template, preview it, then write it out.
02
Fixing one number without rebuilding the page
Read the file to locate the element, then patch that element by selector — or replace the line range outright when the target is a large container.
03
Keeping a figure consistent everywhere it appears
Change the entity once and propagate the edit through the dependency graph, then audit the document for references that are still pointing at the old value.
04
Restructuring a page after the fact
List the rendered sections, replace one with a different component, and insert a new section at the index where it belongs — existing sections shift forward rather than being overwritten.
05
Making the output match your own house style
Register a custom template shell at run time and render against it immediately, instead of post-processing every page the built-in shells produce.
19 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
edit_html_range
Replace a range of lines in an HTML file with new content (most token-efficient edit — send only the changed lines)
edit_section
Replace a rendered section in an HTML file with a new component. Pages rendered with render_page embed section markers. Use list_sections to discover available indices. Provide component+props to re-render, or html for raw replacement.
format_html
Format/beautify an existing HTML file
get_component_schema
Get component schema with available props
get_template_schema
Get template metadata including available variables with defaults
insert_section
Insert a new component section at a specific index, pushing existing sections forward. Uses the same section marker system as render_page. Auto-renumbers all subsequent sections.
list_components
List available interactive components (optionally filter by category)
list_sections
List all component sections in an HTML file that was built with render_page. Returns section indices, component types, and sizes.
list_templates
List available template shells (optionally filter by category)
patch_html
Patch HTML element(s) by CSS selector
preview_html
Preview rendered HTML string without writing
propagate_edit
Propagate an entity edit through the dependency graph, updating all transitively affected sections
read_html
Read/analyze existing HTML file. Use mode='text' for token-efficient plain text extraction with offset/limit progressive reading.
register_template
Register a custom template at runtime for immediate use with render_page/preview_html
render_page
Assemble page from structured components
set_attribute
Set attribute on element(s) by CSS selector
write_html_file
Write content as formatted HTML file
write_raw_html
Write raw HTML content directly to file
BEFORE YOU INSTALL
What to know first
Tools you get
19 tools when we connected. The documented email tools render_email and html_to_email are not available. list_sections, edit_section, insert_section and write_html_file are available but undocumented.
Requires
Node.js 20+
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 19 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @aimino/fast-html-mcp-serverMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"open-talk-2-html-not-md": {
"command": "npx",
"args": [
"-y",
"@aimino/fast-html-mcp-server"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"open-talk-2-html-not-md": {
"command": "npx",
"args": [
"-y",
"@aimino/fast-html-mcp-server"
]
}
}
}
