Tidy Byte Tools
One install for our free local tools: fix broken JSON, pull tables out of a PDF, turn documents into Markdown, and more. It also starts one MCP server with all of those tools, so an AI assistant can use them on your computer. No API key.
This does not replace the individual lite repos. It is a doorway that installs them together.
Try it
This command is not valid JSON (the keys have no quotes, and there is a trailing comma):
printf '{name: "Ada", city: "Austin",}' | tidy-byte-tools json-repair -q
-q hides a one-line tip about the paid cloud version. Real output from that command (0.1.0, 17 Nov 2026):
{
"name": "Ada",
"city": "Austin"
}
Install
Needs Python 3.10 or newer. Install it from PyPI:
pip install tidy-byte-tools
Or use pipx, which keeps it in its own space:
pipx install tidy-byte-tools
That also installs the eight lite tools. All of them come from PyPI. (hash-lite's PyPI name is tidy-hash-lite.)
Use it
printf '{name: "Ada", city: "Austin",}' | tidy-byte-tools json-repair
tidy-byte-tools pdf-table-pull report.pdf
tidy-byte-tools doc2md page.html -o page.md
tidy-byte-tools --help
tbt is a short name for the same command. Installing the package also gives you the original commands (json-repair-lite, doc2md-lite, and so on).
From Python, import a lite package directly:
from json_repair_lite import repair_one
repair_one("{name: 'Ada',}")["value"] # {'name': 'Ada'}
Use it from Claude Desktop, Cursor, or VS Code
The MCP server talks over stdio. After you install the package, add one of these configs. If you would rather not install it first, uvx can run it from GitHub.
Claude Desktop (claude_desktop_config.json) and Cursor (.cursor/mcp.json):
{
"mcpServers": {
"tidy-byte-tools": {
"command": "uvx",
"args": [
"--from",
"tidy-byte-tools",
"tidy-byte-tools-mcp"
]
}
}
}
If the package is already installed, you can use "command": "tidy-byte-tools-mcp" and leave out args.
VS Code (.vscode/mcp.json):
{
"servers": {
"tidy-byte-tools": {
"command": "uvx",
"args": [
"--from",
"tidy-byte-tools",
"tidy-byte-tools-mcp"
]
}
}
}
The server exposes 15 tools. Base64 tools are named base64_convert_text and base64_convert_file so they are not confused with the document converter. Most tools only read. save_chunks_jsonl, convert_to_markdown (when you set an output path), and extract_pdf_tables can write the files you ask for. check_links requests the URLs you give it.
You can also start the server yourself with tidy-byte-tools mcp.
The tools in this install
| Command | What it does | Lite repo |
|---|---|---|
json-repair |
Repair broken or incomplete JSON, including output from language models | json-repair-lite |
json-shaper |
Turn notes, CSV/TSV, or Markdown tables into typed JSON | json-shaper-lite |
base64 |
Encode or decode Base64 for text and local files | base64-lite |
hash |
Hash text or files with SHA-256, SHA-1, MD5, and SHA-512 | hash-lite |
md-chunk |
Split Markdown into chunks by heading, for RAG | md-chunk-lite |
doc2md |
Turn a PDF or HTML file into clean Markdown | doc2md-lite |
pdf-table-pull |
Pull tables out of a PDF into CSV | pdf-table-pull-lite |
link-check |
Check web links for status codes and redirects | link-check-lite |
Paid cloud tools and the API
If you want the same kind of work in the cloud, pay per use:
- Apify store: https://apify.com/tidybytetools
- HTTPS API: https://tidybytetools.tidybytetools.workers.dev
The site is https://tidybytetools.github.io.
Limits
- These tools run on your computer. They are not a hosted service.
link-checkneeds a network. The other tools work offline.- The PDF tools read text PDFs. A scanned page with no text layer will not give useful tables or Markdown.
- This wrapper does not change how each lite tool works. See that tool's README for its flags and limits.
- Official PyPI and MCP Registry install names for this toolkit are not live yet. Use the GitHub install above until they are.
License
MIT. See LICENSE. Changes and ideas are welcome — see CONTRIBUTING.md.
Metadata
Release files for tidy-byte-tools 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tidy_byte_tools-0.1.1.tar.gz | 58.6 kB | With provenance | Details for tidy_byte_tools-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tidy_byte_tools-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for tidy_byte_tools-0.1.1-py3-none-any.whl |
Total release size: 66.4 kB
Release files / tidy_byte_tools-0.1.1.tar.gz
| Download URL | tidy_byte_tools-0.1.1.tar.gz |
|---|---|
| Size | 58.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bdb5422004c77341013ed97ad1d45125419b709b5a83cc13101d885c409dd857
|
|
BLAKE2b-256 checksum How to use checksums |
0a203ace3fbbd9abe3093ff0a0f12fcd73cb36d939b61966fceb6ab97c6d1c8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / tidy_byte_tools-0.1.1-py3-none-any.whl
| Download URL | tidy_byte_tools-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00d13df081589e553cf263187fef71f980c2f8f2b873919e62bc396a3d86aa78
|
|
BLAKE2b-256 checksum How to use checksums |
b7287b45cd4f5696a6f53910e84cf994b0c235f2565ffb67db63e88a2577cdc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for tidy-byte-tools 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for tidy_byte_tools-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.