Daily Studio Teleprompter

by dailystudio.app · remote · no sign-in to list tools · v1.0.0 · published by app.dailystudio

Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.

Deletes · 2Final · 1Changes · 4

Compare Registry entry

12 tools: 2 can delete or cancel things, 1 do something that can't be undone, 4 change things and 5 only read.

Scanned Oct 21, 2026

Deletes or cancels2Claude Code: deny: see these tools
Can't be undone1Claude Code: ask: see these tools
Changes things4Claude Code: ask: see these tools
Only reads5Claude Code: allow: see these tools

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http teleprompter https://dailystudio.app/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warnarchive_planned_scripts
The server marks "archive_planned_scripts" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
Matched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "archive_planned_scripts" says "archive": a word for removing or ending something.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

12 tools

Deletes or cancels 2Removes, cancels or revokes something.Claude Code: deny

archive_planned_scriptsArchive scripts out of the user's working plan, by id — or restore archived ones with `restore: true`.1 finding
Why it is in this group
- The name "archive_planned_scripts" says "archive": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
  The server marks "archive_planned_scripts" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
  Matched text
  annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "archive_planned_scripts" says "archive": a word for removing or ending something.
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
cancel_scheduled_postCancel one post that is waiting to go out, by id from list_scheduled_posts.No findings
Why it is in this group
- The name "cancel_scheduled_post" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

send_script_to_teleprompterTurn 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…No findings
Why it is in this group
- The name "send_script_to_teleprompter" says "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

Changes things 4Creates or changes something that can be changed back.Claude Code: ask

add_scripts_to_planPut finished talking-head scripts into the user's Daily Studio content plan, each with the day it should go out.No findings
Why it is in this group
- The name "add_scripts_to_plan" says "add": a word for a change.
Description, as the server wrote it
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 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. Default to about 45 seconds of natural speech directly to camera: a hook, one clear idea and a short closing. Preserve the creator's voice and verified facts.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
edit_planned_scriptsChange 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.No findings
Why it is in this group
- The name "edit_planned_scripts" says "edit": a word for a change.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
reorder_planned_scriptsSet the order the user's camera walks through their scripts — pass ids first-to-record first.No findings
Why it is in this group
- The description's first verb is "set": a word for a change.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
retry_scheduled_postPut one failed post back in the queue, due now — by id from list_scheduled_posts.No findings
Why it is in this group
- The name "retry_scheduled_post" says "post": a word for a change.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 5Looks things up and changes nothing.Claude Code: allow

get_planned_scriptsRead the full text of specific scripts in the user's content plan, by id — the words themselves, not just titles.No findings
Why it is in this group
- The name "get_planned_scripts" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_collectionsList the collections (piles) the user already groups their scripts into, with counts.No findings
Why it is in this group
- The name "list_collections" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_connected_accountsList the social accounts the user has connected to Daily Studio, so you know where a video could be published and under which handle.No findings
Why it is in this group
- The name "list_connected_accounts" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_planned_scriptsRead 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…No findings
Why it is in this group
- The name "list_planned_scripts" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_scheduled_postsRead 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.No findings
Why it is in this group
- The name "list_scheduled_posts" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http teleprompter https://dailystudio.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__teleprompter__list_connected_accounts",
      "mcp__teleprompter__list_planned_scripts",
      "mcp__teleprompter__get_planned_scripts",
      "mcp__teleprompter__list_collections",
      "mcp__teleprompter__list_scheduled_posts"
    ],
    "ask": [
      "mcp__teleprompter__send_script_to_teleprompter",
      "mcp__teleprompter__add_scripts_to_plan",
      "mcp__teleprompter__edit_planned_scripts",
      "mcp__teleprompter__reorder_planned_scripts",
      "mcp__teleprompter__retry_scheduled_post"
    ],
    "deny": [
      "mcp__teleprompter__archive_planned_scripts",
      "mcp__teleprompter__cancel_scheduled_post"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as teleprompter. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/app.dailystudio/teleprompter/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

For agents: Markdown · JSON · report this listing