Sora 2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key with Sora 2 access. Note: Sora 2 access requires a verified organization on the OpenAI platform. |
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_videoC | Generate a video using Sora 2 or Sora 2 Pro model. Creates a video from a text prompt with optional parameters for resolution, duration, and model selection. |
| get_video_statusB | Get the status and details of a video generation job. Returns information about whether the video is still processing, completed, or failed. |
| list_videosB | List all video generation jobs with optional filtering and pagination. |
| delete_videoC | Delete a video generation job and its associated data. |
| merge_videosB | Merge multiple video files into a single video. Videos are concatenated in the order provided. |
| create_fade_animationB | Create a fade-in animation video from a static image. The image will fade from black to full visibility. |
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 with no ambiguity. The tools cover different aspects of video generation and management: creation (create_video, create_fade_animation), status checking (get_video_status), listing (list_videos), deletion (delete_video), and merging (merge_videos). There is no overlap in functionality that would cause misselection.
All tool names follow a consistent verb_noun pattern using snake_case. The verbs (create, delete, get, list, merge) are clear and appropriate for their actions, and the nouns (fade_animation, video, video_status, videos) accurately describe the resources. There are no deviations or mixed conventions.
With 6 tools, the server is well-scoped for its purpose of video generation and management. Each tool earns its place by covering essential operations: creating videos, checking status, listing jobs, deleting jobs, and merging videos. This count is neither too thin nor too heavy for the domain.
The tool set provides complete CRUD/lifecycle coverage for video generation jobs. It includes creation (create_video, create_fade_animation), reading (get_video_status, list_videos), deletion (delete_video), and additional utility (merge_videos). There are no obvious gaps, and agents can handle the full workflow from generation to management.