Other · Remote MCP server
Brix Digital Signage
Manage digital signage screens: health, content, casts, emergency messages, proof of play.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.BenLoveitt/brix- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- BenLoveitt (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/BenLoveitt) · how
- Website
- brixsignage.com/developers/mcp/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.brixsignage.com/v1/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Brix Digital Signage
Brix Digital Signage is a remote MCP server: there is nothing to install. Its endpoint is https://api.brixsignage.com/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Brightspace D2l MCPD2L Brightspace for AI agents: due dates with submission status, grades and course content. | Local · stdio |
| Brilliant Directories MCPOfficial MCP server for Brilliant Directories - manage members, posts, leads, reviews, and more. | Local · stdio |
| Bristlecone LogicMicro-settled web content extraction and JSON schema validation utilities for AI agents via XRPL. | Local · stdio |
| Brivvy MCPBrivvy MCP (OAuth): on-brand AI content, voice rules, templates, glossary. | Remote · HTTPLive check: sign-in required |
| Brixa StudioYour design, automated endlessly. Design anywhere, Brixa freezes it as a template, publishes forever. | Remote · HTTPLive check: sign-in required |
| Brotato CoachDeterministic Brotato theorycrafter MCP server: facts and math, not guesses. | Local · stdio |
| BrowsenticHands your real, logged-in browser to your agent: an AI side panel extension, also over MCP. | Local · stdio |
| Browser Devtools MCPPlaywright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions. | Remote & Local · HTTP, stdio |