Sora2 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NAME | No | Server name override | sora2-mcp |
| OPENAI_API_KEY | No | Your OpenAI API key with Sora access (alternative to SORA2_MCP_API_KEY) | |
| SORA2_MCP_API_KEY | No | Your OpenAI API key with Sora access |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_videoA | Start a new video generation job with Sora. Returns a job object with status. Poll get_video_status or use webhooks to monitor completion. |
| get_video_statusA | Retrieve the current status and progress of a video generation job. Status values: queued, in_progress, completed, failed. |
| download_videoA | Download the completed video file (MP4), thumbnail (WebP), or spritesheet (JPEG). Only works when status is 'completed'. Returns base64-encoded binary data. |
| list_videosA | List all video jobs with pagination support. Returns metadata for enumeration, dashboards, or housekeeping. |
| delete_videoA | Delete a video from OpenAI's storage. This action is permanent. |
| remix_videoA | Create a new video by remixing an existing completed video with targeted adjustments. Preserves structure and composition while applying modifications. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: create, status check, download, list, delete, and remix. There is no overlap between them, and even the two retrieval tools (get_video_status and download_video) are cleanly separated by their output.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_video, get_video_status, download_video). The only minor variance is list_videos being plural, which is natural for a collection operation and does not break the pattern.
Six tools is well-scoped for a video generation service. The set covers the full job lifecycle (create, poll, download, list, delete) plus an additional remix feature, without unnecessary redundancy or bloat.
The core lifecycle is covered, but there is no way to cancel an in-progress job or fetch full metadata for a single video without listing all jobs. These are minor gaps that agents can work around, so the surface is mostly complete.