Roster
Queries the Bricks Studio review feed, providing status/version, comments, client views, and open/share links for design reviews.
Displays Salesforce fields linked to cards, such as account or deal information, within card details.
Shows Slack thread information associated with cards, allowing users to access relevant conversations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rostershow me team stats"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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: 2Install
npm install -g brello
brello auth
brello statsbrello auth asks for your key at a masked prompt, checks it, and saves it to
~/.roster (only your user can read it), until you renew or replace the key. Run brello auth again with the replacement.
Need a key? Get one at roster.bricks.com.kw/connect (by invitation). Already copied it?
pbpaste | brello loginsigns in straight from the clipboard. The command isbrello(typingrosterworks too).
git clone https://github.com/brickshubkuwait/roster-cli-mcp.git
cd roster-cli-mcp && npm install && npm link
brello authRelated 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 keysClaude can use the roster_docs tool for the same links and key guidance, without an API call.
CLI
Command | What it shows |
| Team dashboard — size, open / done / overdue, who's tracking |
| Your team members |
| Cards past their due date and not done |
| Open + overdue cards per person |
| Who's tracking time right now (live Hubstaff) |
| Recent comments on your team's cards |
| Recent emoji reactions on your team's cards |
| Card history — moves (stage→stage), comments, splits, edits |
| Find cards by title or client |
| Everything for one person — every card, live AND archived, with their open/done/archived totals + what they're tracking now |
| Every field on a card — workflow, Studio, Salesforce, send/view receipt, Slack thread, sizes and copy |
| Bricks Studio review feed — status/version, comments, client views, and open/share links |
| Everything for one client — every in-scope card (live + done), who's on it, with open/done/overdue totals |
| One client in one month: what the contract sold vs what was shot, delivered and approved, per contract, plus special requests. |
| Cards due soon — the next N days (default 7), soonest first |
| Recently completed cards — the last N days (default 14) |
| Blocked or stuck cards — explicit blockers, or overdue by 3+ days |
| Recently touched cards across your team (default 20) |
| Live pulse — who's tracking now, what's due today, and the latest card moves |
| Board stages with your team's open card count in each |
| The roster's departments and headcount |
| Every card in a stage or matching filters; |
| Stage usage over the board's history; |
| The company-wide shoot schedule; |
| Meetings with owner, attendees and minutes status; |
| Client directory with Instagram handle, logo and open cards; |
| 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 --jsonWith --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).
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. Self-service card access stays with your team, even with --board. 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-mcpClaude 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 authsaved. Got a new key? Runbrello authagain; Claude picks it up on the next question.
Keys
Self-service keys are invitation-only and last 30 days. An approval can be claimed for 24 hours, with a sign-in within the last 10 minutes. The key is shown once.
Renew in My keys when eligible. Revealing the renewal replaces and revokes the old key. Run
brello authon each device using it.brello logoutonly removes the local copy. Revoke a lost key in My keys.Keys come from roster.bricks.com.kw/connect. Renew or replace them there.
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, get a new key at the link above and run
brello auth.
This server cannot be deployed
Maintenance
Related MCP Connectors
Query your org's data in natural language — read-only MCP access to SQL, NoSQL, files & warehouses.
Ask your organization's connected business data in plain language, with each person's permissions.
Ask your databases questions in plain English, run read-only SQL and set up data alerts.
Ask data questions in natural language. Get SQL, insights, and charts from your databases.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides read-only issue and project management tools for Jira Server/DC, enabling querying issues, projects, and assignments via natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables querying your spreadsheet using natural language questions; provides read-only tools for schema, sample data, and structured query execution with auditable computation traces.MIT
- AlicenseBqualityDmaintenanceEnables natural-language investigation of Datadog data including logs, metrics, monitors, traces, hosts, dashboards, events, and incidents, all through read-only API access.141,463 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to VortexIQ ecommerce AI data, including store audits, KPIs, alerts, brand DNA, and reports, through natural language queries.MIT