Advibly MCP documentation
Connect an AI agent to Advibly, discover its tools, and run complete creative production workflows over MCP.
Advibly is a remote Model Context Protocol server for producing branded images, videos, audio, carousels, and social campaigns. Connect once, authorise with OAuth, and your AI client can work with the brands, assets, credits, and projects attached to your Advibly account.
https://advibly.com/mcpThe server uses Streamable HTTP and OAuth 2.1. It does not require an API key.
Choose the shortest path
| Goal | Start here |
|---|---|
| Connect an agent for the first time | Connect over MCP |
| Configure a specific client | Claude, ChatGPT, Claude Code, Cursor, VS Code, or Codex |
| Choose or inspect a tool | Tool reference, then the live tools/list schema |
| Complete a production job | Use cases |
| Run a production recipe | Agent skills |
| Automate from a terminal | CLI quickstart |
Connect over MCP
Add the endpoint, complete OAuth, and make your first tool calls.
Choose your client
Setup for Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex, and other MCP clients.
Tool reference
Every live Advibly MCP tool, grouped by capability.
Use cases
Complete jobs end to end: a campaign image set, a UGC ad, an ad recreation, a scheduled week, a clip run.
Agent skills
Install complete production recipes that orchestrate Advibly tools.
CLI client
Call the same MCP server from a terminal or script.
The MCP workflow
Connect and authorise
Point a Streamable HTTP client at https://advibly.com/mcp. The client opens
Advibly's OAuth flow and stores the resulting token.
Discover the live tools
Use MCP tools/list. Tool schemas are the source of truth for arguments,
defaults, supported models, and current capabilities.
Resolve account context
Start with advibly_list_brands and advibly_check_credits. Most generation
tools need a real brand_id returned by the server.
Generate and collect
Generation calls wait briefly. A fast job returns completed with its result;
a slower job returns pending with a generation_id. Call
advibly_get_generation only when a later step needs the finished URL.
The connection is ready when advibly_list_brands returns the account's real
brand ids. A production is complete when every requested deliverable is
completed, collected for the user, and—when it used a project—the strongest
final is set as the project cover.
What the server exposes
| Capability | MCP tools cover |
|---|---|
| Brand context | Brand onboarding, research, identity, products, and assets |
| Generation | Images, video, talking actors, carousels, voiceover, and music |
| Post-production | Video analysis, stitching, subtitles, and composition renders |
| Organisation | Generations and projects |
| Distribution | Social publishing, scheduling, analytics, and comment-to-DM automation |
Machine-readable documentation
Every page has a markdown twin. Append .md to a docs URL, or request it with
Accept: text/markdown.
/docs/llms.txtindexes every MCP docs page./docs/llms-full.txtcontains the complete MCP manual.advibly.com/agents.mdis the short product brief for an agent before its first call.