Daily Studio Teleprompter is an MCP server with 12 tools an agent can call, among them add_scripts_to_plan, archive_planned_scripts, cancel_scheduled_post. It answers at https://dailystudio.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: collection, scripts |
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 del Inputs: ids, restore |
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. Inputs: id |
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 Inputs: edits |
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 c Inputs: ids |
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_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 |
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). Ca Inputs: from, to, includeUndated, collection |
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?'. Inputs: state |
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 t Inputs: ids |
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. Inputs: id |
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` Inputs: text, title, wpm, platform, scripts |
Every block below points at https://dailystudio.app/mcp. Pick your client and copy.
claude mcp add --transport http daily-studio-teleprompter https://dailystudio.app/mcp
{
"mcpServers": {
"daily-studio-teleprompter": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://dailystudio.app/mcp"]
}
}
}{
"mcpServers": {
"daily-studio-teleprompter": {
"url": "https://dailystudio.app/mcp"
}
}
}{
"servers": {
"daily-studio-teleprompter": {
"type": "http",
"url": "https://dailystudio.app/mcp"
}
}
}{
"context_servers": {
"daily-studio-teleprompter": {
"url": "https://dailystudio.app/mcp"
}
}
}{
"mcpServers": {
"daily-studio-teleprompter": {
"serverUrl": "https://dailystudio.app/mcp"
}
}
}{
"mcpServers": {
"daily-studio-teleprompter": {
"url": "https://dailystudio.app/mcp"
}
}
}name: Daily Studio Teleprompter
version: 0.0.1
schema: v1
mcpServers:
- name: Daily Studio Teleprompter
type: streamable-http
url: https://dailystudio.app/mcp{
"mcpServers": {
"daily-studio-teleprompter": {
"httpUrl": "https://dailystudio.app/mcp"
}
}
}{
"mcpServers": {
"daily-studio-teleprompter": {
"type": "http",
"url": "https://dailystudio.app/mcp"
}
}
}{
"mcpServers": {
"daily-studio-teleprompter": {
"url": "https://dailystudio.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdailystudio.app%2Fmcp&type=streamable_http&id=daily-studio-teleprompter&name=Daily%20Studio%20Teleprompter
It answered our last check on 17 October 2026 in 256 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by dailystudio.app and served from dailystudio.app, the vendor's own domain: https://dailystudio.app/mcp.
12, as returned by the server's own tools/list on 9 September 2026: add_scripts_to_plan, archive_planned_scripts, cancel_scheduled_post, edit_planned_scripts, get_planned_scripts, list_collections, list_connected_accounts, list_planned_scripts, and 4 more.
It answered our last check on 17 October 2026 in 256 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://dailystudio.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.dailystudio. Endpoint host: dailystudio.app. ARD identifier: urn:air:app.dailystudio:mcp:teleprompter.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.