Python, a working folder, and either a local backend like Ollama or a hosted API key.
Install
Purchase, install, authenticate, initialize.
You purchase access, install the package through a license-gated URL, authenticate locally, and initialize Clio inside an existing folder. The full setup path is six steps.
Purchase access, install with a license-gated URL, authenticate locally, then initialize Clio in place.
You can connect Claude Desktop, Cursor, or any MCP-ready client after the core install is working.
Test Mode
The commercial flow can be verified before the live switch.
Clio currently uses Lemon Squeezy in test mode while the store is being finalized. That still lets us verify checkout, subscriptions, license keys, webhook delivery, and the gated install path end to end.
What works now
Test checkout, test subscriptions, test licenses, account routing, validation, and webhook handling.
Clio install path
The download is gated by Clio’s own install endpoint, so test licenses are enough to verify the full access flow.
What this environment is for
Integration testing and store review readiness, not live customer charges.
Requirements
What you need before you install.
Clio does not require a hosted account by default, but it does assume a working local environment.
Python
A machine with Python and pip available.
License key
A Clio license key from purchase.
Working folder
An existing folder of material you want Clio to work inside.
Model backend
Either a local setup such as Ollama, or hosted access through API keys.
MCP client
If you want assistant access, a client that supports MCP, such as Claude Desktop or Cursor.
Install Flow
Purchase, install, authenticate, initialize.
The install path is short. Once you have a license key, the rest of the process follows a small sequence.
Purchase access
Get a Clio subscription and receive your license key.
Install the package
Use the authenticated install URL with your license key.
pip install "https://download.clioagent.com/install?key=YOUR_LICENSE_KEY"Authenticate locally
Register the license key on the machine where Clio will run.
clio auth YOUR_LICENSE_KEYInitialize a folder
Create the local .clio/ layer inside the folder you want to work in.
clio initSync your material
Process the folder and build the first version of the local memory system.
clio syncOptional: connect MCP
Expose the local memory to Claude Desktop, Cursor, or any MCP-ready client.
clio mcpProvider Setup
Choose between a fully local stack and higher-quality hosted extraction.
Clio Agent needs a model backend for extraction and mapping. The system supports both local and hosted paths, and the tradeoff is mainly between privacy and model quality.
Local backend
Use a local model process such as Ollama when you want the full stack to stay on the machine.
Hosted API backend
Use providers such as OpenAI or Anthropic through API keys when you want stronger extraction quality and accept the hosted-model tradeoff.
Account And License
Access is tied to a live subscription and validated through your license key.
Clio is currently paid-only. Your license key is linked to your subscription and is used both for package download and for local runtime validation.
License lifecycle
Simple commercial logic.
Your license key is tied to your subscription. Here is how access works.
Active
An active subscription allows package download and normal runtime use.
Inactive
A cancelled or lapsed subscription causes the key to become inactive.
Renewal
If you renew later, the key becomes active again through the same subscription link.
Account path
Use the account page for renewal, portal routing, and license-related troubleshooting.
Troubleshooting
A few things to check if setup does not work the first time.
Most setup issues fall into a small number of categories.
The install URL returned an error
Check that the license key is valid and tied to an active subscription.
Clio installed, but authentication failed
Confirm that the key was entered correctly and that the machine can validate the license.
The system runs, but no memory is being built
Check the selected model backend and confirm that the folder contains supported material.
The assistant cannot see Clio
Check the local MCP configuration and confirm that clio mcp is available in the configured environment.