Ads AI Creator MCP Server
Allows generation of video advertisements optimized for Facebook using Ads AI Creator's platform-specific export formats and aspect ratios.
Allows generation of video advertisements optimized for Google Ads using Ads AI Creator's platform-specific export formats and aspect ratios.
Allows generation of video advertisements optimized for Instagram using Ads AI Creator's platform-specific export formats and aspect ratios.
Allows generation of video advertisements optimized for TikTok using Ads AI Creator's platform-specific export formats and aspect ratios.
Allows generation of video advertisements optimized for YouTube using Ads AI Creator's platform-specific export formats and aspect ratios.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ads AI Creator MCP ServerList all available ad styles"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ads AI Creator MCP Server
Ads AI Creator - Generate Ads with AI
A Model Context Protocol server that exposes the canonical Ads AI Creator knowledge surface — image generation workflows and styles, pricing, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.
Official website: https://adsaicreator.com
🎨 About Ads AI Creator
Ads AI Creator is an AI-powered platform that generates professional video advertisements from product images, descriptions, or scripts — no camera, studio, or video editing experience required. Users supply source material and the platform handles the rest: selecting or customizing an AI avatar, writing copy, adding voiceover in the chosen language, and exporting a finished video formatted for the target ad channel. The result is a production-ready ad in minutes rather than days. The platform is designed for teams and individuals who need consistent creative output at a volume that traditional production workflows cannot sustain.
Related MCP server: Muse AI Image MCP Server
Key Features
AI Avatar Library: A broad selection of realistic AI presenters with filters for gender, apparent age, and language, enabling brand-consistent spokesperson selection across campaigns.
Integrated AI Copywriting: Automated generation of headlines, calls-to-action, and body text optimized for ad performance, reducing the need for a dedicated copywriter on every variation.
Multi-Language Voiceover: Native-quality audio output in 50+ languages, making it practical to adapt a single campaign for international markets without re-recording.
Bulk Variation Generation: Multiple ad versions with different visuals, scripts, or CTAs can be produced simultaneously, supporting structured A/B testing without proportional increases in production time.
Platform-Specific Export: One-click export in formats and aspect ratios optimized for TikTok, Instagram, YouTube, Facebook, and Google Ads, removing the manual reformatting step between channels.
4K Output and Compliance Checks: Broadcast-resolution exports paired with automated checks against major platform advertising policies before delivery.
RESTful API: Programmatic access for teams that want to integrate ad generation into existing marketing automation pipelines or internal tools.
Use Cases
E-commerce product launches: Convert product photos and a short brief into a polished video ad ready to run on Meta or TikTok within the same working session.
Performance marketing iteration: Generate dozens of headline and visual combinations in one batch, then route them into an A/B testing framework to find the highest-converting variant quickly.
Agency content at scale: Manage multiple client accounts by producing differentiated creative for each brand from a shared avatar and copy library, without per-project production overhead.
International market entry: Adapt an existing ad concept into 10 or 20 language versions with localized voiceover in a single workflow, avoiding separate localization vendors.
Dropshipping and solo operators: Produce credible, spokesperson-driven ads without hiring a video crew or contracting a freelance editor, keeping production costs proportional to early-stage budgets.
Who Is It For
Ads AI Creator is built for marketers, e-commerce operators, and creative teams whose output demands outpace traditional production capacity. Performance marketers who run continuous creative refresh cycles will find the bulk generation and A/B tooling directly useful. E-commerce brand owners and dropshippers working with limited budgets get access to video ad production that was previously gated behind agency retainers or full production crews. Agencies handling multiple accounts benefit from the speed and language coverage when scaling client deliverables. The platform also suits growth-focused teams that want to maintain a presence across several ad channels simultaneously without expanding headcount to match the creative workload.
Tools
list_styles
Return the canonical list of image-generation styles or presets the site exposes. (Ads AI Creator)
Input: no parameters. Returns: text/markdown.
get_pricing
Return the canonical pricing entry point for Ads AI Creator.
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for Ads AI Creator (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://ads-ai-creator/styles— Supported image-generation styles and presets.site://ads-ai-creator/pricing— Canonical pricing entry point.site://ads-ai-creator/faq— Short FAQ generated from public site metadata.site://ads-ai-creator/links— Canonical URLs to share with users.
Prompts
tell_me_about_ads_ai_creator
Summarize what the site is, who it's for, and how it works. — Ads AI Creator
try_image_style_ads_ai_creator
Recommend a starting image-generation style for a stated goal. — Ads AI Creator
Installation
Install via Smithery
npx -y @smithery/cli install ads-ai-creator-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/rocnubie/ads-ai-creator-mcp.git
cd ads-ai-creator-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"ads-ai-creator-mcp": {
"command": "node",
"args": [
"/absolute/path/to/ads-ai-creator-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://adsaicreator.com
Pricing: https://adsaicreator.com/pricing
Support: support@adsaicreator.com
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
3 toolsget_official_linksA
Return the canonical list of official links for Ads AI Creator (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. The verb 'Return' implies a read-only query, but it does not explicitly confirm no side effects or authorization needs. The description is adequate but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 15 words, front-loaded with the purpose. No wasted words; every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description is sufficient for a simple list retrieval tool. It names the resource and the categories of links. Could hint at output format but not necessary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema coverage is 100% trivially. According to the rubric, 0 parameters baseline is 4. The description adds no extra param info, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns the canonical list of official links for Ads AI Creator, specifically mentioning website, support, and docs. This distinguishes it from sibling tools list_styles and get_pricing, which deal with styles and pricing respectively.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide any guidance on when to use this tool vs alternatives, nor does it mention any prerequisites or exclusions. It implies usage for retrieving official links but lacks explicit context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_pricingA
Return the canonical pricing entry point for Ads AI Creator.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description alone must disclose behavior. It only states 'return' with no mention of side effects, authentication, rate limits, or output format. Minimal transparency for a read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single concise sentence, front-loaded, no redundant information. Efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description should clarify what the pricing entry point contains or returns. It is adequate for a simple tool but lacks output context that an agent might need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters with 100% schema coverage. The description adds no param info, which is acceptable since there are none. Baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool returns the canonical pricing entry point for Ads AI Creator, with a specific verb and resource. It is distinct from siblings (list_styles, get_official_links).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. The use case is implied but not stated. No when-not or exclusions provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_stylesA
Return the canonical list of image-generation styles or presets the site exposes. (Ads AI Creator)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It explicitly states the tool returns a list (read-only behavior), which is sufficient for a simple, non-destructive tool. No contradictions or missing critical info.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single concise sentence that front-loads the purpose. No extraneous words, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description fully covers the tool's purpose and behavior. The term 'canonical' implies authority and completeness, leaving no ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters. Per rubric, baseline is 4. The description adds no parameter-specific info as there are none, but that is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (Return) and the resource (canonical list of image-generation styles or presets). It distinguishes from sibling tools like get_pricing and get_official_links, which serve different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing the list of styles, but does not explicitly state when to use this tool versus alternatives, nor does it provide context such as prerequisites or typical workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
v0.1.0- First observed
get_official_links - First observed
get_pricing - First observed
list_styles
TDQS
Each tool targets a distinct aspect of the service: styles, pricing, and official links. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern ('list_styles', 'get_pricing', 'get_official_links'), providing a predictable and intuitive interface.
With only 3 tools, the server is tightly scoped to providing informational resources about the service. This is appropriate for a reference-style server and avoids unnecessary complexity.
The tools cover basic reference information (styles, pricing, links) but lack any functionality for actually creating or managing ads, which is the core purpose implied by 'Ads AI Creator'. This leaves a significant gap for agents expecting to perform creative tasks.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
Public, read-only MCP server for FarmNeural company facts, packages, and capabilities.
Read-only MCP server for RZ AI Labs — query its services, workshops, and contact info.
MCP server for Pixapi: check live credit pricing and balance, then generate images and video.
1
Related MCP Servers
- AlicenseBqualityBmaintenanceRead-only MCP server for Meta Ads that lists and reads ad accounts, campaigns, ad sets, ads, ad images, creatives, and fetches insights at various levels.14MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Muse AI Image's styles, pricing, FAQ, and official links to AI clients like Claude Desktop, enabling knowledge retrieval without API keys.3MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Producer AI's music generation workflows, pricing, documentation, FAQ, and official links. Enables AI clients to retrieve product knowledge without requiring API keys.3MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that exposes Meigen AI's image generation styles, pricing, FAQ, and official links to AI clients.3MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/ads-ai-creator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server