Content Tools

dailystudio.app

Manages Daily Studio video scripts, content plans, teleprompter links, and connected social accounts for scheduling and publishing.

1 endpoint12 known toolsFirst detected September 11, 2026Last detected September 11, 2026

ENDPOINT 1

https://dailystudio.app/mcp

No auth detected

MCP server metadata

Name: safevertical
Version: 1.0.0

Capabilities

toolsresourcesprompts

Known tools 12

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.

Inferred read-only

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.

Inferred read-only

add_scripts_to_plan

Put finished scripts into the user's Daily Studio content plan, each with the day it should go out.

Inferred read-only

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

Inferred read-only

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.

Inferred read-only

get_planned_scripts

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

Inferred read-only

archive_planned_scripts

Archive scripts out of the user's working plan, by id — or restore archived ones with `restore: true`.

Inferred read-only

reorder_planned_scripts

Set the order the user's camera walks through their scripts — pass ids first-to-record first.

Inferred read-only

list_collections

List the collections (piles) the user already groups their scripts into, with counts.

Inferred read-only

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.

Inferred read-only

cancel_scheduled_post

Cancel one post that is waiting to go out, by id from list_scheduled_posts.

Potential side effects

retry_scheduled_post

Put one failed post back in the queue, due now — by id from list_scheduled_posts.

Potential side effects

CONNECT WITH APPROVAL

Client installation

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.