Other MCP clients
Screel exposes a standard Model Context Protocol server over Streamable HTTP, so any MCP-capable client — Claude Code, Cursor, IDE assistants, or your own agent — can drive the full video pipeline.
Endpoint
Section titled “Endpoint”https://api.screel.ai/mcpAuthentication is OAuth 2.1: the server advertises its authorization server via RFC 9728 protected-resource metadata, and clients that support MCP authorization (including Claude Code and Cursor) discover it automatically, register, and walk you through sign-in in the browser. Sign in with your Screel account — or create one during the flow — and approve the screel.read / screel.generate scopes.
For example, in Claude Code:
claude mcp add --transport http screel https://api.screel.ai/mcpWhat this surface offers
Section titled “What this surface offers”The generic endpoint is the complete tool set — everything in the tool reference:
- all project/scene/storyboard management tools;
- all generation tools (scene images, image refinement, animation, voiceover, music, upscaling);
- rendering and job tracking.
Responses are plain structured JSON — no widgets or host-specific metadata. Where the ChatGPT app takes file attachments, this surface takes public image URLs (image_url on set_scene_image, reference_image_urls on refine_scene_image); images are fetched server-side over HTTPS.
Generation tools return a job_id immediately rather than blocking; poll get_job_status (up to 40 job IDs per call) for progress and results. Generating content and rendering spend credits from your Screel account — get_account reports your balance and per-action costs.