whoami
Who is signed in
The person this store sign-in belongs to (id, name, email), its scopes, and whether they run the store. Call it when unsure whether the person is signed in.
Takes no parameters.
Kadal Store
cc.kadalPublished by kadal.ccOfficial publisherv0.1.1Updated Nov 7, 2026
Find assets for what you're making, download what you own, and get a buy link to review.
The publisher's own server: Kadal Deck
Overview
AI-generated overview
Kadal Store's catalogue and library tools: search digital assets, download what you own into a project, and get a buy link to pay yourself.
- What you can do
- Search shelves and products, read prices, files, editions and licence terms, and get suggestions from a contents-free project summary
- List the products you own with their files and checksums, and get ten-minute download links
- Download owned files into the project folder, verified against sha256 and skipping files already present
- Build a review page link for items you do not own, so the person pays in the store's checkout
- Report mistakes, questions or ideas about a purchased file, and read Kadal's replies
- Show who is signed in and with which scopes
- When to use it
- Useful when you are building something that needs ready-made assets (planners, sound effects, music, shaders, 3D models, icons, templates) and want an assistant to find fitting products, pull the ones you already bought into the project, or hand you a checkout link for the rest.
- Requirements
- Either the hosted endpoint at store.kadal.cc with OAuth sign-in, or the local npm package run with npx, which needs Node 20 or newer and a one-time browser sign-in via the CLI login command. The local server uses that saved sign-in and serves the folder it was started in unless told otherwise.
Before you install
The tools act as the signed-in person, so anything they can see or download is exposed to the assistant. The recommend tool sends a summary of the project folder (names, dependencies, README headings, file-type counts) to the store; the CLI shows the text first, but the MCP tool does not ask. Buy links lead to a real checkout where the person pays; the server itself cannot buy. Download links are short-lived and carry access to owned files. Reports are visible to the person and Kadal.
Installation
In SourceWeft
- Open Kadal Store in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/cc.kadal%2Fstore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"kadal-store": {
"type": "http",
"url": "https://store.kadal.cc/mcp"
}
}
}README
Kadal Store CLI
Your store library, in your terminal and your AI agent.
[npm version] [CI] [Licence: AGPL-3.0-or-later] [Sponsor]
The Kadal Store sells digital downloads: planners and printables, sound
effects and music, shaders, 3D models, textures, icons and templates. @kadal/store brings it to
where you work. Search the store, get suggestions for the project you are in, download and sync
what you own, and get a link to buy the rest. It works the same for you in a terminal and for the
AI agent you already use (Claude, Cursor, Codex, any MCP client), on your own account and your own
model subscription.
An agent can find things, download what you own and hand you a link. It can never buy: payment always happens on the store's checkout page, in front of you.
Or install it: npm i -g @kadal/store, then kadal-store <command>. Node 20 or newer.
Sign in
You sign in on the store's own page, so your password never passes through the CLI. The token is
saved in ~/.config/kadal/store.json ($XDG_CONFIG_HOME is respected; %APPDATA%\kadal\ on
Windows), readable only by you, and renews itself. On a machine without a browser, use
--no-open, open the address anywhere, and paste the address the browser lands on back into the
terminal. If the store's page says it does not know this app, run kadal-store login --register.
kadal-store logout signs this machine out and revokes its access; so does removing
"Kadal Store CLI" under Account → Settings → Connected apps.
Commands
Find
search <words…>with--shelf <slug>,--style,--topic,--format,--kind asset|pack,--max <dollars>,--sort relevance|newest|price,--limit <1-50>,--cursor <next page>.shelveslists the store's shelves (use a slug with--shelf).show <slug>: prices per licence tier, the licence (what each tier allows and doesn't), the files with their sizes and editions, what a pack holds, and its updates.
Suggestions for your project
--from <dir> reads only the README's headings, package.json's (or pyproject.toml's, Cargo.toml's)
name, description and dependency names, a count of file types, and the top-level names. It never
reads or sends what is inside your files, and you see the exact text before it goes. --yes
skips the question. Also --shelf, --format (both repeatable), --max <dollars>,
--include-owned, --limit <1-20>.
What you own
download <slug>puts one product's files in./<slug>(or-o <dir>).--file <name>(repeatable) picks files;--year 2027 --week sun|mon --lang en|ja|en-ja --size a4|a5|letter…picks one edition of a product sold in editions;--zipgets the whole product as one zip.sync [dir]mirrors everything you own intodir(default./kadal-store), one folder per product. Files already there with the same sha256 are skipped; nothing is ever deleted.--product <slug>(repeatable), the edition flags, and--dry-run.- Every file is checked against the sha256 the store gives before it is kept. A download that is
cut off leaves a
.kadal-partfile, and the next run picks up where it stopped. Downloads run four at a time (--concurrency <n>).
Buy
buy <slug[:tier]>… (tiers: standard, the default, personal, commercial) builds a page where
you see each item, its licence and price, and anything you already own. --open opens it.
Tell us about a problem
--kind mistake|question|idea; --page <n> for a PDF, --at <seconds> for audio or video. Use
- in place of the words to read them from stdin. When a fix ships, the product's update shows in
your library and the next download or sync gets it.
Everything else
whoami, logout, --help (and <command> --help), --version.
For scripts and agents
--jsonon any command prints one JSON document on stdout; everything meant for people goes to stderr. For the store's commands it is the store tool's answer exactly as the store sent it (shapes in the contract).downloadprints{slug, dir, files: [{fileId, name, path, bytes, sha256, status, resumed?, error?}], zip, counts},syncprints{dir, dryRun, files, counts},loginprints{ok, host, user, scopes, operator, config},logoutprints{ok, host, signedOut, revoked}, and arecommend --fromyou declined prints{sent: false}. Errors are{ok: false, error: {code, message, exitCode}}.- Exit codes:
0ok,1failed (the message says why),2usage,3not signed in (or the sign-in expired: runkadal-store login),4a download failed its checksum (nothing was kept). --host <url>orKADAL_STORE_HOSTpoints at another store, such as a local worker (--host http://localhost:8861). Each host keeps its own sign-in.
Connect your agent
Claude Code, with the skill and the MCP server together:
The local MCP server alone (it uses the sign-in from kadal-store login):
For Claude Desktop, Cursor, VS Code and others, point the client at npx -y @kadal/store mcp:
The hosted MCP server, for clients that sign in themselves (OAuth) and need nothing installed:
In Claude (web and desktop), ChatGPT, Cursor and VS Code, add https://store.kadal.cc/mcp as a
custom connector; the store's own page opens to sign in. Step-by-step for each app:
store.kadal.cc/agents.
Both servers are one entry in the official MCP Registry, cc.kadal/store (the hosted one, and this
package as its local version).
[Kadal Store MCP connector – tool definition quality and endpoint health on Glama] [kadalcc/store-cli MCP server]
The skill alone, for any agent that reads Agent Skills: npx skills add kadalcc/store-cli
(skills/kadal-store). It teaches the agent to find assets for the
project in front of it, download into it, never buy on its own, and report problems it finds in
files you bought.
kadal-store mcp --dir <path> serves another folder as the project.
The contract
Every command is one call to a tool of the store's hosted MCP server (POST https://store.kadal.cc/mcp, Streamable HTTP, OAuth 2.1 with PKCE). The tools, their inputs and
their outputs are specified in the store's apps/store-worker/docs/agents.md; the types are in
src/types.ts. Money is always integer US cents; URLs are absolute.
Development
See CONTRIBUTING.md and AGENTS.md.
Licence
AGPL-3.0-or-later, like the Kadal Deck engine. Security reports: SECURITY.md.
Source: README.md at commit c39cf20
Tools
12list_shelves
Store shelves
The store's shelves (its categories), each with a slug, name, blurb, how many products it holds, and its licence model. Use a shelf slug to narrow search_products or recommend.
Takes no parameters.
search_products
Search the store
Search the catalogue. Returns product cards: slug, name, kind (asset or pack), shelf, blurb, url, prices per licence tier in US cents, tags (style, topic, format), and `owned` (the person's tier if they already own it). Page with nextCursor.
Parameters
kindsortlimitqueryshelfstyletopiccursorformatmaxCentsget_product
Product details
Everything about one product: description, prices per tier, its files (name, bytes, minimum tier, edition), editions, what a pack contains and which packs include it, the licence (what each tier allows and does not), and its update history. Check the licence before suggesting a product for commercial work.
Parameters
slugrequiredrecommend
Recommend for this work
Products that fit what the person is working on. `context` is a few plain lines about the project and what it needs (project_summary's `text` is a good start; add what the person asked for). Never put file contents, secrets or personal data in it. Each item has a one-line `why` and a score; `packs` are bundles the person already owns part of (`ownedOf`). This only shortlists: read get_product for the best few, then recommend with your own reasons.
Parameters
limitcontextrequiredformatsshelvesmaxCentsincludeOwnedlist_library
What the person owns
Every product the person owns: the product card, their tier, its files (id, name, bytes, sha256, edition), whether a zip is available, and the latest update. File ids go to download_to_folder or get_download_links.
Takes no parameters.
get_download_links
Download links
Download URLs for files the person owns, each with its name, size and sha256, valid for 10 minutes; no cookie needed (curl -L works). Narrow with fileIds or an edition; zip: true adds one link for the whole product. To put files into the project, download_to_folder does the download and the checksum for you.
Parameters
zipslugrequirededitionfileIdscreate_buy_link
A link to buy
A link to a review page on the store where the person sees each item (picture, licence, price), anything they already own, and the total, and pays in the checkout themselves. Only when the person asked to buy or agreed to it; building the link charges nothing and buys nothing. Give them the URL, and never say something was bought.
Parameters
refitemsrequiredreport_problem
Report a problem
Tell Kadal about a product the person has: a mistake (a typo, a wrong date, a missing page, a broken file), a question, or an idea. Say where with fileName and page (PDFs, from 1) or timeSeconds (audio and video). The note is private to the person and Kadal, and its replies show in list_my_notes. Report only what you checked, in plain words, once per problem, and tell the person you filed it.
Parameters
bodyrequiredkindrequiredpageslugrequiredfileNametimeSecondslist_my_notes
The person's notes
The person's notes (reports) on products, with each one's status (open, accepted, declined, duplicate, fixed), a plain status line, and the thread with Kadal's replies.
Parameters
statusproject_summary
Summarise this project
A short summary of a project folder, without its contents: name and description from package.json / pyproject.toml / Cargo.toml, dependency names, tools it uses (Godot, Blender, Next.js, Obsidian…), the README's headings, file-type counts and the top-level names. It is what `kadal-store recommend --from` sends. Pass its `text` to recommend as context. Reads nothing else and sends nothing anywhere.
Parameters
dirdownload_to_folder
Download into the project
Download files the person owns into the project, each checked against its sha256; files already there with the same checksum are skipped. dir is relative to the project (default kadal-store/<slug>). Narrow with fileNames or fileIds (from list_library) or an edition, or zip: true for the whole product as one zip. Returns where every file went.
Parameters
dirzipslugrequirededitionfileIdsfileNamesoverwriteVersion history
1- v0.1.1LatestNov 5, 2026
Score
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
