ClipSubtitles exposes a remote Model Context Protocol server:
https://api.clipsubtitles.com/api/mcp
Use an MCP client that supports remote Streamable HTTP servers and OAuth. Add the endpoint using the client’s normal Add connector, Add MCP server or equivalent flow. When the browser sign-in opens:
sign in to your ClipSubtitles account;
review the requested captions:read and captions:write scopes; and
approve the connection only if the client name and scopes are expected.
There is no ClipSubtitles API key to paste into a chat. Never send an agent your password, one-time code, access token or signed media URL.
An authorized agent can create a project, import a public media URL or return a web upload link, generate captions, read and explicitly edit words or timing, choose a style, create a free preview, request an export quote, start an approved render, poll progress and return finished downloads.
The agent can prepare a paid export and show the fixed quote, but a person must approve the quoted credit cost before the render begins. A connection does not give an agent permission to spend credits silently.
Open Settings, find Agent connections, and choose Revoke beside the client. Its tokens stop working immediately. Revoking a client does not delete your caption projects or exports.
Client menus and labels change over time. If your client does not support remote OAuth MCP servers, use the web studio or the REST API instead.
