Developers · Early access

Flieber CLI and MCP: technical reference

Flieber exposes sales, adjusted sales, forecasts, catalog and store onboarding as tools for AI agents. The same tools run in the command line and over MCP, under one contract (flieber contract v1).

Overview

Three ways in

Command line

The flieber command, in your terminal.

Local MCP server

uvx flieber@latest mcp, over stdio. Available now; includes the sign-in tools sign_in_start and sign_in_finish.

Hosted MCP server

https://mcp.flieber.com/mcp, for Claude and ChatGPT in the browser as a custom connector. Signs in with your Flieber account (OAuth), passes your sign-in through and stores nothing; offers the same tools except the two sign-in tools.

Flieber CLI · Early access

Give your agents Flieber’s data and tools

Flieber CLI puts Flieber’s data and actions in your terminal and in local MCP clients such as Claude Code, Cursor, Claude Desktop and Muse: sales, adjusted sales, forecasts, catalog and store onboarding, through the same tools in the command line and over MCP. One command installs it, creates your Flieber account or signs you in, and gets your agents ready.

Install and sign in

macOS and Linux
curl -fsSL https://cli.flieber.com/install.sh | sh
Windows (PowerShell)
irm https://cli.flieber.com/install.ps1 | iex

The installer sets up Flieber CLI, opens your browser to create your Flieber account or sign in, lists your organizations and connects Flieber to your AI tool. Running it again is safe and upgrades it. Flieber CLI is the flieber package on PyPI.

Prefer one click on Windows? Download flieber-install.bat and double-click it.

Connect another tool

Claude Code
flieber mcp register --client claude-code
Cursor
flieber mcp register --client cursor
Claude Desktop
flieber mcp register --client claude-desktop
Muse or any other local MCP client
uvx flieber@latest mcp

The installer connects your AI tool. Use these to connect another tool or to connect again. Add --scope project to write a project file your team can commit, so everyone connects the same way.

Give your agent the skills

Claude Code
flieber skills install --client claude-code
  • flieber-install Sets Flieber up.
  • flieber Teaches your agent which tool to use, how to read results and how to preview changes.

The installer adds both skills automatically when it finds Claude Code. Cursor reads them from the same place.

Account first
Creating your Flieber account is the first step. The installer walks you through it, or run flieber signup. You accept Flieber’s terms and the AI early access terms on the sign-in page. Your free trial starts when you create your account in Flieber.
Your sign-in stays on your computer
You sign in once, and the sign-in is stored in a file only you can read. You never paste a key or token into a chat.
Every change is previewed
Changes such as onboarding a store or mapping SKUs are previewed first and applied only after you confirm.
Only what you allow
Flieber reads only what your sign-in or API key allows. API keys read one organization, limited to the data you grant.
Remote machines and sandboxes
flieber login --remote prints a link to open on another device and asks for a one-time code.
Sign in

Other ways to sign in

By hand, with uv installed

Command
uv tool install flieber
Command
flieber login
Command
flieber tenants

New organization (you accept Flieber’s terms and the AI early access terms)

Command
flieber signup

API key (hidden prompt). Keys read one organization, limited to granted data; create them on the API keys page of the Flieber portal

Command
flieber auth login
Command
flieber status

Remote machine or agent sandbox: prints a link to open on another device and asks for a one-time code

Command
flieber login --remote
Setup

Manual setup

Claude Code
claude mcp add flieber -e FLIEBER_OAUTH_WRITES=1 -- uvx flieber@latest mcp
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json with --scope project)
{
  "mcpServers": {
    "flieber": {
      "command": "uvx",
      "args": ["flieber@latest", "mcp"],
      "env": {"FLIEBER_OAUTH_WRITES": "1"}
    }
  }
}
Any other stdio MCP client
uvx flieber@latest mcp
  • --scope project writes a .mcp.json file you can commit, so your team connects the same way.
  • If the client can’t find uvx, use its full path (which uvx or where uvx).
  • On Windows, run flieber mcp register --client claude-desktop from PowerShell, not WSL.
  • Multiple organizations: every tool takes an optional tenant argument (tenant id or org_ id); call tenants to list them.
Reference

Tools

The list of tools grows as Flieber adds them, so get the current list from Flieber itself. Run flieber docs in Terminal or PowerShell, or ask your AI tool connected to Flieber:

Terminal or PowerShell
flieber docs
Prompt
List all the Flieber tools available to you, with a brief description of each.
  • Every result names its signal in meta.signal: actual sales, adjusted sales or forecast. Actual and adjusted sales end at yesterday (UTC); the last days of adjusted sales are approximate. Forecasts start today.
  • Results have columns, rows and meta, up to 2,000 data points each. Larger requests coarsen from days to weeks to months (meta.coarsened_to) and page by series (next_offset).
  • Writes take two calls: the first, with commit=false, previews without changing anything; the second commits with its preview_id. Commit only after the user confirms.
  • Each tool takes an optional tenant argument (tenant id or org_ id); call tenants to list the organizations the sign-in can reach.
  • Results use product and store ids, not names, because store names aren’t unique.
  • Errors carry a stable code, a hint and a retryable flag; over MCP they set isError.
  • Set FLIEBER_OAUTH_WRITES=1 to let the agent make changes such as onboarding stores or mapping SKUs; every change is still previewed first.
  • The reference is in the terminal (flieber docs) and in the MCP resource flieber://docs/contract.
Reference

Errors

Every error carries a stable code, a hint and a retryable flag. Over MCP, errors set isError. For the current list of error codes, ask your AI tool connected to Flieber:

Prompt
Find Flieber’s documented error codes and explain what each means. Distinguish a complete documented catalog from errors you can identify in the available tool descriptions.