Bosca CLI
Install the client, connect to a local instance, and manage content and other platform features.
Overview
The Bosca CLI (bosca) is built with Clikt and Apollo Kotlin. It communicates with the server via GraphQL and provides commands for platform administration. It compiles to a GraalVM native binary for fast startup.
Install the CLI
The installer downloads a platform package and verifies it against SHA256SUMS. Public releases are available from Bosca releases tagged with the bare version, such as 1.3.3.
Authentication
The CLI supports three authentication flows:
Credentials are stored in ~/.config/bosca/config.json (owner-read/write only). Password sessions refresh when needed. API tokens are stored directly.
Start local Bosca before logging in. Replace password if you changed the initial administrator password. The endpoint is a GraphQL URL and includes /graphql.
Saved account profiles
A CLI profile identifies a server/account pair and is separate from a social profile. profile use changes the saved default; put --profile before the subcommand or set BOSCA_PROFILE for one invocation. Stored credentials are only sent to their saved server.
Command-specific credential overrides vary. Use --help on your installed version to check supported --url, --token, and password options.
Replace UUID placeholders with real IDs. Create commands return the new IDs; later commands need these values. The examples below assume a saved login with the required permissions.
Command Tree
Content Management (data)
Work Operations (workops)
Full issue tracking with portfolios, programs, projects, tasks, sprints, and boards:
Localization (localization)
CI/CD (ci)
API Tokens (tokens)
MCP Server
The CLI includes a Model Context Protocol (MCP) server for AI tool integration. It exposes structured tools for content management, task tracking, and more:
Use a saved account profile for the MCP server, for example bosca --profile local mcp-server. MCP tools include: content_metadata (CRUD + set content), content_collection (CRUD + items), content_supplementary, content_relationship, content_template, and full WorkOps task management.