The Brix digital signage connector for Claude
Brix is listed in Claude’s connector directory. Connect it once, sign in with your Brix account, and Claude can see your screens, change what they play, take a screenshot of any screen and tell you why one is offline. You type what you want in plain words. Claude does it with your own Brix permissions, and every change it makes is in your audit log.
- Where it works
- claude.ai, Claude Desktop and the Claude mobile apps. They share one list of connectors.
- How you connect
- From Claude’s connector directory. You sign in to Brix. You do not copy an API key.
- What Claude can reach
- The workspace you pick, an optional single location, and the permission areas you allow. Never more than your own access.
- Tools
- 15 tools: items of every kind, content on screens, takeovers, screen status, screenshots, device control, approvals, data refresh and fleet reports.
- Deletes
- Go to the Brix recycle bin for 30 days. A permanent delete needs a second call with a confirmation code.
- Price
- Included on every Brix plan: $6 per screen per month billed yearly, or $8 month to month. No extra charge for the connector.
Connect Brix to Claude in about two minutes
Open Brix in the connector directory
Open claude.ai/directory/connectors/brix. Or, in Claude, go to Customize > Connectors, click +, and search for Brix.
Click Connect
Claude opens a Brix sign-in page in a new window.
Sign in to Brix
Use the same login you use for the Brix CMS. No Brix account yet? Start a 7-day free trial first. A card is not necessary.
Pick the workspace and what Claude may do
Choose the workspace, a location if you want to limit Claude to one, and View only or View and change for each area (screens, playlists, schedules, media and more). Click Allow.
Ask Claude about your screens
Start a chat and ask, for example, “Which of my Brix screens are offline, and why?” Claude shows each tool call in the chat.
On a Claude Team or Enterprise plan, an owner first adds Brix under Organization settings > Connectors. Each member then connects it from Customize > Connectors and signs in with their own Brix account, so each person keeps their own Brix permissions.
Prefer Claude Code, Cursor or the Claude API? Use the endpoint https://api.brixsignage.com/v1/mcp with an API key.
Setup for each client is in the MCP developer docs.
Things you can ask Claude to do with your screens
Use the names you already use in Brix. Claude looks up the screen, playlist or location by name, so you never type an ID.
Check on your screens
Which of my screens are offline, and why?
Claude lists your screens and open alerts, then reads each offline screen’s likely cause and a checklist (list_items, get_screen_status).
Why is the lobby screen blank? Show me what it’s displaying right now.
Claude reads why the screen shows what it shows, then takes a new screenshot and puts it in the chat (get_screen_status, capture_screenshot).
Was the TV at the Main Street store switched off last week?
Claude reads the TV history: TV off, other input or cable lost, for up to 14 days. This view is for Amazon Signage Sticks (get_screen_status).
Change what plays
Put the Summer Menu playlist on every screen at the Downtown location.
Claude finds the playlist and the location, and sets it as the default content on every screen under that location. Screens change within seconds (set_screen_content).
Show “Closing at 4 pm today” on the store 12 screens until 4.
Claude starts a takeover over the normal content. It ends by itself at the time you give, and the screens go back to what they played before (start_takeover).
Add the new burger photo to the Lunch playlist, after the drinks slide.
Claude uploads the file you attach or copies it from a link, then edits the playlist. Every screen that plays the playlist follows (create_items, update_items).
Fix a problem
The bar screen still shows yesterday’s specials. Refresh it.
Claude sends a refresh, then checks the result with a screenshot. It can also reboot, clear the cache, or turn an HDMI-CEC TV on or off (control_screens, capture_screenshot).
Prices changed in our Google Sheet. Update the menu boards now.
Claude syncs the data feed now instead of at the next scheduled refresh (refresh_data).
Get reports
Give me this month’s uptime report, worst screens first.
Claude reads online time per screen, each outage with its cause, and short insights (get_fleet_report).
How many times did the Burger Promo play last week, and on which screens?
Claude reads proof of play: plays, watch time, skips and failures per item, and where (get_fleet_report).
Who changed the lobby playlist yesterday?
Claude reads the audit log, newest first, by name (get_fleet_report).
Brix also gives Claude four ready-made prompts: a daily fleet health report, a guided check of one offline screen, setting up a new location, and a weekly content review.
The 15 tools Claude gets
The same tools work for every kind of item, so Claude learns one pattern: find it, read it, change it.
| Tool | What Claude uses it for |
|---|---|
list_items | Find items of one kind by name: screens, media, playlists, schedules, layouts, designs, apps, data feeds, screen groups, locations, folders, emergency templates, alerts, approvals and people. |
get_items | Read items in full before Claude changes them. |
create_items | Add items: upload files, copy files from a link, pair a screen by its code, or invite a person. |
update_items | Rename, move or edit items, one or many at once: playlist items, schedule blocks, screen settings and groups. |
delete_items | Move items to the 30-day recycle bin. |
restore_items | Bring deleted items back from the recycle bin. |
set_screen_content | Set what screens play by default: a playlist, schedule, app or file. |
start_takeover | Show content or a message over the normal content for a set time, or start a prepared emergency. |
end_takeover | End a takeover or emergency on every screen it covers, in one call. |
get_screen_status | Explain one screen: why it shows what it shows, likely cause and checklist, outages, and TV history. |
capture_screenshot | Take a new screenshot of one screen and show it in the chat. |
control_screens | Refresh, reboot, clear the cache, or turn an HDMI-CEC TV on or off. |
review_approval | Approve, reject or withdraw a waiting approval request. |
refresh_data | Sync a data feed or re-render a web page now. |
get_fleet_report | Uptime with outage causes, proof of play, or the audit log. |
Arguments, permissions and examples for each tool: MCP tool catalog.
You decide what Claude can touch
Claude acts as you, with less if you choose
The connection uses your Brix permissions and only the areas you allowed at sign-in. Claude cannot do anything you cannot do. Pick View only for a first try: Claude can answer questions but cannot change what plays.
Some things stay with a person
A connection made by signing in cannot use billing, payments, invoices, API keys or single sign-on. Claude can see people and roles and invite a person, but only with a role that does not manage people, roles, keys, settings or billing.
Deletes can be undone for 30 days
A delete moves items to the recycle bin, and Claude can restore them. A permanent delete takes two calls: the first shows what would be erased and returns a code, and the second must carry that code.
Approval rules still apply
Where a location needs approval, content Claude creates waits as a draft for your approvers, the same as content a person makes in the CMS.
Every change is on the record
Changes Claude makes are written to the workspace audit log under your name, the same as changes you make in the CMS.
Revoke at any time
Every connection is listed in the CMS under Settings > AI, API & MCP > Connected apps, with who connected it and when it was last used. Revoke ends it at once.
Brix receives only the tool calls Claude makes, not your chat, and does not use that data to train AI models. More in the privacy policy and on the security page.
Brix and Claude: common questions
Can Claude manage digital signage?
Yes, with a connector. Brix is a digital signage platform with a connector in Claude’s directory. After you connect it, Claude can list your screens, change what they play, start and end takeovers, take screenshots, restart players and read uptime, proof-of-play and audit reports.
How do I add the Brix connector to Claude?
Open claude.ai/directory/connectors/brix, or go to Customize > Connectors in Claude, click + and search for Brix. Click Connect, sign in to Brix, pick the workspace and what Claude may do, then click Allow.
Do I need an API key?
No. The connector uses sign-in (OAuth), so you do not copy a key. Developer tools such as Claude Code and Cursor can use an API key instead. See the MCP developer docs.
Does the connector work in Claude Desktop and on my phone?
Yes. claude.ai, Claude Desktop and the Claude mobile apps share one list of connectors, so you connect Brix once. On a Claude Team or Enterprise plan, an owner must add Brix for the organization first.
Does the connector cost extra?
No. The connector is included on every Brix plan: $6 per screen per month billed yearly, or $8 per screen month to month. Brix has a 7-day free trial and no card is necessary.
Can Claude change my screens without asking me?
Every Brix tool tells Claude whether it only reads or changes something, and Claude uses that to decide when to ask you first. Each tool call shows in the chat, and you can set each tool’s permission in Claude’s connector settings. To stop all changes, connect with View only.
Can I limit Claude to one location?
Yes. At sign-in, pick a location. Claude then sees and changes only the screens and content at and under that location.
Does Brix see my conversations with Claude?
No. Brix receives only the tool calls Claude makes, not the chat. Brix does not use data reached through connected apps to train AI models.
What screens does Brix run on?
The Amazon Signage Stick, Android TV and Google TV boxes such as the Walmart Onn, Fire TV, TVs with Google TV or Android TV built in, and Windows PCs. The connector works the same on all of them.
Does Brix work with ChatGPT and other AI tools too?
Yes. The same MCP server works in ChatGPT (Developer mode), Claude Code, Cursor, the Claude API and the OpenAI Responses API. Setup for each is in the MCP developer docs.
- Comparing signage platforms that work with AI assistants? Read Control digital signage from Claude or ChatGPT.
- Running screens on Amazon hardware? See Brix on the Amazon Signage Stick.
- Writing code instead? Start at the Brix developer docs.
- News: The Brix connector for Claude now has 15 tools.