Collavre

CLI for managing Collavre Creatives via MCP protocol.

Setup

# Configure (once)
collavre auth --url https://collavre.example.com --token <oauth_token>

# Verify
collavre list

The collavre script lives in scripts/collavre. Config is stored at ~/.config/collavre/config.json.

Commands

List root creatives

collavre list
collavre list --level 5              # deeper tree
collavre list --format json          # structured output

Get a creative subtree

collavre get 123
collavre get 123 --level 5 --comments

Search

collavre search "project name"
collavre search "urgent" --tags "v2"

Create

collavre create --parent 123 --desc "New task"
collavre create --parent 123 --desc "<h1>Rich content</h1>"

Update

collavre update 456 --desc "Updated title"
collavre update 456 --progress 1.0        # mark complete (leaf only)
collavre update 456 --parent 789           # move

Import markdown

collavre import --parent 123 --file plan.md
collavre import --parent 123 --stdin < plan.md
echo "# Quick\n## Plan" | collavre import --parent 123 --stdin

Batch operations

collavre batch --file ops.json

ops.json format:

[
  { "action": "create", "parent_id": 100, "description": "Task A" },
  { "action": "update", "id": 200, "progress": 1.0 },
  { "action": "delete", "id": 300 }
]

Key Concepts

• Tree structure: Creatives nest via parent_id. Use --level to control depth.
• Progress: Leaf = manual (0.0 or 1.0). Parent = auto-calculated from children.
• Import: Markdown headings/bullets become nested Creatives.
• Batch: All-or-nothing transaction. Requires approval.
• Description format: Accepts HTML. Plain text auto-wraps in <p> tags.

For detailed MCP tool parameters, see references/tool-reference.md.