# Daily Studio Teleprompter Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Daily Studio Teleprompter

Send video scripts to your iPhone teleprompter and manage your content plan in one place.

- Record: https://musedirectory.ai/connector/daily-studio-teleprompter
- Category: Marketing & Ads
- Developer: Daily Studio (https://dailystudio.app)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 95ms, checked 2026-09-28T09:16:02Z
- Endpoint: https://dailystudio.app/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T07:50:49Z)
- Source: Found in the official MCP Registry (app.dailystudio/teleprompter) https://registry.modelcontextprotocol.io/v0/servers?search=app.dailystudio%2Fteleprompter

Connects to Daily Studio to turn finished video scripts into one-tap links that load into the teleprompter app with platform-specific safe zones. Manage content plans, batch scripts for back-to-back recording, and track publishing status across social accounts.

Example request: "Send me three scripts I wrote today to my teleprompter so I can record them all in one session."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Daily Studio Teleprompter to help me. It is a free service with an MCP server at https://dailystudio.app/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 `text`; for a batch the user will record back-
- 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 one, and the call is retried automatically 
- 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 than to hand them something to record right now. The plan lives on their account: it shows up in the ap
- 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). Call this before adding to a plan so you d
- 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' when the content already exists — read the p
- 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 call.
- 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 deletion is deliberately not available to a
- 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 that should be recorded in sequence.
- 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 not?'. Nothing is changed by this tool, and ne
- 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.

Screening checks:
- MCP handshake: pass (Answered in 104ms)
- Domain against threat feeds (Cloudflare security DNS): pass (dailystudio.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (12 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)