token-cut-cli 0.1.7

Verify Token-Cut API integration from the terminal (no repo clone required)

token-cut-cli

Public client for Token-Cut. Your proprietary API stays private; customers only get this thin CLI + MCP shim.

Business model

What	Public?	Paid?
This PyPI package (token-cut-cli)	Yes	Free to install
cc_live_… API key	—	Yes (your Stripe plans)
Optimization + repo index on your API	Private server	Metered per key

The CLI cannot optimize without a valid key against your deployment.

Install

pip install token-cut-cli

Not on PyPI yet? Maintainer runs ./scripts/publish-cli.sh from the repo root.
Until then:

cd cli && pip install .

Verify integration (~1 min)

export TOKEN_CUT_API_URL='https://www.token-cut.com'
export TOKEN_CUT_API_KEY='cc_live_…'   # full key from Connect — not the prefix
token-cut verify

Shows token count and estimated cost before vs after for:

1. A short auth/optimize check (no repo graph)
2. A repo-graph optimize on a small public sample repo

Calls https://www.token-cut.com (override with TOKEN_CUT_API_URL).

IDE setup (Cursor · Claude · Copilot)

export TOKEN_CUT_API_URL='https://www.token-cut.com'
export TOKEN_CUT_API_KEY='cc_live_…'
token-cut mcp-config > ~/.cursor/mcp.json
# merge if file already exists — restart IDE

Uses python -m token_cut_cli.mcp_server from the installed package (no git clone).

Commands

Command	Purpose
token-cut verify	Test key + optimize + graph on a public sample repo
token-cut optimize "…"	One-off optimize JSON
token-cut mcp-config	Print MCP config for IDEs
token-cut-mcp	MCP stdio server (called by IDE)

Publish (maintainers)

See ../docs/PYPI_PUBLISH.md.