kiriya
Developer tools for files, git, ports, processes and more, the same on Windows, Linux and macOS
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
kiriyaclaude mcp add kiriya -- npx -y kiriya@0.3.0 mcp --root{
"mcpServers": {
"kiriya": {
"command": "npx",
"args": [
"-y",
"kiriya@0.3.0",
"mcp",
"--root"
]
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
kiriya
One command-line toolbox for everyday developer work that behaves the same on Windows, Linux and macOS.
kiriya (ကိရိယာ, Burmese for "tool") saves remembering del and rm, netstat -ano and
lsof -i, clip and pbcopy, or writing a one-off script for each. It is one Node.js
program with no runtime dependencies. Every command answers --json, and
convert json --get reads a value back out of that answer without a second tool. Changes to
many files show a plan first, deletions go to the trash, and nothing that cannot be undone
happens until you type a confirmation. AI agents can use the same commands over MCP, under the same
rules.
Install
kiriya needs Node.js 22.13 or later.
npm install --global kiriyaThen check what this machine gives it:
kiriya doctorEvery release is published from CI with provenance,
so npm audit signatures can show which workflow built the copy you installed. Every module
below is tested on Windows, Linux and macOS with Node.js 22, 24 and the current release.
Getting started takes it from there, and CONTRIBUTING.md covers building from source.
Quick start
kiriya doctor # what this machine offers kiriya
kiriya port who 3000 # which process holds port 3000
kiriya files find --name "*.log" --older 30d # the same search in every shell
kiriya files delete dist --dry-run # the plan, before anything changes
kiriya git status ~/code --json # every repository under a folder, as JSONFinding your way
Help goes three steps deep, and each step names the next, so nothing has to be guessed.
kiriya --help # the modules, and the options every command accepts
kiriya help files # one module: its commands, and what each one takes
kiriya help files delete # one command: its arguments, options and exampleskiriya files delete --help says the same as that third line. The middle step lists each
command's option names underneath it, so a module's whole surface fits on one screen:
Commands
delete Send files and folders to the trash, or remove them for good with --permanent
--permanent --dry-run --yes --confirm --all
find Find files and folders by name, extension, type, size, age or emptiness
--name --ext --type --larger --smaller --newer --older --empty --all --limitEvery module also has a guide below with a full reference: every command, argument and option, what each does, and whether it can be undone.
Modules
| Module | What it does |
|---|---|
archive | ZIP and tar.gz archives, made and opened the same way on every OS with no zip, tar or 7-Zip installed. |
clip | Copy text to the clipboard and paste it back, with Unicode intact on every OS. |
completion | Tab completion for kiriya's modules, commands, options and values in bash, zsh, fish and PowerShell. |
config | kiriya's own settings, such as the plugins to load, in one file per user. |
convert | Convert text between base64, hex, URL encoding, JSON, JWT, times and cases, entirely on this machine. |
docker | docker compose for the project in the current folder, and a previewed clean-up of the engine. |
doctor | Check what this machine gives kiriya: runtime, configuration, trash, clipboard, git, docker and plugins. |
env | Environment variables, PATH and .env files, read the same way on every OS. |
files | Files and folders: create, find, read, search, compare, copy, move, rename and delete, the same on every OS. |
gen | Random identifiers, passwords and tokens from the operating system's secure random source. |
git | Git across every repository under a folder: status, fetch, pull and switch. |
net | Local addresses, TCP reachability and DNS lookups, the same on every OS. |
open | Open a file or folder in its default application, or a web address in the browser. |
port | See which process listens on a TCP port, end it, or find a free port, the same on every OS. |
proc | List, find and end processes, and show them as a tree, the same on every OS. |
secrets | Find secrets committed into a folder's files: tokens, private keys and passwords in plain sight. |
self-update | Ask the registry whether a newer kiriya exists, and install it with --apply. |
sys | This machine and the developer tools on it, described the same way on every OS. |
wait | Wait until a port listens, a web address answers or a file appears, the same way on every OS. |
AI agents
kiriya mcp serves these commands to AI agents over the Model Context Protocol. It offers
only commands that change nothing until you allow more, and asks you before any work that
cannot be undone. MCP server shows how to add it to a client.
Documentation
| For | Read |
|---|---|
| Using kiriya | Getting started · Usage · Modules |
| Guides | MCP server · Tab completion · Plugins |
| Contributing | CONTRIBUTING.md · Architecture · Design |
| Everything | Documentation index |
Project
Frequently asked questions
What is kiriya?
Developer tools for files, git, ports, processes and more, the same on Windows, Linux and macOS
How do I install kiriya?
It runs on your machine. In Claude Code: claude mcp add kiriya -- npx -y kiriya@0.3.0 mcp --root. For other clients, paste the JSON configuration from this page into their MCP settings.
Does kiriya need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is kiriya open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains kiriya?
It is published by SatPaingOo. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.