Brix Digital Signage
io.github.BenLoveittv1.0.0Updated Oct 1, 2026
Manage digital signage screens: health, content, casts, emergency messages, proof of play.
Overview
AI-generated overview
Lets an assistant manage digital signage screens, including health, content, casts, emergency messages, and proof of play.
- What it does
- This remote MCP server connects an assistant to a digital signage platform for screens. According to its description, it covers screen health, content, casts, emergency messages, and proof of play. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs to work with digital signage displays, for example checking screen status, handling content or casts, sending emergency messages, or reviewing proof-of-play records.
- Requirements
- It runs as a remote endpoint at over streamable HTTP. The manifest declares no authentication, no environment variables, and no headers, and no packages are listed. A Brix signage account may still be needed in practice, but the input does not state this.
Before you install
The manifest declares no authentication, so it is unclear how access is controlled or who can reach the endpoint. Emergency messages and content or cast changes can affect live displays, and proof-of-play data may be sensitive. Confirm the actual access controls and permissions before connecting.
Installation
In SourceWeft
- Open Brix Digital Signage in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"brix": {
"type": "http",
"url": "https://api.brixsignage.com/v1/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026

