Ceo MCP Media
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | API key for real Gemini/Veo generation. Set in .env or process environment. Required only when using actual generation capabilities. |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| media.project.createC | Create a media project manifest. |
| media.project.listA | List media projects. |
| media.project.getB | Read a media project. |
| media.character.lockC | Create a Character Bible / identity continuity lock. |
| media.storyboard.planC | Plan a multi-shot storyboard with <=8 second shots. |
| media.image.generateC | Submit a durable image-generation job. |
| media.video.generateB | Submit a durable video-generation job and return immediately with a job id. |
| media.video.regenerateC | Create a replacement video job for one shot. |
| media.audio.voiceB | Submit a durable voice/TTS generation job. |
| media.audio.musicC | Submit a durable music generation job. |
| media.composeC | Submit an FFmpeg composition/render job. |
| media.subtitle.generateB | Generate an SRT sidecar from storyboard dialogue. |
| media.director.reviewC | Run deterministic continuity/shot QA. |
| media.job.statusB | Read durable job status. |
| media.job.listB | List durable jobs. |
| media.job.run_onceC | Advance one durable job by one non-blocking step. |
| media.job.tickB | Advance due jobs by one step each. |
| media.job.cancelC | Cancel a durable job. |
| media.provider.statusA | Read provider readiness without paid generation. |
| media.flow.handoffC | Prepare an optional Google Flow handoff package. |
| media.capabilitiesB | Return V1-V6 capability manifest. |
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 21 tools
Most tools map to a clear resource-action pair, so project, storyboard, generation, review, and job tools are easy to distinguish. The closest pair is media.job.run_once vs media.job.tick, which both advance jobs and could be selected incorrectly, and media.provider.status vs media.capabilities also overlap in availability reporting.
The media.<area>.<detail> prefix pattern is consistent, but the last segment alternates between verbs and nouns: media.project.create, media.image.generate, and media.job.cancel are verb-style, while media.audio.voice, media.audio.music, media.job.status, and media.capabilities are noun-style. A few names like media.compose and media.capabilities also drop the resource or action part, making the convention mixed but still readable.
21 tools is in the heavy range for an MCP server, even though the media pipeline spans project, storyboard, generation, composition, review, and job management. Several tools, such as media.job.run_once, media.job.tick, media.provider.status, and media.flow.handoff, feel like optional advanced controls that could be consolidated without losing core functionality.
The set covers the main lifecycle: create project, plan storyboard, generate image/video/audio, compose, subtitle, review, and manage durable jobs. Minor gaps remain, such as no media.project.update/delete, no direct storyboard read/update, and no explicit asset retrieval endpoint, but agents can likely work around these via job status and project manifests.