MCP for AI agents
A Model Context Protocol server exposes CreatorSaver tools to AI agents and assistants, so a model can fetch transcripts and public creator data as part of a workflow.
CreatorSaver
Use CreatorSaver's transcript and public-creator-data tools from your own code or an AI agent — over a standard API and an MCP server.
The same capabilities the web app runs on, exposed for developers and agents.
A Model Context Protocol server exposes CreatorSaver tools to AI agents and assistants, so a model can fetch transcripts and public creator data as part of a workflow.
Standards-based auth with PKCE and Dynamic Client Registration, plus a separate bearer audience for API vs. agent access.
Static API keys for server-to-server integrations, alongside the OAuth flow for user-authorized apps.
Submit longer jobs and poll for status — built for bulk transcript and data tasks rather than a single blocking request.
Pull results back out in the formats the Studio supports, so agent output plugs into your own pipeline.
The same verified transcript and public-profile capabilities as the app, exposed as callable tools.
Where the Agent & API stands today, and how to get in before it opens.
The Agent & API is in preview while we finish the security work required before opening paid public access. If you want to build with CreatorSaver transcripts and public creator data, join the waitlist and we'll reach out.
The MCP connector for Claude and ChatGPT is live for subscribers — see how to connect.
See the Transcript Studio for the product these tools are built on, and Pricing for plans.
Find answers to common questions about CreatorSaver.
It's a way to use CreatorSaver's transcript and public-creator-data tools from your own code or an AI agent — over a standard API and a Model Context Protocol (MCP) server, with OAuth 2.1 or API keys.
It's in developer preview. We're finishing security hardening required before opening paid public access, so today you can join the waitlist and, where invited, test with limited access.
They cover transcripts and public creator/content data — the same verified capabilities as the app. They do not provide access to private content, and there is no monitoring or backup capability.
OAuth 2.1 with PKCE and Dynamic Client Registration, a separate bearer audience for API vs. agent tokens, and per-key rate limits. Network-level protections are being finalized before public paid access.
Run a profile report, transcribe a video, or export a whole batch — all from one workspace.