WIA Motion: product video campaigns
ai.wiamotion/wiamotionVersion 1.0.0Create product video campaigns from 1-4 product photos and track them. Requires an API key.
Status
Responds886 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:35 UTC
- Latency
- 886 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.wiamotion.ai/mcpResponds886 msNo sign-in
Claude Code
claude mcp add --transport http wiamotion https://mcp.wiamotion.ai/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: wiamotion
Remote MCP server URL: https://mcp.wiamotion.ai/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"wiamotion": {
"url": "https://mcp.wiamotion.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"wiamotion","type":"http","url":"https://mcp.wiamotion.ai/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_campaignCheck status/progress/artifacts of a wiamotion campaign job by job_id (from create_campaign). | No | Yes | Yes | No |
create_campaignCreate a wiamotion product video campaign from 1-4 product photos. Produces finished 1080x1920 video(s) + thumbnail(s) + multi-language metadata (never a raw/unfinished clip) and deducts credits from the caller's account. Package tiers: "trial" (1 video, watermarked, 25cr, 3-language metadata), "starter" (1 video, 50cr, 254-language metadata), "launch" (3 videos — hook/how-to/brand mood — 254-language metadata, 125cr), "story" (everything in launch plus one 60-90s cinematic brand short on a premium engine, 400cr). DIRECT YOUR OWN CINEMATOGRAPHY: write distinct scene prompts (English, one short cinematic camera direction each) — this is what makes the result good, the server will not invent creative direction for you. Videos are subtitle-free by default (globally reusable); on-screen text (hook_text / endcard_text) is OPT-IN — omit both unless you specifically want burned-in copy for one language. For "starter"/"trial" use scenes[] (2-4 scenes, one video). For "launch"/"story" use hook_scenes[]/howto_scenes[]/brand_scenes[] (2-4 scenes each, one set per video role) — omit any of these to fall back to a generic template for that video. For "story" additionally use story_scenes[] (8-12 scenes) for the brand short — think in classic beats: hook, development, climax, resolution into the endcard. The server always appends a standard anti-distortion guard to every scene prompt server-side (keeps the product/printed text exactly as in the reference photo, no warping) — do not add your own "no distortion" wording, just describe the shot. Prefer image_urls over images_base64 when the photos are already hosted somewhere — base64 request bodies are capped at 8MB total (~1MB/photo) and get rejected past that. "creator" (200 credits, 2026-09-25) = a realistic on-screen presenter holds the product and speaks YOUR script with lip-sync (~12s, up to 15s): pass persona (who appears), setting (where), language, script (what they say — hook first, then proof), optional gender (voice) an | No | No | No | Yes |
list_packagesList wiamotion campaign packages — credit cost, video count/duration, resolution. Call before create_campaign to pick a package. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 17, 2026
- Updated
- Oct 17, 2026
- Repository
- Not given
- Categories (suggested)
- Design and mediaSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared