Clipia MCP
Generate AI images, video, speech, and music from Claude, ChatGPT, Cursor, and other MCP clients through the Clipia API.
README
Clipia MCP
Generate AI images & video inside Claude, Cursor, ChatGPT — 50+ models in one MCP endpoint.
Clipia is an AI image & video generation platform. This is its hosted, remote Model Context Protocol (MCP) server: a single endpoint that lets any MCP-capable AI agent generate images and video, poll results, browse models, search prompt templates and read your credit balance — no SDK and no code required.
Endpoint: https://mcp.clipia.ai/mcp — stateless Streamable HTTP, authenticated with a Clipia API key.
Glama server runtime
The repository includes a minimal Docker runtime so Glama can start the public server entry and inspect its MCP tool definitions. The container is a stdio bridge to the hosted endpoint; it does not contain the Clipia application or any credentials.
Configure CLIPIA_API_KEY as a secret in Glama. Use a sandbox key with the
clipia_test_ prefix so validation never spends credits. The optional
CLIPIA_MCP_URL setting defaults to https://mcp.clipia.ai/mcp and only accepts
HTTPS URLs.
docker build -t clipia-mcp-glama .
docker run --rm -i \
-e CLIPIA_API_KEY='<CLIPIA_TEST_API_KEY>' \
clipia-mcp-glama
Quick start
Connect Clipia to Claude Code in one command (replace the placeholder with your key):
claude mcp add --transport http clipia https://mcp.clipia.ai/mcp \
--header "Authorization: Bearer <CLIPIA_API_KEY>"
Then just ask in the chat: "Generate a neon city image with Clipia" — the preview lands right in the terminal.
Where to get a key: create one in the Clipia Developer Console. The key is shown once.
Sandbox without charges: keys with the clipia_test_ prefix run in a sandbox — instant mock results, no credits spent. Use a clipia_test_* key to validate your integration before going live.
Connect from any client
The endpoint is the same everywhere: https://mcp.clipia.ai/mcp. IDEs and CLIs authenticate with an API key from the Developer Console; claude.ai and ChatGPT connect by signing in to your Clipia account over OAuth (no key needed).
Ready-to-paste configs live in examples/.
| Client | How to connect | Auth |
|---|---|---|
| Claude Code | claude mcp add --transport http clipia … (see Quick start) |
API key |
| Claude Desktop | mcp-remote bridge in claude_desktop_config.json |
API key |
| claude.ai (web/desktop/mobile) | Settings → Connectors → Add custom connector | OAuth |
| Cursor | ~/.cursor/mcp.json (or project .cursor/mcp.json) |
API key |
| VS Code | .vscode/mcp.json (servers + inputs) |
API key |
| Cline | cline_mcp_settings.json (mcpServers) |
API key |
| Windsurf | ~/.codeium/windsurf/mcp_config.json (serverUrl) |
API key |
| Codex CLI | ~/.codex/config.toml (bearer_token_env_var) |
API key (env) |
| Gemini CLI | gemini mcp add --transport http clipia … |
API key |
| ChatGPT | Developer mode → Apps & Connectors → Create | OAuth |
Claude Code
claude mcp add --transport http clipia https://mcp.clipia.ai/mcp \
--header "Authorization: Bearer <CLIPIA_API_KEY>"
Claude Desktop
Claude Desktop bridges to remote HTTP servers through mcp-remote. Add to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude Desktop:
{
"mcpServers": {
"clipia": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.clipia.ai/mcp",
"--header",
"Authorization: Bearer <CLIPIA_API_KEY>"
]
}
}
}
claude.ai (web / desktop / mobile)
- Open Settings → Connectors.
- Click Add custom connector and paste the URL:
https://mcp.clipia.ai/mcp - Click Connect and sign in to your Clipia account — no key needed (OAuth).
- In a new chat, ask for an image or a video: a live Clipia card with progress and the result appears inside the message.
Credits are charged to the connected Clipia account.
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project), then restart Cursor:
{
"mcpServers": {
"clipia": {
"url": "https://mcp.clipia.ai/mcp",
"headers": { "Authorization": "Bearer <CLIPIA_API_KEY>" }
}
}
}
VS Code
Create .vscode/mcp.json in your workspace (or use the MCP: Add Server command). VS Code prompts for the key on first run and stores it securely:
{
"servers": {
"clipia": {
"type": "http",
"url": "https://mcp.clipia.ai/mcp",
"headers": { "Authorization": "Bearer ${input:clipia_api_key}" }
}
},
"inputs": [
{
"type": "promptString",
"id": "clipia_api_key",
"description": "Clipia API Key",
"password": true
}
]
}
Cline
Cline reads mcpServers from its cline_mcp_settings.json (MCP Servers → Configure MCP Servers in the Cline panel):
{
"mcpServers": {
"clipia": {
"url": "https://mcp.clipia.ai/mcp",
"headers": { "Authorization": "Bearer <CLIPIA_API_KEY>" }
}
}
}
Cline can also install this server itself — see llms-install.md.
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json (note the Windsurf-specific serverUrl field), then refresh Cascade → MCPs:
{
"mcpServers": {
"clipia": {
"serverUrl": "https://mcp.clipia.ai/mcp",
"headers": { "Authorization": "Bearer <CLIPIA_API_KEY>" }
}
}
}
Codex CLI
Add a block to ~/.codex/config.toml and export the key into your environment — Codex injects Authorization: Bearer from the variable automatically:
# ~/.codex/config.toml
[mcp_servers.clipia]
url = "https://mcp.clipia.ai/mcp"
bearer_token_env_var = "CLIPIA_API_KEY"
# in your environment:
# export CLIPIA_API_KEY=<CLIPIA_API_KEY>
Gemini CLI
gemini mcp add --transport http clipia https://mcp.clipia.ai/mcp \
--header "Authorization: Bearer <CLIPIA_API_KEY>"
Verify the connection with gemini mcp list.
ChatGPT (Developer Mode)
- In ChatGPT (web): Settings → Apps & Connectors → Advanced settings → enable Developer mode (Plus, Pro, Business, Enterprise).
- Back in Apps & Connectors → Create. Name it
Clipia, MCP Server URL:https://mcp.clipia.ai/mcp. - Authentication — OAuth, tick "I trust this application", click Create.
- Sign in to your Clipia account in the popup. In a chat press + → More → Clipia, then ask in plain text.
Supported auth header schemes: Authorization: Bearer clipia_* (recommended), Authorization: Key <key>, or X-Api-Key: <key>.
Tools
The server always exposes 10 core tools to the agent. As of 2026-07-11, production exposes 14 agent tools: the 10 core tools plus chat, scenario planning, server-side video composition and presentation generation. A separate app-only helper is hidden from the AI agent. Compact schemas keep the agent's context window light.
| Tool | What it does |
|---|---|
generate_image |
Generate image(s) from a text prompt, optionally with reference images (editing / image-to-image). Waits briefly and usually returns the finished image inline (URL + small preview). Cost in credits is returned. |
generate_video |
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 — renders take 1–10 min, poll with wait_generation. |
generate_audio |
Generate speech from text with a selected voice and language. Returns an MP3 when complete. |
generate_music |
Generate background music or a soundtrack from a description of mood, genre and tempo. |
wait_generation |
Wait for a generation to finish (long-poll up to wait_seconds, then returns current status). Call repeatedly until COMPLETED, FAILED or CANCELED. Returns output URLs (and an inline preview) when done. |
get_generation |
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. |
list_models |
List available AI models with type (image/video/audio), capabilities and base price in credits. Filter by type / search. |
get_model |
Get model details: supported input parameters (input_schema) and base price in credits. |
get_balance |
Get the credit balance of the connected Clipia account and 30-day usage of the current API key. |
search_templates |
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. |
chat |
Currently enabled, feature-gated: chat with a text LLM using a prompt or messages array; returns reply text, token usage and credit cost. |
generate_scenario |
Currently enabled, feature-gated: turn a brief into per-scene video prompts and a soundtrack prompt. |
compose_video |
Currently enabled, feature-gated: stitch 2–20 completed scenes into a final MP4 with optional voiceover, soundtrack and subtitles. |
generate_presentation |
Currently enabled, feature-gated: render an editable PPTX, PDF and previews from a structured deck specification. |
app_get_generation |
Internal / app-only: status poll used by the Clipia generation viewer card (MCP Apps). Hidden from the model; prefer get_generation. |
Default models (used when no slug is passed): nano-banana-2 for images, seedance-2-fast-t2v / seedance-2-fast-i2v for video. Override with a model slug from list_models.
Why Clipia
- Pay from Russia & CIS — Russian bank cards, SBP, MIR, no VPN required. Western processors reject these; Clipia is built for this market (and works internationally too).
- 50+ flagship models, one endpoint — Western and Chinese models side by side: Veo 3.1, Sora, Kling 3, Seedance 2, Hailuo, Wan 2.7, Nano Banana, FLUX, Midjourney V7, Imagen 4, and more. No juggling multiple foreign subscriptions.
- Sandbox without charges —
clipia_test_*keys return instant mock results with no credit spend, perfect for wiring up an integration or CI. - Live preview in the chat (MCP Apps) — on claude.ai (web/desktop/mobile) every generation renders an interactive card with live progress, the finished media and an "Original" button. In Claude Code the preview lands inline in the terminal for vision-based iteration.
- 3500+ prompt templates —
search_templatesgives the agent curated, ready-to-use prompts (hybrid search, RU/EN), each with a recommended model. - Cost in every response — every generation returns its exact cost in credits, and
get_balanceshows the remaining balance. No hidden MCP markup. - Compact tool surface — 10 core tools with tight schemas keep the agent's context window light; enabled capabilities add only the tools they need.
SDK
Prefer calling Clipia from your own code instead of an agent? Use the official SDKs against the same public API (fal.ai-style submit → status → result queue, credits-based billing):
- TypeScript / Node:
clipia-ai—npm install clipia-ai(also ships aclipiaCLI). - Python:
clipia—pip install clipia(sync + async clients).
Both support webhooks with HMAC-SHA256 signature verification and the same clipia_test_* sandbox keys.
Pricing
Billing is in credits from your connected Clipia account — the same balance as the website. Every generation returns its exact credit cost, and get_balance shows what's left. Different models cost different credits depending on resolution, duration and quality.
New accounts receive a small pack of welcome credits to evaluate the platform; after that a subscription is required. Four monthly plans (Basic / Standard / Pro / Ultima) — see clipia.ai/tariffs.
clipia_test_* sandbox keys return mock results with no credit charge — use them to develop and test without spending.
🇷🇺 Для России и СНГ
Clipia — AI-платформа для генерации изображений и видео с русским интерфейсом и поддержкой. Для пользователей из России и СНГ доступны оплата картой РФ, СБП и МИР, без VPN. 50+ западных и китайских моделей (Veo 3.1, Sora, Kling 3, Seedance 2, Nano Banana, FLUX, Midjourney V7) работают через один MCP-эндпоинт прямо из Claude, Cursor и ChatGPT.
Подключение в одну команду (ключ — в консоли разработчика):
claude mcp add --transport http clipia https://mcp.clipia.ai/mcp \
--header "Authorization: Bearer <CLIPIA_API_KEY>"
Ключи clipia_test_* — песочница без списания кредитов для отладки. Биллинг в кредитах, стоимость каждой генерации возвращается в ответе. Тарифы: clipia.ai/tariffs.
Links
- Developers / REST API & SDK: clipia.ai/developers
- MCP landing: clipia.ai/mcp
- Model catalog: clipia.ai/models
- Pricing: clipia.ai/tariffs
- Get an API key: clipia.ai/en/developer
Support & legal
- Website: clipia.ai
- Documentation: clipia.ai/docs/mcp
- Privacy Policy: clipia.ai/privacy
- Terms: clipia.ai/terms
- Support: hello@clipia.ai
License
MIT — see LICENSE. © 2026 Clipia (IP Zakharov Maksim Sergeevich).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.