
kiriya
io.github.SatPaingOoPublished by GitHub account SatPaingOov0.3.0Updated Oct 24, 2026
Developer tools for files, git, ports, processes and more, the same on Windows, Linux and macOS
Overview
A local MCP server exposing kiriya's cross-platform developer toolbox: files, git, ports, processes, archives, encoding and more, with safety confirmations.
- What you can do
- Find, read, search, compare, copy, move, rename and delete files and folders, with deletions going to the trash and multi-file changes shown as a plan first. Check git status, fetch, pull and switch across every repository under a folder. Inspect and end processes, see which process holds a TCP port, find a free port, and check local addresses, TCP reachability and DNS. Make and open ZIP and tar.gz archives, and convert text between base64, hex, URL encoding, JSON, JWT, times and cases. Read environment variables, PATH and .env files, generate random identifiers, passwords and tokens, and scan a folder for committed secrets.
- When to use it
- Useful when you want an assistant to handle everyday local developer chores the same way on Windows, Linux and macOS, such as cleaning up build output, checking repository status across a folder, or finding what holds a port. It is meant for agents that should act only after confirmation on anything irreversible.
- Requirements
- Runs as a local process via npx from the npm package kiriya. Needs Node.js 22.13 or later. No accounts, API keys or environment variables are declared. A doctor command checks runtime, trash, clipboard, git, docker and plugins on the machine.
Installation
In SourceWeft
- Open kiriya in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
Then check what this machine gives it:
Every 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
Finding your way
Help goes three steps deep, and each step names the next, so nothing has to be guessed.
kiriya 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:
Every 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
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
Project
Source: README.md at commit 332da3c
Tools
0Version history
6- v0.3.0LatestOct 9, 2026
- v0.2.0Oct 3, 2026
- v0.1.3Oct 3, 2026
- v0.1.2Sep 24, 2026
- v0.1.1Sep 23, 2026
- v0.1.0Sep 23, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts