Use Clipia with AI agents

Clipia is an AI media generation platform that agents can operate directly across a catalog of 60+ image and video models. Through the remote MCP server at https://mcp.clipia.ai/mcp, an agent can generate video from text or a start image, create or edit images, produce speech and music, assemble multi-scene videos, create presentations, inspect available models, track jobs and return finished files to the conversation. For application-owned image and video workflows, call the REST API or an official SDK.

MCP or REST API: which one?Copy Anchor Link

MCP and REST use the same Clipia account, credit balance and generation history where their capabilities overlap. There is no separate MCP markup.

Tools available to AI agentsCopy Anchor Link

The full profile, available with an API key, contains 15 agent-callable tools: 10 core tools plus five that appear when their product capabilities are enabled. Over OAuth in claude.ai and ChatGPT the set can be narrower, for example without get_balance. The tools/list response is authoritative for your connection.

10 core toolsCopy Anchor Link

• generate_image — generate or edit images from a prompt and optional references
• generate_video — create video from text or a start image
• generate_audio — convert text to speech
• generate_music — create background music or a soundtrack
• wait_generation — long-poll an asynchronous job until it finishes
• get_generation — read status and finished file URLs without waiting
• list_models — discover active models, capabilities and credit prices
• get_model — inspect one model's input schema and price
• get_balance — read the connected account's credit balance and recent usage
• search_templates — find ready-to-use image and video prompts

5 capability-dependent toolsCopy Anchor Link

• chat — call a text model
• generate_scenario — turn a video brief into structured scenes and prompts
• compose_video — combine generated scenes, narration, music and subtitles
• generate_presentation — create an editable PPTX, PDF and slide previews
• edit_presentation — revise an existing deck while reusing unchanged illustrations

Seven app-only helpers drive live result, rerun and composition cards. They remain outside the model context and do not increase the AI agent's tool list. See MCP tools for parameters and availability details.

Ready-made promptsCopy Anchor Link

Besides tools, the server exposes four ready-made workflows through prompts/list. Claude Code shows them as slash commands; other clients list them in their prompt menu. A prompt inserts step-by-step instructions for the agent into the conversation; the generations themselves run through the regular tools and are paid in credits.

End-to-end video workflowCopy Anchor Link

An agent can complete a full video rather than stopping at a single generated clip:

1. Call generate_scenario to split a brief into scenes when scenario planning is enabled.
2. Call generate_video for each scene. Pass image_url when a start frame or visual reference should guide the shot.
3. Call generate_audio for narration and generate_music for the soundtrack when needed.
4. Call compose_video to assemble 2–20 completed scenes, optional voiceover, music and subtitles.
5. Call wait_generation until the final job is COMPLETED, then return output.video.url.

For a single clip, start with generate_video and poll the returned request_id; the planning and composition tools are optional.

Getting a keyCopy Anchor Link

Create an API key in the Developer Console. Keys prefixed clipia_live_ are live (they charge credits); keys prefixed clipia_test_ run in the sandbox: instant test results with no charge, handy for debugging agents and CI.

Connect a clientCopy Anchor Link

claude mcp add --transport http clipia https://mcp.clipia.ai/mcp \
  --header "Authorization: Bearer $CLIPIA_KEY"

OAuth sign-in (claude.ai, ChatGPT and other clients with a consent screen) stays valid for 180 days from the moment you click "Allow": after that the client asks you to sign in to Clipia and confirm access again. You can revoke access earlier in the Developer Console, "Connected apps" tab — the app loses access to the account immediately. Changing your password in the settings pauses these connections until your next sign-in to your Clipia account, and resetting it through the email link revokes them.

Jobs, cost and safe retriesCopy Anchor Link

Image calls often finish in one request. Video, audio, music, composition and presentation jobs are asynchronous:

1. The generation tool returns a request_id, current status and the credit cost.
2. Call wait_generation repeatedly until the status is COMPLETED, FAILED or CANCELED.
3. On completion, read the media or document URLs from output.

Use a stable idempotency_key only when retrying the same unchanged paid request after a transport or ambiguous failure. Use a new key after changing the prompt, files or settings: the same key with different input, including a different num_images or a switch between a single run and a batch, returns idempotency_key_reuse. A key is up to 255 characters and is accepted by generate_image, generate_video, generate_audio, generate_music, generate_scenario and chat. This prevents an agent loop from charging twice for the same operation.

SandboxCopy Anchor Link

Keys prefixed clipia_test_ return instant test results with no charge — useful for debugging response parsing, polling and pipelines. Live keys return the exact cost of each generation, and the get_balance tool reports the remaining credit balance.

Agent workflow questionsCopy Anchor Link

Machine-readable discoveryCopy Anchor Link

Agents and crawlers can discover the same contract without parsing the marketing site:

• LLM product facts and tool inventory
• Developer documentation index
• MCP server card
• Agent skills index
• OpenAPI 3.1 specification
• Authentication guide

The server card is built from the current configuration and shows the full profile for an API key; tools/list returns the exact set for your connection. See the full MCP tools reference or the REST API overview.