Simply CLI
simply is the command that hosts SimplySF's product command-line
tools. Install it once; the product CLIs install themselves the first time you use one.
Documentation: https://simplysf.github.io/simply-cli/
npm install -g @simplysf/simply-cli
simply gitlab mr list --project group/project
# Installing @simplysf/simply-gitlab to run gitlab:mr:list (first run only)…
# IID STATE SOURCE TARGET AUTHOR UPDATED TITLE
# 42 opened feature/thing main someone 2026-09-01 feat: the thing
simply atlassian jira whoami
# Installing @simplysf/simply-atlassian to run atlassian:jira:whoami (first run only)…
Every later run is instant.
Why this exists
Each product CLI used to own the simply command itself, which meant only one of them could be
installed at a time — npm links one binary name to one package. Now a single host owns simply and
the products are plugins, so they coexist, and adding a third changes nothing about the first two.
What it hosts
simply --help lists every topic whether or not they are installed — the command list ships with
the host, so you can discover a command before anything is fetched.
Installing ahead of time
The first run of any command from a not-yet-installed product does an npm install, which needs
network access and permission to write to the CLI's data directory. In CI, a container image, or an
air-gapped machine, do it up front instead:
npm install -g @simplysf/simply-cli
simply plugins install @simplysf/simply-atlassian
simply plugins install @simplysf/simply-gitlab
In a Dockerfile that is two lines and it makes every later invocation offline-safe.
Managing what is installed
simply plugins # what is installed, and at what version
simply plugins update # update all of them
simply plugins uninstall @simplysf/simply-gitlab # remove one
simply plugins install @simplysf/[email protected] # pin a version
Plugins live in the CLI's own data directory, not in global node_modules, so nothing here
competes with anything else you have installed.
Upgrading from a standalone install
If you previously installed a product CLI directly, it owned simply itself. Replace it:
npm uninstall -g @simplysf/simply-atlassian @simplysf/simply-gitlab
npm install -g @simplysf/simply-cli
Your commands do not change. simply atlassian jira issue view PROJ-42 and
simply gitlab mr list --project group/project are exactly what they were — only what owns the
simply binary is different. Scripts keep working.
Version ranges
The host declares which version of each product it will install:
"jitPlugins": {
"@simplysf/simply-atlassian": "0.x",
"@simplysf/simply-gitlab": "0.x"
}
A product can ship as many releases inside its range as it likes without the host moving. Leaving
the range needs a host release, which is the one place the two are genuinely coupled.
Windows: an unexpected undefined package
simply 0.4.0 and earlier, on Windows, also installed an unrelated npm package named undefined
alongside each product, because of how the version range reached npm
(design 0004). It was never loaded or run, but to
remove it, upgrade simply and then run:
simply plugins reset --hard
That removes every installed product; each one reinstalls itself the next time you use it.
Issues
Report anything about the simply command itself at
https://github.com/SimplySF/simply-cli/issues. For a problem with a specific command, the product
repo is the better place — simply-atlassian,
simply-gemini, or
simply-gitlab.
Documentation
https://simplysf.github.io/simply-cli/ covers simply and every product it hosts: the command
reference for each, the guides that ship with each package, and how to configure the MCP servers.
It is built from the published packages, so it describes the versions people actually have
installed rather than whatever is on main.
Contributing
See CONTRIBUTING.md.
License
Apache-2.0. See LICENSE.txt.
