io.github.tidybytetools/md-chunk-lite
OfficialProvides a reusable GitHub Action that runs md-chunk-lite on Markdown files during CI, generates JSONL chunks, reports oversized split sections, can fail the build when sections are split, and can upload the output as an artifact.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.tidybytetools/md-chunk-lite Split guide.md into heading-based chunks and save them to guide.chunks.jsonl"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
md-chunk-lite
Free tool that splits Markdown into chunks by heading. Every chunk knows its heading path and the line numbers it came from. Need PDF, Word or web page files turned into chunks (with page numbers for PDFs), or whole folders? The paid doc2md does that: doc2md on Gumroad
Good for AI search (RAG), embeddings, and docs bots. Plain code, not AI, so the same file always gives the same chunks. Runs on your own computer. MIT license. Python 3.10 or newer, on Windows, Mac and Linux.
Install
pip install md-chunk-liteOr use pipx, which keeps it in its own space:
pipx install md-chunk-liteWant the newest code from GitHub instead?
pip install git+https://github.com/tidybytetools/md-chunk-liteRelated MCP server: mcp-server-markdown
Use it
md-chunk-lite guide.md # writes guide.chunks.jsonl
md-chunk-lite docs/*.md -o all.jsonl # many files into one file
md-chunk-lite guide.md -o - # print the chunks on screen
md-chunk-lite guide.md --max-chars 800 # smaller chunks
md-chunk-lite guide.md --outline # just show the headings
cat guide.md | md-chunk-lite - # read from stdinExample run:
Saved: guide.chunks.jsonl (7 chunks, biggest 151 chars)Each line of the .jsonl file is one chunk:
{
"id": "guide.md#3",
"source": "guide.md",
"index": 3,
"heading_path": ["Garden Guide", "Planting", "Tomatoes"],
"heading_level": 3,
"anchor": "tomatoes",
"start_line": 16,
"end_line": 24,
"part": 1,
"parts": 1,
"chars": 151,
"text": "### Tomatoes\n\nPlant tomatoes after the last frost. Give them sun.\n\n```python\n..."
}heading_path: all the headings above this chunk, from the top.anchor: the#linkGitHub makes for that heading, so you can link straight to it.start_lineandend_line: where the chunk is in the file (the first line is 1).partandparts: a big section is split into parts.part 2, parts 3means the 2nd of 3.chars: how longtextis.
--outline prints the headings:
Garden Guide [line 8, #garden-guide, 14 chars]
Tools [line 10, #tools, 47 chars]
Planting [line 14, #planting, 11 chars]
Tomatoes [line 16, #tomatoes, 151 chars]When you run it in a terminal it ends with one short line about the paid doc2md. --quiet turns it off, and it never shows when output is piped or redirected.
How it splits
Each heading starts a new section. A chunk never mixes two sections, so every chunk has one clear heading path.
A small section becomes one chunk. Its text is copied straight from your file, so the line numbers match.
A big section is split at blank lines. Lists, tables and code blocks stay whole when they fit.
A table that is too big is split by rows, and each part gets the header row again.
A code block that is too big is split by lines, and each part gets its own ``` fence again, with the same language.
A very long line is cut at the end of a sentence, then at a space if it has to be.
A heading with no text of its own (just more headings under it) does not get its own chunk, but it still shows in the
heading_pathof the chunks under it.
It knows # headings and underlined headings (=== and ---). It skips headings inside code blocks and YAML front matter (the --- block at the very top).
Options:
--max-chars N: biggest chunk, in characters (default 1500, smallest 200). About 4 characters make 1 token in English.--overlap-chars N: when a section is split, start each part with up to N characters from the end of the part before it (default 0). It is never added inside a code block or table, and never between two different sections.--prefix-path: start each chunk's text with its heading path, likeGarden Guide > Planting > Tomatoes. This often helps search. It counts toward--max-chars.--json: print one JSON object for scripts and AI agents instead of saving a file.
Known limits
Sizes are characters, not tokens. It does not load a tokenizer.
Markdown and plain text only. PDF, Word and HTML are not read. The paid doc2md turns those into chunks (with page numbers for PDFs).
No folders. Give it files (your shell can expand
docs/*.md). The paid doc2md walks whole folders.Not a full Markdown parser. A heading inside an HTML block, or an underlined heading that spans more than one line, may be handled wrong.
Overlap uses whole words from the part before, so it can be a little shorter than you asked for.
Lite vs paid
md-chunk-lite (free) | doc2md (paid) | |
Reads | Markdown and text files | PDF, Word (.docx) and HTML |
Chunks with the heading path | yes | yes |
Line numbers and anchors | yes | no (page numbers for PDFs instead) |
Rough token count on each chunk | no | yes |
Whole folders, sub-folders too | no | yes |
MCP server | yes | no |
Other good free tools
Pick what fits you. If you already use LangChain, its MarkdownHeaderTextSplitter also splits by heading. Chonkie and semchunk split any text by token count. md-chunk-lite is small, MIT, has no AI or tokenizer parts, gives you line numbers and anchors, and has an MCP server built in.
Use it from Claude Desktop or Cursor (MCP)
There is a small free MCP server built in. It needs uv.
Run it by hand to check it starts (it waits quietly for an app to talk to it):
uvx md-chunk-lite mcpClaude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"md-chunk-lite": {
"command": "uvx",
"args": ["md-chunk-lite", "mcp"]
}
}
}uvx --from md-chunk-lite md-chunk-lite-mcp starts the same server.
Tools (each one takes a file path or Markdown text):
Tool | What it does | Changes files? |
| Splits into chunks. Returns 100 at a time; use | No |
| Lists the headings with line numbers and anchors. | No |
| Gets one section by heading or anchor. | No |
| Saves the chunks to a | Writes one |
None of them use the internet.
Use it in GitHub Actions
Chunk your docs on every push, so your AI search or docs bot always gets fresh chunks. It also warns you when a section is too big for one chunk, right on the line in the pull request.
name: Docs chunks
on: [push, pull_request]
permissions:
contents: read
jobs:
chunks:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: tidybytetools/md-chunk-lite@v1
with:
files: docs/**/*.md
max-chars: "1500"
artifact-name: docs-chunks # download the JSONL from the run pageWant a big section to fail the check instead of just warn? Add fail-on-split: "true".
It runs the code in the same tag you pick, with only Python's standard library. No API key, no account, and nothing is sent outside GitHub. It works on Linux, Windows and Mac runners.
Inputs
Input | Default | What it does |
|
| Which files to read. Glob patterns, one per line or split by commas. |
|
| Patterns to skip. |
|
| Biggest chunk, in characters (200 or more). |
|
| Characters from the part before to repeat at the start of the next part. |
|
| Start each chunk's text with its heading path. |
|
| Where to save the chunks. |
|
| Fail when a section is too big for one chunk. |
|
| Fail when no files match. |
| (empty) | If set, upload the JSONL as an artifact with this name. |
| (empty) | Python to set up. Empty uses the runner's Python (3.10 or newer). |
Outputs
Output | What it is |
| How many files were read. |
| How many chunks were made. |
| Size of the biggest chunk, in characters. |
| How many sections were too big and got split. |
| Path of the JSONL file. |
The run page also gets a short report: chunks per file, and a list of every section that got split, with its line number.
For AI agents
Use when: you have a Markdown or text file (docs, notes, a README) and need chunks with heading paths and line numbers for search, embeddings or citing sources. Use
outline_markdownandget_sectionto read just one part of a long file.Don't use when: the file is PDF, Word or HTML (convert it first), or you need token-exact sizes.
Input: a file path or Markdown text, plus
max_chars(default 1500),overlap_chars(default 0) andprefix_path(default false).Output: chunks with
id,source,index,heading_path,heading_level,anchor,start_line,end_line,part,parts,chars,text.CLI exit code is 0 on success and 1 on error (message on stderr, or
{"ok": false, "error": ...}with--json). See alsollms.txt.
Python
from md_chunk_lite import chunk_file, chunk_markdown, outline, get_section
chunks = chunk_file("guide.md", max_chars=1000)
for c in chunks:
print(c["heading_path"], c["start_line"], c["end_line"])
install = get_section(open("README.md").read(), heading="Install")The chunker file uses only Python's standard library. Installing with pip also adds the mcp package for the MCP server.
Tests
pip install "mcp>=1.10,<2"
python3 -m unittest discover -s testsThe MCP tests are skipped if mcp is not installed.
License
MIT. See LICENSE.
Available Tools
4 toolschunk_markdownSplit Markdown into chunksARead-onlyIdempotent
Split a Markdown file or Markdown text into chunks by heading, for search, embeddings or RAG.
Use this when you need a long Markdown document (docs, notes, a README) broken into pieces that each know where they came from. A chunk never mixes two sections. Each chunk has heading_path (like ["Guide", "Install"]), anchor (the GitHub-style #link), start_line and end_line (1-based, in the file), part and parts (when a big section had to be split), chars and text. Code blocks and tables are kept whole when they fit; when they don't, each piece gets the fence or table header again. Plain code, not AI: same input, same chunks.
Do not use it for PDF or Word files (convert them to Markdown first), to just see the headings (use outline_markdown), or to read one section (use get_section). Sizes are characters, not tokens.
Returns {"source", "total", "start", "chunks": [...], "next_start"}. next_start is null when there are no more chunks.
Inputs: path, text, limit, start, +3 more.
get_sectionGet one Markdown sectionARead-onlyIdempotent
Return the text of one section of a Markdown file or text, found by heading title or anchor.
Use this when you only need one part of a long document, like the "Install" section of a README, so you don't have to read the whole file. If two headings have the same title, the first one is returned and "matches" tells you how many there are; use the anchor (from outline_markdown) to pick another.
Do not use it to split the whole document (use chunk_markdown).
Returns {"title", "heading_path", "level", "anchor", "start_line", "end_line", "chars", "matches", "text"}. If nothing matches, the error lists the headings.
Inputs: path, text, anchor, heading, +1 more.
outline_markdownList Markdown headingsARead-onlyIdempotent
List every heading in a Markdown file or text, with its level, path, anchor, line number and size.
Use this when you want a quick map of a long document before you read or chunk it, or to find the exact heading or anchor to pass to get_section. Headings inside code blocks and YAML front matter are ignored. Both "# Title" and underlined (=== / ---) headings are found.
Do not use it to get the text itself (use get_section or chunk_markdown).
Returns {"source", "count", "headings": [{"level", "title", "path", "anchor", "line", "end_line", "chars"}]}. chars is the size of that heading's own text, not counting the sections under it.
Inputs: path, text.
save_chunks_jsonlSave chunks to a JSONL fileADestructiveIdempotent
Split a Markdown file into chunks and save them as a JSONL file (one chunk per line).
Use this when the chunks are going into a search index, vector database or another program, and you want a file instead of a long chat reply. The chunks are the same as chunk_markdown gives. It writes only the one .jsonl file and replaces it if it is already there. It never changes the Markdown file.
Do not use it to look at chunks in the chat (use chunk_markdown).
Returns {"output_path", "chunks", "bytes", "biggest_chunk_chars"}.
Inputs: path (required), max_chars, output_path, prefix_path, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
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.
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.
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.
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
Related MCP Connectors
Convert files, URLs, and documents to clean, AI-ready Markdown via MCP.
PDF, Word, PowerPoint, Excel, HTML, EPUB to clean Markdown for LLMs/RAG; OCR for scans; chunks.
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Converts PDF, scans, DOCX, XLSX and PPTX to Markdown with tables and page-aware RAG chunks.
Related MCP Servers
- 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
- AlicenseAqualityBmaintenanceMCP server for markdown files — search, extract sections, list headings, find code blocks across docs.6111 npm8MIT
- 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.53 npm1MIT
- AlicenseNot gradedqualityCmaintenanceSplits Markdown documents into hierarchical sections with parent-child and sibling relationships, enabling structured document access for AI assistants.3Apache 2.0