Installation
Install Solwyn CLI v0.3.0, check release availability, and configure Python and MCP requirements.
The Solwyn CLI ships as the solwyn-cli package on PyPI. It is a standalone terminal client for the Solwyn Cloud API — a different package from the solwyn Python SDK, with no dependency between them.
Install
This is the v0.3.0 CLI/MCP reference. PyPI 0.3.0 is available, with a wheel and source distribution uploaded October 14, 2026; neither is yanked. The published wheel's requirements, executable aliases and Python source were verified against the release checkout.
The older PyPI 0.2.0 artifact, uploaded September 11, predates the October additions; installing 0.2.0 does not install the full reference surface.
uv tool install --python 3.11 solwyn-cli==0.3.0uv tool install puts the CLI on your PATH in its own isolated environment. uv tool dir --bin shows the executable directory.
pipx install solwyn-cli==0.3.0python -m pip install solwyn-cli==0.3.0Use a dedicated virtual environment when installing with pip.
Source checkout
This reference was verified against release commit b26d2fae67e1ebb93dab19779908c034ffc4e179. For development, you can also install from an authorized CLI checkout at that commit:
uv tool install --force --python 3.11 .
solwyn --helpThe release contains the completed October implementation plus release metadata. Verify your installed version and help; MCP clients should inspect tools/list. The v0.3.0 reference inventory is 33 read tools / 37 guardrails tools.
MCP availability
MCP is included in solwyn-cli; no extra package or install extra is required. Both the published wheel and this checkout require Python 3.11+ and pin mcp==2.1.1. Use an isolated installation to avoid conflicts with another MCP SDK version. The server is local stdio; there is no hosted MCP endpoint.
PyPI publication is separate from the unpublished MCP Registry draft. Its proposed ai.solwyn/solwyn namespace is unverified. A working local server or a valid descriptor does not establish Registry publication or namespace ownership. Use the installed executable and client setup.
Requirements
- Python 3.11 or newer. The package declares
requires-python >=3.11; older interpreters are refused at install time. Releases are tested on 3.11, 3.12, and 3.13, and the built package is smoke-tested on Linux, macOS, and Windows. - An OS keychain, to store credentials. The CLI stores keys and login tokens through the platform keychain — Keychain Services, SecretService, or Windows Credential Manager. Without one, it still runs: pass a project key through
SOLWYN_API_KEYinstead. See Authentication.
The CLI pins one dependency exactly — the mcp package that backs solwyn mcp. Installing into an environment that already holds a different mcp version will conflict, which is one more reason to prefer uv tool install or pipx over a shared pip install.
Two names, one command
Installing exposes two entry points — solwyn and solwyn-cli. They resolve to the same program; use whichever reads better in your shell or scripts. This documentation uses solwyn.
No phone-home
The CLI does not report anything about you or your usage back to Solwyn. There is no telemetry, no update checks, and no phone-home — the only network traffic it originates is the API calls a command explicitly makes on your behalf, using credentials you supplied. It never collects provider keys, prompts, or responses.
Verify your installation
Confirm the version:
solwyn --versionFor an installed v0.3.0 release, it prints:
solwyn 0.3.0List the available commands:
solwyn --helpIf both commands print without error, the CLI is installed correctly.
Once you have a credential, run the diagnostics:
solwyn doctordoctor checks the config file, the keychain, API readiness, your stored credential, and the bundled API snapshot, and exits 0 when everything passes.
Separate package from the SDK
The CLI and the SDK are distinct packages that do different jobs. You can install both in one environment.
| Package | Install command | What it does |
|---|---|---|
solwyn-cli | pip install solwyn-cli | Terminal client that talks to the Solwyn Cloud API. |
solwyn | pip install solwyn | Python SDK that wraps your LLM provider client. |
They have no dependency on each other — installing or upgrading one never pulls in the other.