Daily Studio Teleprompter MCP Server

by dailystudio Your server? Claim it

answering

Daily Studio Teleprompter is answering right now. Last checked 13 min ago. It exposes 12 tools.

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

Uptime history 44 days of history · worst day 95%

44 days agonow

93.4%

Uptime 24h

85 of 91 checks

Tools

read from the server

144 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 August 2026. No other catalogue keeps this.

20 Aug 8 tools appeared archive_planned_scripts, cancel_scheduled_post, edit_planned_scripts and 5 more

20 Aug 2 tools changed the parameters they ask for3 times that day add_scripts_to_plan, list_planned_scripts

20 Aug a tool description was rewritten list_planned_scripts

19 Aug 2 tools appeared add_scripts_to_plan, list_planned_scripts

and 1 more, back to 19 August 2026

Daily Studio Teleprompter does not always answer

Over the last week it answered 97.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "teleprompter": {
      "url": "https://dailystudio.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.teleprompter]
url = "https://dailystudio.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "teleprompter": {
      "url": "https://dailystudio.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "teleprompter": {
      "url": "https://dailystudio.app/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

planned

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.

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

archive

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 assistants — the user does that themselves.

cancel

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.

collections

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.

connected

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

edit

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

reorder

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.

retry

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.

scheduled

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 new posts cannot be scheduled from here.

scripts

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

send

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

Endpoints

URL	Transport	State	Latency	Checked
https://dailystudio.app/mcp	streamable-http	answering	161 ms	13 min ago

Alternatives to Daily Studio Teleprompter

same job, measured the same way

Teleprompter

by teleprompter

Read and write your Teleprompter.com scripts and folders: list, create, update, and organize.

answering

ScriptSeen

by yesmars

Create short-form scripts and paced audio, then hand clips to ScriptSeen's on-device video maker.

answering

Orquesta

by getorquesta

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

answering

The Scribble Thing

by boringstuff

Turn one line-art image into a prompt-directed, hand-drawn scribe animation MP4.

6 tools answering

Scribble — Real Handwritten Cards

by scribblecards

Send real handwritten cards in the US. A machine writes each one in ink, then we mail it.

answering

Har Forensics MCP

by aryanspv

Tells you what leaked in a .har capture, who's on the page, and what to strip. No network calls.

44 installs/wk local only

Anythink all-in-one backend: data, auth, files, workflows, payments, APIs

by anythink

Sick of stitched-together services? Anythink is the all-in-one backend, configured with AI.

local only

iOS Web Bluetooth (WebBLE)

by wklm

MCP server to ship Web Bluetooth on iPhone Safari via the WebBLE extension.

27 installs/wk local only

Daily Studio Teleprompter — questions

Answers built from our own checks of this server.

What can Daily Studio Teleprompter do?

It exposes 12 tools, read directly from the server on our last check. Among them: add_scripts_to_plan, archive_planned_scripts, cancel_scheduled_post, edit_planned_scripts, get_planned_scripts, list_collections and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Daily Studio Teleprompter working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 91 checks got a reply (93.4%), average response time 144 ms. The bar chart above shows every period we have measured.

How do I connect Daily Studio Teleprompter?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Daily Studio Teleprompter need an API key?

No. Daily Studio Teleprompter completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Daily Studio Teleprompter?

It answers our handshake in 144 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.