install_packageLABSCO SUMMARY
The whole client, including publish.
Most package-manager integrations stop at reading and installing; this one also creates, builds and publishes, which means an assistant can take a package from template to repository without a terminal. That also means the same token of trust covers publishing, so decide deliberately whether an agent should hold it. The default configuration points at localhost, so expect to edit the repository list before anything useful resolves.
What it is
The full Criage client surface exposed over MCP. Everything the command-line client does is reachable as a tool, so package management can happen in the same conversation as the code that needs the package.
What you get
- Packages installed from a repository, removed, updated to the latest version, listed, and inspected in detail —
install_package,uninstall_package,update_package,list_packages,package_info - Repositories searched for packages, and one repository's information read —
search_packages,repository_info - New packages created from a template with a name, author and description, then built and published to a repository —
create_package,build_package,publish_package - All the archive formats the main client supports: criage, tar.zst, tar.lz4, tar.xz, tar.gz and zip
- Cross-platform operation on Windows, Linux and macOS
Requirements
Go, to build the binary: go mod tidy then go build -o criage-mcp-server ., after which your client launches that binary directly. It speaks MCP over standard input and output. Configuration is read from ~/.criage/config.json and created automatically with defaults if it is missing — the defaults point at a repository on http://localhost:8080, with package, cache and temp paths under ~/.criage, a 30 second timeout, a concurrency of 4 and HTTPS not forced.
Setup effort
Build from source — git clone https://github.com/criage-oss/criage-mcp
USE CASES
Adding a dependency mid-conversation
Search the repositories, read the package details, then install the version you want without switching to a shell.
Auditing what is installed
List the installed packages and inspect the ones you do not recognise.
Scaffolding a new package
Create it from a template with name, author and description, then build it in the same pass.
Publishing a release
Build and publish to the configured repository once the package is ready.
10 tools
Listed in project docs. Your client may show a different list.
uninstall_packageupdate_packagelist_packagespackage_infosearch_packagesrepository_infocreate_packagebuild_packagepublish_packageBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
Go 1.24.4 or newer
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/criage-oss/criage-mcp
cd criage-mcp
go mod tidy
go build -o criage-mcp-server .Add the Claude Desktop mcpServers block below to your config, pointing at the built binary
MCP Clients
Any MCP client
{
"mcpServers": {
"criage": {
"command": "<YOUR_PATH_TO_CRIAGE_MCP_SERVER>"
}
}
}