Clipia MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIPIA_API_KEY | Yes | Your Clipia API key. Get one from https://clipia.ai/en/developer | |
| CLIPIA_MCP_URL | No | The URL of the Clipia MCP server (optional, defaults to https://mcp.clipia.ai/mcp) | https://mcp.clipia.ai/mcp |
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 | {} |
| prompts | {} |
| resources | {} |
| extensions | {
"io.modelcontextprotocol/ui": {
"mimeTypes": [
"text/html;profile=mcp-app"
]
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate image(s) from a text prompt, optionally with reference images (editing / image-to-image). Waits briefly for completion and usually returns the finished image inline (URL + small preview). Cost in credits is returned. |
| generate_videoA | Start a video generation from a text prompt (text-to-video) or from a start image (image-to-video, pass image_url). Returns request_id and cost in credits immediately — video renders take 1–10 minutes, poll with wait_generation. |
| generate_audioA | Generate speech from text (text-to-speech): pick a voice and language, get an mp3 back. Returns request_id and cost in credits immediately — narration is quick, poll with wait_generation until COMPLETED, then output.audio.url is the mp3. Pass the resulting request_id as voiceover_request_id in compose_video to narrate a multi-scene video, or use the mp3 on its own. |
| generate_musicA | Generate background music / a soundtrack from a text description: instrumental (no vocals) by default — ideal to play under narration. Returns request_id and cost in credits immediately; music takes ~1–3 min, so poll with wait_generation until COMPLETED, then output.audio.url is the mp3. Pass the resulting request_id as audio_request_id in compose_video to score a multi-scene video, or use the mp3 on its own. Describe mood/genre/tempo/instruments in the prompt (English works best). |
| compose_videoA | Stitch 2–20 finished video scenes into ONE final clip server-side (scenes are normalized to a common frame/fps, concatenated, optional soundtrack replaces scene audio). Pass request_id of your COMPLETED video generations (or media.clipia.ai URLs). Returns request_id (cmp_*) — poll with wait_generation until COMPLETED, then output.video.url is the final mp4. Typical full-video flow: generate_scenario → generate_video per scene → compose_video. |
| wait_generationA | Wait for a generation to finish (long-poll up to wait_seconds, then returns current status). Call repeatedly until status is COMPLETED, FAILED or CANCELED. Returns output URLs (and an inline image preview) when done. |
| get_generationA | Get the current status/result of a generation without waiting. When COMPLETED, output.images[].url is the inline webp preview and output.images[].original_url is the full-quality PNG/JPG. |
| app_get_generationB | Internal: status poll used by the Clipia generation viewer card. Prefer get_generation. |
| list_modelsA | List available AI models with type (image/video/audio), capabilities and base price in credits. Use before generating if the user asks for a specific model or to compare options. |
| get_modelA | Get model details: supported input parameters (input_schema) and base price in credits. |
| get_balanceA | Get the credit balance of the connected Clipia account and 30-day usage of the current API key. |
| search_templatesA | Search 3500+ curated prompt templates (hybrid text+semantic search, Russian or English query). Each result has a ready-to-use prompt and a recommended model — pass them to generate_image/generate_video. |
| chatA | Chat with a text LLM (Claude / GPT / Gemini / DeepSeek class) and get the reply text plus token usage and credit cost. Pass either a single prompt or a full messages array. Charged in credits from the connected account. |
| generate_scenarioA | Plan a multi-scene video from a brief: an LLM director returns a structured scenario — per-scene English video prompts with durations, plus a soundtrack prompt. Feed each scene prompt to generate_video, then stitch the finished clips with compose_video. Charged in credits like chat (LLM usage). |
| generate_presentationA | Generate a slide presentation (editable PPTX + PDF + PNG previews) from a DeckSpec you compose. Returns request_id (prs_*) — poll with wait_generation until COMPLETED, then output has pptx_url, pdf_url, preview_urls[]. Write the full spec: title, language (ru/en), theme (clipia-dark default, clean-light for print/office), and 3–20 slides. Each slide has a "layout": cover, section, bullets, two-col, image-full, quote, stats, or closing. For illustrations set image.prompt (English) — generated by our image models and billed as credits; skip images for text-only slides. Costs credits (render fee + illustrations). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| clipia_generation_viewer | Inline viewer card for Clipia generations: live progress, image/video preview, original-quality link. |
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes (e.g., generate_audio, generate_image, generate_video). However, app_get_generation and get_generation overlap significantly, and wait_generation adds a third polling tool, causing potential confusion.
The majority follow a verb_noun pattern (generate_*, get_*, list_models, search_templates). The only inconsistency is app_get_generation, which uses an unnecessary prefix and deviates from the standard naming style.
With 15 tools, the server covers a broad range of media generation tasks (audio, image, video, music, presentation, chat) and supporting utilities (balance, model info, templates). This count is well-scoped for its purpose.
Core generation and retrieval workflows are covered, but missing tools for listing or deleting generations and updating existing content (e.g., presentations) create minor gaps that agents may need to work around.