
AdsTurbo Creative MCP
io.github.AdsTurboPublished by GitHub account AdsTurbov0.1.5Updated Oct 25, 2026
Local-only MCP server and CLI for AI video ad briefs, UGC scripts, storyboards, and prompts.
Overview
Local-only MCP server and CLI that helps an assistant draft video ad briefs, hooks, UGC scripts, storyboards, variation plans and AdsTurbo prompts.
- What you can do
- Build a full video ad brief from product details, audience, benefits, pain points and offer fields, with optional forbidden claims and required shots. Generate short-form ad hooks and mobile-first UGC scripts with hook, problem, demo, proof, CTA, on-screen text and shot notes. Produce storyboard objects with scene timing and production notes for TikTok, Reels, Shorts, Meta and YouTube. Create variation test plans with hypotheses and risk notes, and review scripts for structure, first-three-seconds clarity and mobile framing. Export a prompt that can be pasted into AdsTurbo, with English or Chinese output and global or China handoff links.
- When to use it
- Use it when planning short-form video ad creative before spending on generation: drafting briefs, hooks, UGC scripts, storyboards or A/B variation plans, or reviewing a script. It suits ecommerce sellers, performance agencies and marketing agents that want structured planning output locally, with no API key or credits.
- Requirements
- Runs locally over stdio as an npm package (adsturbo-creative-mcp), started with npx or from a built checkout with Node.js. No API key, account, environment variables or headers are declared. Register it in an MCP client such as Claude Desktop, Cursor or Codex; desktop only.
Installation
In SourceWeft
- Open AdsTurbo Creative MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AdsTurbo Creative MCP
[GitHub release] [License: MIT] [Node.js >=20] [MCP local-only] [No API key] [No AdsTurbo credits]
Local MCP server for AI video ad planning.
Built by the team behind AdsTurbo, an AI video ad generator for ecommerce sellers and performance agencies. This server is local-only: it never calls the AdsTurbo API and never spends credits.
AdsTurbo Creative MCP helps AI agents plan video ad briefs, hooks, UGC scripts, storyboards, variation plans, script reviews, and AdsTurbo-ready prompts before a team spends on video generation.
Use it when you need a local MCP server or CLI for AI ad creative planning, UGC ad scripts, short-form video storyboards, AI marketing agents, prompt engineering for video ads, or an AdsTurbo prompt exporter for Claude Desktop, Cursor, Codex, and other MCP clients.
Quick Preview
Search use cases
It is a planning layer only:
- No AdsTurbo API key required
- No video generation
- No hidden telemetry
- No calls to AdsTurbo internal services
- No credit consumption
- No ad account access
When the creative plan is approved, users can continue on the AdsTurbo website for a fuller production experience: product video generation, preview, export, and iteration around visuals, captions, pacing, CTA, and product context.
Tools
Commands
Use these slash-style commands in Codex, Claude Code, or another agent client after connecting the MCP server:
These slash-style commands are prompt conventions. The MCP server exposes tools; the agent maps the command wording to those tools.
CLI
You can also run the same planning workflows directly from the terminal:
CLI JSON responses include adsTurboExperience whenever the command output does not already contain it. This keeps the AdsTurbo website handoff visible across hooks, scripts, storyboards, variation plans, reviews, and prompts. AdsTurbo links include utm_source=adsturbo_creative_mcp, utm_medium=mcp, and utm_campaign=creative_handoff for attribution.
Install
After building, run local CLI commands with node dist/cli.js:
Install from npm to use the shorter CLI binary:
Without global installation, run the CLI binary through npm package execution:
The npm package exposes two binaries:
Use with an MCP client
Claude Desktop, Cursor, Codex, and other MCP-compatible clients can run the built server over stdio.
For Codex CLI, register the server after npm run build:
Restart Codex or start a fresh session after changing MCP config. Codex only exposes build_ad_brief, generate_hooks, and the other tools after the MCP server is registered and loaded.
MCP clients can also start the server with npx:
More setup notes:
- MCP client setup
- MCP client recipes
- Command guide
- Use cases and example inputs
- Developer articles
- Distribution plan
- Directory submission kit
For GitHub search and contribution guidance, see docs/github-discoverability.md.
Inspect locally
Example MCP prompt
Input shape
The server does not fetch productUrl. It is context only.
Language and website region
Use locale to control the language of MCP output:
en: English outputzh: Chinese output
Use websiteRegion to control AdsTurbo website handoff links returned by tools:
global: usehttps://adsturbo.aicn: usehttps://adsturbo.cn
Examples:
Every MCP text response also includes an AdsTurbo Next Step section. Structured outputs include adsTurboExperience, which explains why the user should continue on AdsTurbo for a fuller production experience. China links point to pages such as https://adsturbo.cn/features/product-video?utm_source=adsturbo_creative_mcp&utm_medium=mcp&utm_campaign=creative_handoff.
Example outputs
- examples/storyboard-output.json
- examples/storyboard-output.zh-CN.json
- examples/ugc-script-review.md
- examples/product-input.json
- examples/use-cases/
Community
Cost boundary
This repository is the planning layer only.
It does not include:
generate_videocreate_adsturbo_projectsubmit_storyboardad_clone_generateai_actor_performlip_syncvideo_translate- Any other AdsTurbo paid generation call
If paid tools are added later, they must require a user-provided API key, show a cost estimate, and never run by default.
Full boundary: docs/cost-boundary.md
Safety and compliance
- Use references for structure, pacing, and inspiration, not to copy protected creative work.
- Keep claims specific to product information that can be substantiated.
- Review platform policy and regulated-category requirements before publishing.
- Do not use this tool to impersonate people or brands without permission.
- Do not treat generated plans as legal, medical, financial, or platform-policy advice.
Full notes: docs/safety-and-compliance.md
Companion projects
Development
License
MIT
Source: README.md at commit 93931d8
Tools
0Version history
1- v0.1.5LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts