Skip to main content
Glama
Sign In
Roster

Roster

by brickshubkuwait
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brello

Query your team's work from the terminal, or straight from Claude. A small CLI and MCP server for Roster. No app, no SQL.

$ brello stats
team size: 7
open: 24   done: 37   overdue: 5
active now: 2

Install

npm install -g brello
brello auth
brello stats

brello auth: press Enter and your browser opens roster.bricks.com.kw/connect. Sign in with your Bricks Google account and request access. An admin approves it and picks what your terminal can do. Once approved, your terminal is connected and the key is saved to ~/.roster (only your user can read it).

Need a key? Run brello auth and sign in with your Bricks Google account. Closed the terminal before the approval? Run brello auth again within 24 hours of it. Approved once. After that your terminal reconnects on its own. Have a key from an admin? Type it at the brello auth prompt, or pbpaste | brello login. The command is brello (typing roster works too).

git clone https://github.com/brickshubkuwait/roster-cli-mcp.git
cd roster-cli-mcp && npm install && npm link
brello auth

Related MCP server: spreadsheet-qa-kit MCP server

Developer hub

Open Bricks Developers for setup guides, the searchable CLI/MCP reference, workflows and troubleshooting.

brello docs
brello help keys

Claude can use the roster_docs tool for the same links and key guidance, without an API call.

CLI

Command

What it shows

brello stats

Team dashboard — size, open / done / overdue, who's tracking

brello team

Your team members

brello overdue

Cards past their due date and not done

brello workload

Open + overdue cards per person

brello active

Who's tracking time right now (live Hubstaff)

brello comments

Recent comments on your team's cards

brello reactions

Recent emoji reactions on your team's cards

brello activity

Card history — moves (stage→stage), comments, splits, edits

brello search "<text>"

Find cards by title or client

brello user <name>

Everything for one person — every card, live AND archived, with their open/done/archived totals + what they're tracking now

brello card <id>

Every field on a card — workflow, Studio, Salesforce, send/view receipt, Slack thread, sizes and copy

brello studio [filter]

Bricks Studio review feed — status/version, comments, client views, and open/share links

brello client "<name>"

Everything for one client — every in-scope card (live + done), who's on it, with open/done/overdue totals

brello scope "<client>" --month YYYY-MM

One client in one month: what the contract sold vs what was shot, delivered and approved, per contract, plus special requests. ? means unknown and a note says why. Add --json for the raw response. e.g. brello scope "Sedra" --month 2026-10

brello due [days]

Cards due soon — the next N days (default 7), soonest first

brello done [days]

Recently completed cards — the last N days (default 14)

brello blocked

Blocked or stuck cards — explicit blockers, or overdue by 3+ days

brello recent [n]

Recently touched cards across your team (default 20)

brello now

Live pulse — who's tracking now, what's due today, and the latest card moves

brello stages

Board stages with your team's open card count in each

brello departments

The roster's departments and headcount

brello cards ["<stage>"]

Every card in a stage or matching filters; --history adds each card's stage history; --created-after / --created-before YYYY-MM-DD; 200 a page, --limit up to 1000 and --offset for the next page

brello stage-stats

Stage usage over the board's history; --department and --client narrow it

brello shoots

The company-wide shoot schedule; --from/--to, --client, --type, --status, --include-removed; each shoot has a readiness line

brello meetings

Meetings with owner, attendees and minutes status; --from/--to, --client, --owner

brello clients ["<name>"]

Client directory with Instagram handle, logo and open cards; --all adds archived clients

brello readiness [--days 7] [--json]

Upcoming shoots and what is still missing: plan, budget, models, props, call time

Run brello help to see them all. Full reference: QUERIES.md.

Add --json to any command for scripts: the raw JSON response, with no banner and no colour.

brello shoots --from 2026-10-01 --to 2026-10-31 --client Foodhall --json
brello meetings --owner Melani --json
brello clients --json

With --json, card results that name a client carry client_logo_url and instagram_handle, and team and user carry avatar_url.

Card changes (brello move, brello due <card> <date>, brello assign) take --reason "<why>", which is recorded on the card. Taking a card out of Backlog needs a due date first (DUE_REQUIRED), and moving a missed due date to a later day needs a reason (REASON_REQUIRED).

