Daily Studio Teleprompter MCP server

• add_scripts_to_planwrite actionFree

  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 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 are skipped. Requires a connected Daily Studio account with the plan turned on. To record something immediately, use `send_script_to_teleprompter` instead — that is a delivery, this is a plan.

• archive_planned_scriptsFree

  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.

• cancel_scheduled_postwrite actionFree

  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.

• edit_planned_scriptsFree

  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 entry never drops the batch.

• get_planned_scriptsFree

  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.

• list_collectionsFree

  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_connected_accountsFree

  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.

• list_planned_scriptsFree

  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. Nothing is changed by this tool.

• list_scheduled_postsFree

  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.

• reorder_planned_scriptsFree

  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.

• retry_scheduled_postwrite actionFree

  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.

• send_script_to_teleprompterwrite actionFree

  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 order, and ONE link carries them all. Call this only once the scripts are final. Returns a link the user taps on their iPhone; on a desktop it opens a page with a QR code to scan.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 319ms20/20
• Tool poisoning12 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 4 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Daily Studio Teleprompter: common questions

Is Daily Studio Teleprompter MCP server safe?

With care: it is graded C, so read the findings first (60/100). Read the Daily Studio Teleprompter safety report

How do I install Daily Studio Teleprompter?

It runs remotely at dailystudio.app. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Daily Studio Teleprompter need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Daily Studio Teleprompter maintained?

The latest release is v1.0.0.

Is Daily Studio Teleprompter up?

100% of our last 20 checks got an answer. We check remote servers about four times a day.

What can I use instead of Daily Studio Teleprompter?

Servers from other publishers that do the same job: Music Studio MCP server.