Bundle a tool directory into a self-containedDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/superradcompany/tool-cli/llms.txt
Use this file to discover all available pages before exploring further.
.mcpb archive. The output file contains the manifest.json and all files referenced by the entry point. Validation runs automatically before packing unless you pass --no-validate.
Synopsis
Options
Path to the tool directory to pack. Defaults to the current directory.
Output file path for the bundle (e.g.,
./dist/my-tool.mcpb). Ignored when --multi-platform is used, because multiple files are written automatically.Skip the validation step before packing. Not recommended for production use.
Treat validation warnings as errors. The pack aborts if any warnings are found.
Print each file as it is added to the bundle.
Create a separate bundle for each platform defined in
platform_overrides, plus a universal bundle. The tool-cli checks _meta["store.tool.mcpb"].mcp_config.platform_overrides first, then falls back to server.mcp_config.platform_overrides. Output filenames are derived from the package name and platform identifier automatically.Examples
The .mcpb format
A.mcpb file is a ZIP archive containing manifest.json and the bundled source files. Tools with HTTP transport or reference mode (no entry_point) use the .mcpbx extension instead, which signals to hosts that the package uses extended MCPB features.
tool install and tool publish both understand both formats. The correct extension is chosen automatically based on what your manifest uses.
--multi-platform requires platform_overrides to be defined in the manifest. Run tool validate first if you are not sure whether your manifest is configured correctly.