Studio

Bricks Studio works from the same key: submissions, review comments, versions, Creative Plans and clients. Studio answers as your own Studio login, so you see what you see there. Ids can be the first 8 characters.

Command

What it does

brello studio submissions ["<filter>"]

Studio submissions with client and internal status; --client "<name>", --status <s>, --type <t>, --mine, --limit n, --offset n

brello studio submission <id>

Every version with its files and their preview and download links, plus the Studio link

brello studio comments <id>

Review comments with version, author, timecode and file; --version n; --csv prints a spreadsheet, e.g. brello studio comments 1c11685c --csv > comments.csv

brello studio comment <id> "<text>"

Add a team comment; --at 0:42 pins it to a moment, --version n to a version, --file <fileId> to one file. The client never sees team comments

brello studio upload <id> <file...>

Upload a new version from images (jpg, png, webp, gif, heic) or a video (mp4, mov, webm), not both at once. It starts hidden from the client; --label "<option label>" and --option-of <versionId> add it as an option

brello studio status <id> <approve|changes|clear>

Set the internal review status; --note "<text>", --version-id <id>. The client's own verdict is never set here

brello studio plans ["<filter>"]

Creative Plans; --client "<name>", --status DRAFT|READY, --mine, --limit n

brello studio plan <id>

One plan in full and the fields you can change

brello studio plan <id> --set field=value

Change a plan: name, status, shootDate, shootLocation, shootDuration, clientBrief. --set repeats, e.g. --set name="Eid shoot" --set status=READY

brello studio clients ["<filter>"]

Studio clients with submission, plan and item counts; --all adds inactive clients

brello studio items <client id or name> ["<filter>"]

A client's items catalog; --plans adds items named on the client's plans

brello studio whoami

Your Studio account and the Studio permissions on your key

Reads work on every key. Comments, uploads, status changes and plan changes need the matching Studio permission on your key (post team comments, upload a new version, change the internal status, edit plans), which an admin grants when approving your brello auth request. Sending to a client, share links, client approval and delete stay in Studio.

brello studio with a filter (for example brello studio reel) is still the Roster review feed.

Claude gets the same through studio_whoami, studio_submissions, studio_submission, studio_comments, studio_comment, studio_upload, studio_status, studio_plans, studio_plan, studio_plan_edit, studio_clients and studio_client_items.

Limits

Surface

Limit

Self-service key

60 requests / minute + 5,000 / rolling day

Administrator-issued key

180 requests / minute

CLI and MCP share the same budget per key. Cards come from your team, or the whole board when your key has it. Write actions need individual approval, assignments stay within your team, and archive is unavailable. Self-service responses omit share/open URLs, invoice details and delivery recipients.

Each call returns a sensible page: search up to 50 cards, comments / reactions the latest 40.

Use it from Claude (MCP)

The global install also adds a brello-mcp command. Run brello auth first; Claude reuses that sign-in. Then ask in plain English ("what's overdue for my team?", "who's off next week?").

Claude Code

claude mcp add brello -- brello-mcp

Claude Desktop: add this to claude_desktop_config.json

{
  "mcpServers": {
    "brello": {
      "command": "brello-mcp"
    }
  }
}

No path and no key in the config. The server reads the key brello auth saved. Got a new key? Run brello auth again; Claude picks it up on the next question.

Keys

  • Anyone on the Bricks team can run brello auth and sign in with their Bricks Google account. An admin approves and picks your team or the whole board, the actions and the length, up to 90 days. Approved once: after that brello auth reconnects on its own until an admin revokes the key. Your terminal is connected by itself; nobody sees the key.

  • When a key runs out or has under 7 days left, run brello auth and it renews with the same access. Renew in My keys works too. Connecting a new terminal revokes the old key.

  • brello logout only removes the local copy. Revoke a lost key in My keys.

  • See, renew and revoke your keys at roster.bricks.com.kw/connect.

  • If a key expires, is paused, or hits the rate limit, brello tells you why and what to do next.

  • When the server has a heads up for you (for example, your key expires in a few days), the CLI prints it after your results and Claude sees it as a final Notice: line.

  • Old style keys are retired. If you still have one, run brello auth and sign in with Google.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    This server cannot be deployed

    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers