io.github.8beeeaaat/touchdesigner-mcp-server vs Brix Digital Signage
Brix Digital Signage is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
io.github.8beeeaaat/touchdesigner-mcp-server is an MCP server published by 8beeeaaat. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Brix Digital Signage is an MCP server published by BenLoveitt. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (npm): 6 469 Downloads/week (npm): 536 Forks (GitHub): 65 Stars (GitHub): 597 Not marked · First seen |
Removed on 2026-10-16 Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.8beeeaaat/touchdesigner-mcp-server | Brix Digital Signageno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 2 | 0 |
| Stars (GitHub) (differs) | 597 | No figure on GitHub |
| Forks (GitHub) (differs) | 65 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (touchdesigner-mcp-server) | Remote server (api.brixsignage.com/v1/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/8beeeaaat/touchdesigner-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Brix Digital Signage
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Manage digital signage screens: health, content, casts, emergency messages, proof of play.
-
Control CastHub digital signage. Manage TVs, presentations, schedules, and emergency alerts.
-
Manage digital signage screens, playlists and media from your AI assistant.
-
Manage screenRIG screens, playlists, media, schedules, webhooks, and reports through MCP.
-
Deploy sims to any screen. Control your displays with Claude.
-
cli io.github.pushtodisplay/cli
PushToDisplay MCP server — send real-time updates to display boards on iOS and Android devices.
What each says it does
io.github.8beeeaaat/touchdesigner-mcp-server
MCP server for TouchDesigner - Control and operate TouchDesigner projects through AI agents
Brix Digital Signage
Manage digital signage screens: health, content, casts, emergency messages, proof of play.
How to run each
io.github.8beeeaaat/touchdesigner-mcp-server As a local MCP server: npm package
claude mcp add --transport stdio touchdesigner-mcp-server -- npx -y touchdesigner-mcp-server
Brix Digital Signage
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.8beeeaaat/touchdesigner-mcp-server · What it can do: Brix Digital Signage · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.