Blender integration through the Model Context Protocol
Nothing to run from here
Daily Studio Teleprompter 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.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http daily-studio-teleprompter-mcp https://dailystudio.app/mcp
# 2 — ask your agent for something these tools do
# send_script_to_teleprompter, list_connected_accounts, add_scripts_to_plan and 9 more
Daily Studio Teleprompter costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
dailystudio1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 daily-studio-teleprompter-mcp https://dailystudio.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
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.
Turn one or more finished video scripts into a single one-tap link that opens the user's Daily Studio app with the script(s) loaded into the teleprompter and the right platform safe-zones selected, ready to record. For one script use text; for a batch the user will record back-to-back (a day's 3-4 videos, or a whole content plan — up to 100), use scripts — they land as an in-app shoot queue in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | A finished talking-head script to speak directly to camera, plain UTF-8. Newlines allowed. Provide either this or scripts, not both. |
| title | string | no | Optional short label for text, e.g. 'Cold plunge hook'. |
| wpm | integer | no | Optional scroll speed in words per minute. Sets the app's teleprompter speed. Omit to leave the user's setting alone. With scripts, applies to items that don't set their own. |
| platform | string | no | Where the video will be published. Selects that platform's safe-zone overlay so on-screen UI never covers the creator. Omit to leave the user's choice alone. With scripts, applies to items that don' |
| scripts | array | no | A batch of scripts (in recording order) delivered as a single link — up to 100 of them, 400000 characters of script in total. The app queues them; after each recording it offers the next. Provide eith |
List the social accounts the user has connected to Daily Studio, so you know where a video could be published and under which handle. Requires a connected Daily Studio account — the first time you call this, the user is asked to connect one, and the call is retried automatically afterwards. Nothing is published by this tool.
No parameter schema on file.
Put finished talking-head scripts into the user's Daily Studio content plan, each with the day it should go out. Use this when the user asks you to PLAN — a week, a month, a series — rather than to hand them something to record right now. The plan lives on their account: it shows up in the app, on dailystudio.app/plan, and stays there. Calling this twice with the same scripts is safe; duplicates a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | no | Optional name for this batch as a group — a topic ('Customer questions'), a series ('Framing, part 1-5'), or what the week is about. The scripts show up grouped under it in the app and on the web, whi |
| scripts | array | yes | The scripts to add, in the order they should sit in the plan. |
Read what is already in the user's Daily Studio content plan — each script's id, title, collection, the day it goes out, its place in the shoot order, and how far it has got (written, recorded, uploaded, scheduled, published, or failed). Call this before adding to a plan so you do not repeat what is there, before editing so you hold real ids, and whenever the user asks what they have coming up. No
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Only scripts dated on or after this day. |
| to | string | no | Only scripts dated on or before this day. |
| includeUndated | boolean | no | Include scripts with no date at all (the backlog). Default true. |
| collection | string | no | Only scripts in this collection. Omit to read the whole plan. |
Change scripts already in the user's Daily Studio content plan, by id and in bulk: move them to other days, group them into collections, retitle or rewrite them. This is the tool for 'these contents go on these days, grouped like this' when the content already exists — read the plan first with list_planned_scripts, then send one call with all the changes. Only the fields you send change; one bad e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| edits | array | yes | The changes, one entry per script. Only the fields you send change; everything else stays. Get ids from list_planned_scripts. |
Read the full text of specific scripts in the user's content plan, by id — the words themselves, not just titles. Use it before rewriting or reviewing a script, or when the user asks about one ('check the hook on Tuesday's'). Up to 20 per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | The scripts to read in full, at most 20 per call. Ids come from list_planned_scripts. |
Archive scripts out of the user's working plan, by id — or restore archived ones with restore: true. Archiving is reversible and keeps the script and any recorded video; it is the right way to clear finished or shelved work. Permanent deletion is deliberately not available to assistants — the user does that themselves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | The scripts to archive (or restore). Ids come from list_planned_scripts. |
| restore | boolean | no | true brings archived scripts back into the plan instead. Default false. |
Set the order the user's camera walks through their scripts — pass ids first-to-record first. Scripts you leave out keep their current order after the ones you name. Use it when the user says what to shoot first, or after planning a batch that should be recorded in sequence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Script ids in the order they should be recorded, first first. Scripts you leave out keep their current order, after the ones you name. |
List the collections (piles) the user already groups their scripts into, with counts. Call it before grouping anything so you reuse their existing names instead of inventing near-duplicates.
No parameter schema on file.
Read what the user has approved for publishing and what happened to it: waiting, going up now, published (with the link), failed (with the reason in plain words), or cancelled. Call it when the user asks 'did my post go out?' or 'why not?'. Nothing is changed by this tool, and new posts cannot be scheduled from here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Only posts in this state. Omit for the whole queue, newest first. |
Cancel one post that is waiting to go out, by id from list_scheduled_posts. Only works while the post is still waiting; the take becomes approvable again. Confirm with the user before calling this — it withdraws something they approved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The post's id, from list_scheduled_posts. |
Put one failed post back in the queue, due now — by id from list_scheduled_posts. Use it after the cause in the failure sentence is fixed (say, a reconnected account). The post goes out within about five minutes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The post's id, from list_scheduled_posts. |
Free
$0 forever
- 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 Daily Studio Teleprompter or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Daily Studio Teleprompter can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.