Daily Studio MCP server

• Registry nameapp.dailystudio/teleprompterverified in the MCP registry

The registry name sits under dailystudio.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-13
• Tools12
• Server calls itselfsafevertical
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 19 ms.

• 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 safe-zones selected, ready to record. For one script use…

• 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 — the first time you call this, the user is asked to connect…

• add_scripts_to_plan

  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…

• 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 (written, recorded, uploaded, scheduled, published, or failed)…

• 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 for 'these contents go on these days, grouped like this'…

• 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 asks about one ('check the hook on Tuesday's'). Up to 20 per…

• 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 the right way to clear finished or shelved work. Permanent…

• 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 the user says what to shoot first, or after planning a batch…

• 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-duplicates.

• 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. Call it when the user asks 'did my post go out?' or 'why…

• 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 before calling this — it withdraws something they approved.

• 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 goes out within about five minutes.