What is the Clipia MCP remote MCP server?
The Clipia MCP remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.clipia.ai/mcp, so AI assistants can connect to it without installing or running anything locally.

@Clipia.ai
Basic information
Transport
Streamable HTTP
Authentication
OAuth
Last updated
Category
Media & Design
Author
Clipia.ai
Submitted by
Maksim Zakharov
Hosted MCP server for generating AI images, videos, speech, music, and presentations from agents and IDEs. Supports OAuth and Clipia API keys.
https://mcp.clipia.ai/mcpclaude mcp add clipia-mcp --transport http https://mcp.clipia.ai/mcpGenerate 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.
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 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 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).
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 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 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.
Internal: status poll used by the Clipia generation viewer card. Prefer get_generation.
List available AI models with type (text/image/video/audio), capabilities and pricing in credits. Text models are priced per 1K input/output tokens; generation models show a base price. Use before chat or generation when the user asks for a specific model or wants to compare options.
Get model details and pricing. Generation models include input_schema and a base credit price; text models include context limits and per-1K input/output credit rates.
Get the credit balance of the connected Clipia account and 30-day usage of the current API key.
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.
Chat with a text LLM and get reply text, token usage and credit cost. Supports strict JSON Schema output and an idempotency key for safe transport retries. Pass either a single prompt or a full messages array. Charged in credits from the connected account.
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 a BRAND-NEW slide presentation (editable PPTX + PDF + PNG previews) from a DeckSpec you compose. To change a deck that already exists (slide text, title, theme, add/remove/reorder slides) use edit_presentation instead — it reuses the illustrations already generated instead of billing them again. 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, optional brand, and 3–20 slides. ALWAYS pick the theme that fits the SUBJECT of the deck; the deck belongs to the user, so never default to the Clipia brand palette unless the deck is about Clipia itself. Set brand.name/brand.website only if the user names their company — otherwise slides stay unbranded. 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).
Edit an EXISTING presentation instead of regenerating it: change slide text, title, theme, add/remove/reorder slides. The deck is rebuilt from its saved spec and the illustrations that were already generated — those are reused for free, so a text fix costs only the small render fee. Use it for ANY change request about a deck that already exists; generate_presentation is only for a brand-new deck. All "index" values are 0-based positions in the CURRENT deck. An illustration is redrawn (and billed) ONLY if you change that slide's image.prompt, list it in regenerate_images, or set regenerate_all_images=true. Returns request_id (prs_*) — poll with wait_generation until COMPLETED.
Clipia MCP connects AI agents and IDEs to hosted image, video, speech, and music generation tools.
https://mcp.clipia.ai/mcpThe Clipia MCP remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.clipia.ai/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://mcp.clipia.ai/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. Clipia MCP uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Clipia MCP exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Read-only, source-backed AI model pricing, history, comparisons and cost calculations.
Remote MCP for AI image, video, music, speech and custom voice generation. Discover models and input schemas for free; authorize your APIXO account to generate media and check results.
Live crypto trading signals via API. Full trade setups with entry, stop-loss, take-profit, leverage, and automated verification. Built for Claude Code, OpenAI Codex, and 30+ AI agents.
Checks whether an EVM address has an EIP-7702 delegation (the trick behind wallet sweepers) on Ethereum, Base, BNB Chain, Arbitrum, OP, Polygon, Gnosis and Unichain
Write, schedule and publish LinkedIn posts in your own voice, reply to comments and read your analytics, all from your AI assistant. Remote MCP server with OAuth sign-in.
Comments