Documentation
CLI Reference
Path: /docs/cli
The Orchestrator CLI (orc) talks to your instance with a Personal Access Token.
Install and login
bash# From a package context that exposes orc, or your local checkout orc login
You will be asked for:
- Base URL (production: https://getorchestrator.app)
- Personal Access Token from the web app
Verify:
bashorc whoami orc status
Logout:
bashorc logout
Common commands
| Command | Purpose |
|---|---|
| orc login | Store API URL + token |
| orc whoami | Show auth identity |
| orc status | Connection / project status |
| orc list | List tickets (project scoped) |
| orc mcp:tools | List MCP tools against the server |
Exact subcommands depend on your installed CLI version. Prefer MCP HTTP tools from Cursor when working as an agent.
Project codes
Always pass an explicit project code when listing or creating tickets (ORC, GDADMIN, …). Do not rely on ambient cwd alone in multi-team accounts.
Agents vs CLI
| Actor | Auth |
|---|---|
| Human in browser | Auth.js session |
| orc CLI | Stored Bearer PAT |
| Cursor MCP | Authorization: Bearer in MCP config |
Do not paste passwords into chat or tickets. Rotate tokens if leaked.
Related
- API Reference
- MCP Server
- Repo: docs/auth.md, docs/commands.md