INDIVIDUAL MCP TOOL

get_planned_scripts

Read the full text of specific scripts in the user's content plan, by id — the words themselves, not just titles.

dailystudio.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://dailystudio.app/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_planned_scripts and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.safevertical]
url = "https://dailystudio.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "safevertical": {
      "type": "http",
      "url": "https://dailystudio.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: safevertical
Remote MCP URL: https://dailystudio.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "safevertical": {
      "type": "http",
      "url": "https://dailystudio.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "safevertical",
  "transport": "streamable-http",
  "url": "https://dailystudio.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

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.
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.
add_scripts_to_plan — Put finished scripts into the user's Daily Studio content plan, each with the day it should go out.
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).
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.
archive_planned_scripts — Archive scripts out of the user's working plan, by id — or restore archived ones with `restore: true`.
reorder_planned_scripts — Set the order the user's camera walks through their scripts — pass ids first-to-record first.
list_collections — List the collections (piles) the user already groups their scripts into, with counts.