A
licenseA
qualityB
maintenanceMCP server for markdown files — search, extract sections, list headings, find code blocks across docs.
6
77 npm
8
MIT
io.github.tidybytetools/md-chunk-lite
OfficialRelated Servers
Alternatives to io.github.tidybytetools/md-chunk-lite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to parse markdown documents into structured AST nodes—including headings, lists, tables, callouts, and code blocks—and serialize modified AST back into clean canonical markdown via MCP tools.7MIT
- AlicenseNot gradedqualityDmaintenanceSplits Markdown documents into hierarchical sections with parent-child and sibling relationships, enabling structured document access for AI assistants.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools to scan and navigate markdown repositories, offering graph-based overview, document reading, context retrieval, and orphan detection.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for analyzing, linting, formatting, and generating Markdown content. It enables users to programmatically manage Markdown files through features like table of contents generation, statistics calculation, and JSON-to-table conversion.27 npm1MIT
- AlicenseCqualityNot gradedmaintenanceProvides semantic editing tools for Markdown files, allowing structured manipulation of document elements through hierarchical paths rather than raw text operations. Supports navigation, search, content replacement, element insertion/deletion, undo functionality, and YAML frontmatter management.152MIT
TDQS
A4.5/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct operation: chunking the whole document, listing headings, extracting one section, and persisting chunks to a file. Descriptions include explicit 'do not use it for X, use Y' guidance that makes the boundaries unambiguous.
Naming Consistency4/5
All four names follow a verb_noun shape, but the noun varies: two end in _markdown (chunk_markdown, outline_markdown) while get_section and save_chunks_jsonl drop the markdown qualifier and name a sub-resource instead. Still predictable and readable, just not a single uniform pattern.
Tool Count5/5
Four tools is exactly right for a focused Markdown chunking utility, with no redundant or filler entries. Each tool covers a clear step in the read-outline, inspect-section, chunk, persist workflow.
Completeness4/5
The core lifecycle (map, extract, chunk, export) is fully covered with no dead ends for the stated purpose. Minor gaps exist, such as no token-based chunk sizing (explicitly noted as character-based) and no batch/multi-file operation, but agents can work around both.
Maintenance
ActivityMaintained
ResponsivenessNo issues