Introduction

Command Line Interface clio is the utility for integration Creatio platform with development and CI/CD tools.

Please give clio-explorer, a Visual Studio code extension for clio a try! This extension provides user interface over clio commands.

Installation and features

Prerequisite: clio requires the .NET SDK (or, at minimum, both the .NET runtime and the ASP.NET Core shared runtime — Microsoft.AspNetCore.App). The SDK bundles the ASP.NET Core shared framework, so SDK-based installs need nothing extra. Runtime-only installs that ship only the base .NET runtime (Microsoft.NETCore.App) without ASP.NET Core — e.g. minimal CI agents — are not supported: clio references the ASP.NET Core shared framework (used by clio mcp-http) for all commands, so it will fail to start with a "framework not found" error when ASP.NET Core is absent.

Windows

To register clio as the global tool, run the command:

dotnet tool install clio

you can register clio for all users:

dotnet tool install clio -g

To unregister clio as the global tool, run the command:

dotnet tool uninstall clio

or for all users:

dotnet tool uninstall clio -g

More information you can see in .NET Core Global Tools overview.

Context menu

clio register

https://user-images.githubusercontent.com/26967647/169416137-351674ca-0bd2-44f1-83af-df4557bd02fd.mp4

clio unregister

MacOS / Linux

1. Download .net 8 for Mac/Linux

2. Register clio as the global tool, with the command:

dotnet tool install clio

More information you can see in .NET Core Global Tools overview.

Execute command in terminal for success check

clio help

Help and examples

To display available commands use:

clio help

For display command help use:

clio <COMMAND_NAME> --help

Run with docker

Build

docker build -f ./install/Dockerfile -t clio .

Run

docker run -it --rm clio help
docker run -it --rm clio reg-web-app -help

Commands Reference

Explore clio commands

Contributing

See CONTRIBUTING.md for build setup, test targets, code style, and PR workflow.

MCP Server

Clio supports Model Context Protocol (MCP) for integration with AI code agents.

Prerequisites

Install clio as a global .NET tool (see Installation above), then verify:

clio mcp-server --help

Registering in AI Code Agents

All agents use stdio transport with the same command: clio mcp-server.

Claude Code

claude mcp add clio -- clio mcp-server

Or add to .claude/settings.json in your project (or ~/.claude/settings.json globally):

{
  "mcpServers": {
    "clio": {
      "command": "clio",
      "args": ["mcp-server"],
      "type": "stdio"
    }
  }
}

GitHub Copilot (VS Code)

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: Add Server, then follow the guided flow.

Alternatively, add to .vscode/mcp.json manually:

{
  "servers": {
    "clio": {
      "type": "stdio",
      "command": "clio",
      "args": ["mcp-server"]
    }
  }
}

GitHub Copilot CLI

Inside a Copilot CLI session, run the interactive command:

/mcp add

Then follow the guided flow to register a stdio server with command clio and argument mcp-server.

Alternatively, add to ~/.copilot/mcp-config.json (global) or .mcp.json (project root) manually:

{
  "servers": {
    "clio": {
      "type": "stdio",
      "command": "clio",
      "args": ["mcp-server"]
    }
  }
}

Codex CLI

codex mcp add clio -- clio mcp-server

Alternatively, add to ~/.codex/config.toml manually:

[mcp_servers.clio]
command = "clio"
args = ["mcp-server"]

Testing with MCP Inspector

npx @modelcontextprotocol/inspector dotnet run --project ~/Projects/clio/clio mcp-server

Or configure manually:

• Command: dotnet
• Arguments: run --project /path/to/clio/clio mcp-server
• Transport Type: STDIO

This opens a browser interface to test MCP tools.

Available MCP Tools

list-pages - List Freedom UI pages

• packageName (optional) - Filter by package
• searchPattern (optional) - Filter by name pattern
• limit (optional) - Max results (default: 50)
• environmentName / uri+login+password - Connection

get-page - Get page schema body

• schemaName (required) - Page schema name
• environmentName / uri+login+password - Connection

update-page - Update page body (Destructive)

• schemaName (required) - Page schema name
• body (required) - New JSON body
• dryRun (optional) - Validate only
• environmentName / uri+login+password - Connection

install-application - Install application package

Workspace Solution Generation (.slnx)

Starting from September 2025, the createw command generates a solution file in .slnx format. All projects are added in a sorted order by their relative path, ensuring a stable and repeatable solution structure.

• Solution file: .solution/CreatioPackages.slnx
• Projects: always sorted by path
• Command: clio createw

This change improves consistency for CI/CD and version control.

SSO sign-in

For an SSO-only Creatio site, register a public OAuth client with authorization_code and refresh_token, require PKCE S256, and register a loopback redirect such as http://127.0.0.1:<port>/callback (or provide an HTTPS redirect for paste-back mode). Then run:

clio reg-web-app work -u https://work.creatio.com --clientId <client-id> --auth-flow authorization-code --redirect-port 37319
clio login -e work

The authorization-code flow carries the signed-in user's own permissions, unlike client_credentials, and is intended for interactive use against corporate SSO sites. Use clio auth-status -e work in automation; when it returns non-zero, ask a human to run clio login once. Tokens are stored outside appsettings.json under the owner-only clio token cache.