Publish

List your setup

Your files stay in your own public GitHub repository. Kitloom stores a description and links to the ZIP that GitHub builds from it. Listing is free.

Loading the form…

Before you publish

The repository is public and is the setup
Visitors download the whole repository as a ZIP, so it should contain the setup files and little else. A dedicated repository works best.
It has a README
What it does, what each file is for, how to install and customise it. Kitloom shows it on your page as plain Markdown, without HTML or images.
It has a licence
Add a LICENSE file. Without one, others have no right to reuse your work and the listing reads “No licence stated”.
It contains no secrets
Search every file for keys, tokens, passwords and private URLs — MCP configuration and hook settings in particular. Anything in a public repository is already exposed.
Anything that runs is explained
If the setup includes hooks, scripts or MCP servers, say in the README exactly what they execute and why.
Compatibility is honest
Tick only the agents the setup is written for. Listings always say “declared by the creator”.

Why a link and not an upload?

Kitloom does not store package files yet. Linking to GitHub keeps your setup under your control, with its history visible to anyone who wants to check it. Because the ZIP follows your repository, it has no fixed checksum.

Listings appear as soon as you publish. Maintainers can hide one that contains secrets, malware, or someone else's work. More on the About page.