# Advibly MCP documentation

> Connect an AI agent to Advibly, discover its tools, and run complete creative production workflows over MCP.

Source: https://advibly.com/docs



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/mcp
```

The server uses **Streamable HTTP** and **OAuth 2.1**. It does not require an
API key.

## Choose the shortest path [#choose-the-shortest-path]

| Goal                                | Start here                                                                                                                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Connect an agent for the first time | [Connect over MCP](/agents/mcp)                                                                                                                                                                                          |
| Configure a specific client         | [Claude](/agents/clients/claude), [ChatGPT](/agents/clients/chatgpt), [Claude Code](/agents/clients/claude-code), [Cursor](/agents/clients/cursor), [VS Code](/agents/clients/vscode), or [Codex](/agents/clients/codex) |
| Choose or inspect a tool            | [Tool reference](/agents/tools), then the live `tools/list` schema                                                                                                                                                       |
| Complete a production job           | [Use cases](/use-cases/launch-campaign-image-set)                                                                                                                                                                        |
| Run a production recipe             | [Agent skills](/agents/skills)                                                                                                                                                                                           |
| Automate from a terminal            | [CLI quickstart](/cli)                                                                                                                                                                                                   |

<Cards>
  <Card title="Connect over MCP" href="/agents/mcp" description="Add the endpoint, complete OAuth, and make your first tool calls." />

  <Card title="Choose your client" href="/agents/clients/claude" description="Setup for Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex, and other MCP clients." />

  <Card title="Tool reference" href="/agents/tools" description="Every live Advibly MCP tool, grouped by capability." />

  <Card title="Use cases" href="/use-cases/launch-campaign-image-set" description="Complete jobs end to end: a campaign image set, a UGC ad, an ad recreation, a scheduled week, a clip run." />

  <Card title="Agent skills" href="/agents/skills" description="Install complete production recipes that orchestrate Advibly tools." />

  <Card title="CLI client" href="/cli" description="Call the same MCP server from a terminal or script." />
</Cards>

## The MCP workflow [#the-mcp-workflow]

<Steps>
  <Step>
    ### Connect and authorise [#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.
  </Step>

  <Step>
    ### Discover the live tools [#discover-the-live-tools]

    Use MCP `tools/list`. Tool schemas are the source of truth for arguments,
    defaults, supported models, and current capabilities.
  </Step>

  <Step>
    ### Resolve account context [#resolve-account-context]

    Start with `advibly_list_brands` and `advibly_check_credits`. Most generation
    tools need a real `brand_id` returned by the server.
  </Step>

  <Step>
    ### Generate and collect [#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.
  </Step>
</Steps>

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 [#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 [#machine-readable-documentation]

Every page has a markdown twin. Append `.md` to a docs URL, or request it with
`Accept: text/markdown`.

* [`/docs/llms.txt`](/llms.txt) indexes every MCP docs page.
* [`/docs/llms-full.txt`](/llms-full.txt) contains the complete MCP manual.
* [`advibly.com/agents.md`](https://advibly.com/agents.md) is the short product
  brief for an agent before its first call.