@findyourmodel/cran
v0.1.7
Published
Cran CLI — log in once, install the MCP, and use Cran in any repo (link optional, for routing live traffic).
Readme
@findyourmodel/cran
Cran CLI — device login, project linking, proxy smoke tests, and IDE MCP install.
Full guide: docs/cli.md and https://trycran.in/docs/cli
Install
# Do NOT use: npm i -g cran (wrong package on npm)
npm i -g @findyourmodel/cran
# From monorepo:
npm run build:cli && npm i -g ./packages/cliQuick start
Connect once, then "use Cran" works everywhere on your account's default project:
cran login # browser sign-in, once per machine
cran mcp install cursor # or claude / windsurf / codexThen tell your agent: Use Cran for model selection. No per-repo cran link is needed — switch projects from the agent with the fym_use_project MCP tool.
cran linkis optional — run it only to route your app's live traffic through the Cran proxy (it writes a connection key to.env). Thencran devsmoke-testsmodel: auto.
Which project is this repo?
- Per repo:
.cran/config.toml(project_id,project_slug) - Per machine:
~/.cran/session.json(fromcran login)
cran whoami
cran status
cran projects list
cran link --project-id proj_…Commands
| Command | Purpose |
|---------|---------|
| cran login | Browser device auth → ~/.cran/session.json |
| cran logout | Remove session |
| cran whoami | Session + linked project (cwd) |
| cran projects list | All account projects |
| cran projects ensure | Create/find the dashboard product for this repo |
| cran link | (optional) mint a connection key + write .env to route live traffic |
| cran init | .env.example, gitignore, config template |
| cran status | Link + Connected check |
| cran dev | Smoke-test model: auto via proxy |
| cran open | Dashboard for linked project |
| cran mcp install <ide> | Cursor / Claude / Windsurf / Codex MCP |
| cran mcp run | Run Cran MCP with session env |
Tokens
- User CLI token (
cran login) — CLI and MCP only - Connection token (
cran link→OPENAI_API_KEY) — your app and production
Never commit .env.
