AgentParcel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTPARCEL_MCP_ROOTS | No | Optional sandbox: set to the folders the server may read and write (`;` on Windows, `:` on Mac and Linux). Remove `env` from a snippet to allow every path. | |
| ZIPSPLITTER_MCP_ROOTS | No | Backward-compatible fallback for AGENTPARCEL_MCP_ROOTS; still accepted when AGENTPARCEL_MCP_ROOTS is unset. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspectA | Read-only. Look at a path before splitting or rebuilding. For a .zip: entry count, sizes, entries bigger than one part, estimated number of parts at max_mb. For a AgentParcel part: set id, part n of N, which parts are present/missing in its folder, whether it is ready to rebuild. For a folder: the part sets in it (with missing parts), or for a normal folder file count/bytes and a worst-case part estimate. For any other file: size and worst-case part estimate. Paths must be absolute. |
| split_zipA | Use when a .zip is too big to upload/attach. Splits it into parts named _part01.zip, _part02.zip ... each <= max_mb, and each a complete, valid zip that opens on its own (files are never cut unless a single file is bigger than a part; such files become .001/.002 pieces). Returns absolute paths and byte sizes of every part: upload all of them. Never overwrites anything. The original can be rebuilt exactly (SHA-256 verified) with the rebuild tool or the AgentParcel apps. For anything that is not a .zip (folders, logs, videos...) use split_files. |
| split_any_fileA | Byte-level split of ANY file (PDF, video, dataset, CAD, a zip you must not repack, and so on) into numbered raw parts, each <= max_mb / max_bytes. Parts are not zips. Rebuilding concatenates them and checks the original SHA-256. The output folder also contains _agentparcel_bytes.json, HOW-TO-REBUILD.txt, and a dependency-free rebuild.py (Python 3 standard library only) so a receiver can rebuild without AgentParcel. Use split_zip or split_files when you want standalone zip parts. |
| split_filesA | Use when files or folders that are not a .zip are too big to upload (a big log, video, dataset, project folder, several files). Packs the inputs into <archive_name>.zip (folders keep their structure) and splits it into standalone zip parts <= max_mb, in one step, without writing the full zip anywhere permanent. A single file bigger than a part is cut into .001/.002 pieces inside consecutive parts. Returns every part's absolute path and size. Rebuild with the rebuild tool (extract=true gives the files back as a folder). |
| verifyA | Read-only check before rebuild. Confirms every part is present and each part's checksum matches the manifest. Works for zip part sets (_zipsplitter_manifest.json, and _agentparcel_zipset.json when that sidecar is present) and for byte-split sets (_agentparcel_bytes.json). Does not write a rebuilt file. ok is false when something is wrong; missing_parts, missing_names, and corrupt_parts name exactly which parts. A part that fails its SHA-256 is corrupt, not missing. |
| regenerate_partsA | Given the original file and an existing part set, rewrite only the parts that verify reports as missing or corrupt (or the part_numbers you list). Parts that already match are left untouched, so you can upload just the replacements. Works for a byte-split folder and, when a fresh split lands on the same layout, for a zip part set. If the zip layout does not match, nothing is replaced and the error tells you to split the whole zip again. An encrypted byte set needs password. The password is not stored. still_needed names any parts that are still missing or corrupt. |
| rebuildA | Rebuild the original from AgentParcel parts (made by this server or by any AgentParcel app). Zip part sets become the original zip (every file verified, size + SHA-256). A byte-split set (folder with _agentparcel_bytes.json, or any file in that folder) becomes the original file, byte for byte. Give the folder, any single part (the others are found next to it), or an explicit list. If parts are missing or corrupt it fails and names exactly which (missing_parts / missing_names / corrupt_parts). AgentParcel-apps.zip is ignored. Output never overwrites. extract=true unpacks a rebuilt zip into a new folder; it does not apply to a byte-split file. |
| make_apps_bundleA | Write AgentParcel-apps.zip (AgentParcel for Windows, Mac and Linux plus this MCP server and 'HOW TO REBUILD.txt') into output_dir, so a human who receives parts can rebuild them. Never overwrites (adds ' (2)'). Optional max_mb/max_bytes: fail if the bundle would be bigger. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The three split tools overlap superficially but have clearly different inputs/outputs: split_zip makes standalone zip parts from .zip, split_files packs non-zip files/folders into zip parts, and split_any_file makes raw byte-split parts. Descriptions make the boundaries workable, though an agent must read carefully to choose among them.
All names use snake_case and the split_* family is predictable. The set mixes verb-only names (verify, inspect, rebuild) with verb_noun names (split_zip, regenerate_parts, make_apps_bundle), which is a minor but noticeable inconsistency.
Eight tools is well-scoped for a file-splitting/rebuilding workflow. Each tool covers a distinct stage: split, verify, repair, inspect, rebuild, and provide a desktop helper bundle.
The surface covers the full lifecycle: inspect inputs, split zips/files/folders, verify part sets, regenerate missing or corrupt parts, rebuild originals, and create a human-friendly apps bundle. No obvious operational gaps for the stated purpose.