Daily Studio Teleprompter
warningsdailystudio.app
Send a shoot's worth of scripts to the Daily Studio teleprompter on iPhone, in one link.
https://dailystudio.app/mcpWebsiteOAuthMCP 2025-06-18v1.0.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 312 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://dailystudio.app |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | publish, offline_access |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 12 tools listable |
| Credentials demanded in prose | ✕list_connected_accounts, add_scripts_to_plan These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
| Documentation | https://dailystudio.app/ |
What the probe found
2 of the 12 tools listed anonymously say in their own descriptions that they need an account or a key (list_connected_accounts, add_scripts_to_plan), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
The server exposes a public surface before authorization: send_script_to_teleprompter, list_connected_accounts, add_scripts_to_plan, list_planned_scripts, edit_planned_scripts, get_planned_scripts, archive_planned_scripts, reorder_planned_scripts, list_collections, list_scheduled_posts, cancel_scheduled_post, retry_scheduled_post.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/daily-studio-teleprompter)Own this server?
Sign in to claim this listing by proving control of the endpoint.