Installation¶

Installation runs entirely through the customer portal: one line downloads the binary for your platform, connects the device to your portal account and stores the license.

Install one-liner¶

# Linux / macOS
curl -fsSL https://portal.stefanbaust.de/api/v1/install/cco-mcp-server.sh | sh

# Windows (PowerShell)
irm https://portal.stefanbaust.de/api/v1/install/cco-mcp-server.ps1 | iex

On first run, the script shows a short code and a portal URL. Open the URL in your browser, sign in with your portal account and confirm the code. No account yet? Register first at portal.stefanbaust.de.

The installer then takes care of the rest:

downloads the binary for your platform and verifies it via SHA-256,
fetches your license key from the portal,
stores everything under ~/.cco-mcp-server/ (a stable path, so your MCP configuration survives updates):

File	Contents
`bin/cco-mcp-server`	the server binary
`portal-token`	your account token (revocable in the portal; also used by `cco-mcp-server update`)
`license.key`	your license (refreshed on every run)

Running the same one-liner again updates an existing installation. Alternatively, the server updates itself, see Operation.

Run from any terminal directory¶

The installer adds cco-mcp-server to your user PATH. No administrator rights are needed. Windows updates the current PowerShell session immediately; restart other terminal applications to pick up the change. On Linux and macOS, open a new terminal after installation. Bash, Zsh and Fish are supported.

cco-mcp-server --version
cco-mcp-server add-manager
cco-mcp-server update

For an existing installation, run the install one-liner again to add PATH. Updating only the binary with cco-mcp-server update does not set up PATH. Your saved Manager profiles remain available from every directory. Keep the full executable path in desktop MCP configurations, since desktop apps may use a different PATH.

To manage PATH yourself, pass --no-modify-path to the shell installer or -NoModifyPath to the PowerShell installer. To remove the command from PATH, remove the cco-mcp-server: terminal command block from the shell startup files reported by the installer, or remove the binary directory from your Windows user PATH. Fish uses fish/conf.d/cco-mcp-server.fish in your config directory.

Options¶

The installer accepts arguments after -s --:

# Install a specific version
curl -fsSL https://portal.stefanbaust.de/api/v1/install/cco-mcp-server.sh | sh -s -- --version 0.7.0

# Without browser confirmation (e.g. scripts/CI): pass the account token directly
curl -fsSL https://portal.stefanbaust.de/api/v1/install/cco-mcp-server.sh | sh -s -- --token cpt_...

Supported platforms: Linux x64, Windows x64, macOS Intel and Apple Silicon. If your platform is missing, contact stefan.baust@stefanbaust.de.

Adding a Manager¶

Before the server can start, it needs the credentials of at least one CCO Manager. The easiest way is the interactive wizard:

cco-mcp-server add-manager

It asks for a stable profile key, readable display name, type (on-premise or Cloud Edition), URL, credentials, read-only access and privacy mode. It tests the connection before saving, and finally prints the ready-made snippets for registering the server in your MCP client. All variants (environment variables, multiple Managers) are described on the Configuration page.

Version 1.1.0 includes an experimental privacy filter that is disabled by default (privacyMode=off). You can enable it in the wizard or set "privacyMode": "minimize" on a profile. Revenue, article, price and quick-selection workflows remain available when enabled; raw requests, action deployment and job starts are blocked. Read Privacy mode for the filter's limits and the DPA/AVV and legal considerations for your use. The 1.0.0 tutorial predates this feature.

Registering in the MCP client¶

Codex and ChatGPT Desktop on Windows¶

Run the setup wizard in PowerShell:

cco-mcp-server add-manager

For an on-premise Manager, choose type 2 and give the profile a clear name, such as fp21-demo. Run the wizard again to add another Manager.

In the desktop app, open Settings → Plugins → MCPs → Add → Add MCP server (older versions use Settings → MCP servers → Add server). Choose STDIO, name the server cco-manager, and enter the full executable path, for example C:\Users\Alex\.cco-mcp-server\bin\cco-mcp-server.exe. Leave Arguments empty to make all saved profiles available. Save the connection. After adding or changing Manager profiles, switch the MCP connection off and on, then start a new conversation. An existing conversation can retain the previous Manager list. If the new conversation still shows old profiles, restart the desktop app.

If you use the Codex CLI, you can register the same server from PowerShell:

codex mcp add cco-manager -- "$env:USERPROFILE\.cco-mcp-server\bin\cco-mcp-server.exe"

The desktop app and Codex CLI share %USERPROFILE%\.codex\config.toml. The equivalent configuration is:

[mcp_servers.cco-manager]
command = 'C:\Users\Alex\.cco-mcp-server\bin\cco-mcp-server.exe'

Replace Alex with your Windows user name. The TOML path must be absolute; PowerShell variables such as $env:USERPROFILE are not expanded there.

Start a new conversation and ask: "List my CCO Managers and check their connections." Then name a profile in your request, for example: "On fp21-demo, show revenue by POS for August 2026. State the period and currency."

To restrict this connection to one saved profile, add args = ["--manager", "fp21-demo"] below the command. Leave CCOM_URL unset when using profiles: that variable overrides the profiles file.

See the official MCP setup documentation.

Claude Code¶

With Manager profiles from add-manager, the path to the binary is enough:

claude mcp add cco-manager -- ~/.cco-mcp-server/bin/cco-mcp-server

Or with a single Manager directly via environment variables:

claude mcp add cco-manager \
  -e CCOM_URL=https://ccom.example.com \
  -e CCOM_ADMIN_USER=Admin \
  -e CCOM_ADMIN_PASSWORD=... \
  -- ~/.cco-mcp-server/bin/cco-mcp-server

Claude Desktop¶

In claude_desktop_config.json:

{
  "mcpServers": {
    "cco-manager": {
      "command": "/home/ich/.cco-mcp-server/bin/cco-mcp-server",
      "env": {
        "CCOM_URL": "https://ccom.example.com",
        "CCOM_ADMIN_USER": "Admin",
        "CCOM_ADMIN_PASSWORD": "..."
      }
    }
  }
}

You can omit the env block if your Managers are stored in ~/.cco-mcp-server/managers.json. For the Cloud Edition, CCOM_CLIENT_ID/CCOM_CLIENT_SECRET take the place of user and password, see Configuration.

Running MCP clients and sessions must be restarted to pick up the new server.