MCP installation

Install Baseline into OpenClaw

Baseline exposes seven legible MCP tools: setup, run, doctor, report, accept, schedule, and scrub preview. The CLI binary is a free local runner; Pro charges for cloud history, workspace tokens, remote MCP account operations, monitoring, and billing-backed retention.

curl -fsSL https://trackbaseline.com/install.sh | sh
baseline setup
baseline report
baseline accept RUN_ID --confirm "accept RUN_ID" --label clean-local
openclaw mcp list
baseline compare

Distribution

The installer downloads the latest checksummed release asset for macOS or Linux from GitHub Releases, verifies checksums.txt, and installs baseline into ~/.local/bin by default. Set BASELINE_INSTALL_DIR for a different destination or BASELINE_VERSION for a pinned release.

curl -fsSL https://trackbaseline.com/install.sh | BASELINE_INSTALL_DIR=/usr/local/bin sh
curl -fsSL https://trackbaseline.com/install.sh | BASELINE_VERSION=v0.1.0 sh

Cloud sync

baseline sync on --url https://trackbaseline.com --token YOUR_BASELINE_TOKEN
baseline doctor
baseline sync push

Remote MCP

Pro accounts can also connect to the cloud MCP at https://trackbaseline.com/mcp. The remote MCP never runs local probes; it reads account history, hotspots, self-history comparisons, workspace tokens, and Stripe portal handoffs after magic-link session auth.

POST https://trackbaseline.com/api/auth/magic-link
POST https://trackbaseline.com/api/auth/consume
Authorization: Bearer YOUR_SESSION_TOKEN
POST https://trackbaseline.com/mcp

Safety model

The MCP can read what the connected agent gives it. Baseline defaults to local SQLite and redacted summaries. Raw outputs are not exported unless allow_raw_output is enabled in ~/.baseline/config.json.

Recommended first Good Baseline

baseline setup
baseline report
baseline accept RUN_ID --confirm "accept RUN_ID" --label clean-local
baseline compare