MCP serverapp.dailystudio/teleprompter
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
Overview
Score?
UNRATED 0.824
of what a free look can see, on 32 looks
Looks
36
last 13 hr ago
Tools
12
changed 1 day ago
More info
URL
dailystudio.app/mcp
streamable-http
Says it is
safevertical 1.0.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.824 · highest on record 0.8561
Toolsfrom sha256:53302911e4…9f929f · +0 −0 1 day ago
| Tool | Schema |
|---|---|
| add_scripts_to_plan Put finished 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 tha |
input · no output |
| archive_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 th |
input · no output |
| cancel_scheduled_post 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 bef |
input · no output |
| edit_planned_scripts 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 f |
input · no output |
| get_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 as |
input · no output |
| list_collections 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-d |
input · no output |
| list_connected_accounts 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 — th |
input · no output |
| list_planned_scripts 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 (writt |
input · no output |
| list_scheduled_posts 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. Cal |
input · no output |
| reorder_planned_scripts 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 th |
input · no output |
| retry_scheduled_post 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 goe |
input · no output |
| send_script_to_teleprompter 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 saf |
input · no output |
Verify it yourself
npx teppi-check https://dailystudio.app/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ23HB3QBRK2BXKJ0CZKA7