Blender integration through the Model Context Protocol
Screenbird is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Manage Screenbird digital signage screens: see what is live, show content, create designs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http screenbird-mcp https://mcp.screenbird.app/mcp
# 2 — ask your agent for something these tools do
# list_screens, search_content, push_content and 9 more
Screenbird costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http screenbird-mcp https://mcp.screenbird.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the connected team's screens: online status and what each screen and sub-screen shows right now (its normal content, pushed content, a scene or screen mirroring), with the end time if there is one. Also returns the account's time zone and current local time. Filter with query (part of a screen or sub-screen name) or screen_id. Results come in pages: pass next_cursor as cursor for the next pag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of a screen or sub-screen name. |
| screen_id | string | no | One screen. |
| limit | integer | no | Screens per page. Default 25. |
| cursor | string | no | next_cursor from the previous page. |
Search the team's content that can be shown on a screen: files, designs, apps, split screens and playlists. Newest first. Returns the id, name and type of each item.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of the name. Leave empty to list recent content. |
| type | string | no | — |
| limit | integer | no | Default 20. |
Show content on one screen, or on one sub-screen of a split screen, in place of what it shows now, until a time or until it is put back to normal. A split screen needs a subscreen_id. Returns what the screen shows afterwards. Content only appears once the screen is online and has a player paired; the result includes online and paired when the connection may read screens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| screen_id | string | yes | — |
| content_id | string | yes | — |
| subscreen_id | string | no | — |
| until | string | no | When to go back to normal: local time of the account without an offset (for example 2026-10-23T18:00), or a time with an offset (2026-10-23T18:00:00+02:00). At most 90 days ahead. Leave out to show it |
End pushed content or a scene on one screen or sub-screen; it goes back to its own content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| screen_id | string | yes | — |
| subscreen_id | string | no | — |
List the team's scenes in their order, with their state (live, partly live, changed since it went live, off) and which screens and sub-screens each scene sets (at most 20 targets per scene; targets_total is the real number). Results come in pages: pass next_cursor as cursor for the next page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Scenes per page. Default 25. |
| cursor | string | no | next_cursor from the previous page. |
Put a scene live: every screen and sub-screen in the scene switches at once, in place of what it shows. Running it again puts changes to the scene live. A screen only shows the scene once it is online and has a player paired; each result includes online and paired when the connection may read screens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scene_id | string | yes | — |
End one scene: its screens go back to their own content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scene_id | string | yes | — |
End all scenes and all pushed content on the team's screens. Screen mirroring keeps running.
No parameter schema on file.
Create a design (a full-screen slide for a screen, such as a menu, an announcement or an event poster) from a description. It picks a fitting template, fills in the text and adds stock photos where the template has them; no images are generated with AI. The design is saved in the team's files and can be shown on a screen or used in a scene. Each design uses the account's AI budget, with at most 20
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | What the design must show, in the user's words, with all texts, prices, times and names to put on it. |
| orientation | string | no | Screen orientation. Default landscape. |
| name | string | no | Name of the design in Screenbird. Optional. |
| language | string | no | Two-letter language code of the texts on the design (en, nl, de, ...). |
Search the Screenbird help center (how features work, setup, troubleshooting). Returns up to 3 articles with title, summary and link; set full to true for the complete text of each article.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the user wants to know, in their own words. |
| language | string | no | Two-letter language code of the user (en, nl, de, fr, ...). Articles come in that language. |
| full | boolean | no | Return the complete article text. Default false. |
Steps to install the Screenbird player on a device type, ending with the pairing code that the user enters in the dashboard.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | yes | — |
Check whether a device (as the user names it, for example "Samsung TV", "Chromecast", "iPad") works with Screenbird. Returns works, coming_soon, does_not_work, works_in_browser or unknown, with an explanation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Screenbird or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_screens | no tags | |
| search_content | no tags | |
| push_content | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| release_screen | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_scenes | no tags | |
| activate_scene | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| release_scene | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| release_all | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_design | state-write | state-write: declares readOnlyHint: false |
| search_help | no tags | |
| get_install_steps | no tags | |
| check_device | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Screenbird can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.