Skip to content
Keboola Docs

Get started with kbagent

A guided first run of the kbagent CLI — install it, connect a Keboola project, verify with doctor, and run your first read commands. Plus multi-project and organization setup.

This walkthrough takes you from nothing to browsing a real project with kbagent in a few minutes. Follow it top to bottom for a single project; the Connect more section covers multi-project and organization setup.

Pick your operating system:

The prebuilt wheel via the install script:

Terminal window
curl -LsSf https://raw.githubusercontent.com/keboola/cli/main/install.sh | sh

Or with uv (auto-updates, version-pinnable):

Terminal window
uv tool install "git+https://github.com/keboola/cli"

Confirm it's on your PATH (all platforms):

Terminal window
$ kbagent --version
kbagent v0.66.0

For one project you need a Storage API token and your stack URL:

Terminal window
kbagent project add --project prod \
--url https://connection.keboola.com --token YOUR_TOKEN

prod is an alias you pick — you'll use it with --project later, or set it as the default with kbagent project use prod.

kbagent doctor checks your configuration and connectivity. Once a project is connected it confirms the link and flags anything else worth doing (like installing the agent plugin):

kbagent doctor output: config found, project 'docs-demo' connected to the stack (L0 - Shopify, id 264), CLI version PASS, and warnings for the MCP server and Claude Code plugin

You can also test connectivity on its own with kbagent project status.

Explore what's there. Recent jobs:

kbagent job list --limit 5: a table of recent jobs in docs-demo with job ID, success status, component, created time, and duration

Terminal window
kbagent job list --limit 5 # recent jobs (shown above)
kbagent project list # connected projects
kbagent config list # configurations in the default project

Find configs, tables, buckets, and flows by name or content:

Terminal window
kbagent search "shopify"
  • Add --json to any command for machine-readable output — this is what an AI agent consumes.

  • Set a conversation ID when an agent drives kbagent, so platform observability can correlate the session (adds an X-Conversation-ID header):

    Terminal window
    export KBAGENT_CONVERSATION_ID="<unique-id>"

Several projects — register each with its own Storage token (project add), or bulk-onboard with a Manage API token:

Terminal window
KBC_MANAGE_API_TOKEN=xxx kbagent --allow-env-manage-token \
org setup --project-ids 901,9621 --url https://connection.keboola.com --yes

A whole organization (org admin) — kbagent registers every project and mints per-project tokens:

Terminal window
KBC_MANAGE_API_TOKEN=xxx kbagent --allow-env-manage-token \
org setup --org-id 123 --url https://connection.keboola.com --yes

Read commands then fan out across every connected project — see multi-project.


Next: How kbagent works →

Ask Kai

Ask anything about Keboola — I'll search the docs and cite the pages I use.