Skip to content
Ad Army for your AI assistant

Your next campaign.Starts in a conversation.

Give your assistant a creative workspace. Turn a brief into images, videos, and finished ads — with your assets, on your boards.

Connect withCodexClaude Codeany compatible MCP client

One conversation. A whole creative workflow.Example workflow
The brief

Use the serum product photo in my Assets to create three ad concepts: warm morning light, a clean studio shot, and a dramatic close-up. Keep the bottle consistent. Save them to a new Playground and estimate the credits before generating.

Your assistant

Start with your product reference, explore three visual directions, and bring the results together on one board.

  • Find product assets
  • Estimate generation
  • Create on your board
Ad Army · PlaygroundIn your workspace
Same product. Three directions.
Variation 1Variation 01
Variation 2Variation 02
Variation 3Variation 03
The creative

One product. More possibilities.

Made for the work you do

A creative team at your prompt.

Start with an idea, a product shot, or the assets you already have. Here are a few things to ask your assistant.

A small setup. A bigger toolkit.

Meet your new creative connection.

Connect Ad Army once. Bring your workspace into the conversations where your ideas start.

1

Add Ad Army to your assistant

Run these commands in your terminal to add Ad Army and sign in. The first command may start sign-in automatically.

Terminal
codex mcp add adarmy --url https://app.ad.army/api/mcp
codex mcp login adarmy --scopes workspace:read,assets:write,playground:write,media:analyze,media:generate,media:compose
2

Make it your workspace

Sign in to Ad Army, choose a workspace, and approve the requested capabilities. Set a maximum credit allowance per operation.

3

Start with a brief

Ask your assistant to find your assets, create a Playground, or make your next ad. Your generated media is saved to your workspace.

You’ll need an Ad Army account. Creating media uses your workspace credits.

Manage connected assistants

Your workspace. Your call.

01

The assets you already use

Work with your brand kit and asset library. Generated media lands back in Ad Army.

02

A budget you decide

Estimate generation and render costs before starting. Set a credit limit for each operation.

03

Access you control

Choose a workspace and permissions at sign-in. Revoke a connection whenever you need to.

A few things to know.

What is Ad Army MCP?

MCP (Model Context Protocol) connects your AI assistant to tools in Ad Army. It lets the assistant work with your workspace assets, generate media, analyze footage, assemble videos, and collaborate on Playground boards through a conversation.

Which assistants can I connect?

The setup above includes Codex and Claude Code. Other clients can connect if they support remote MCP servers over HTTP and OAuth sign-in. The setup and available permissions depend on the client.

Do I need an API key?

No. Sign in with your Ad Army account through the browser and authorize your workspace. You can manage and revoke connections from Connected assistants in your workspace settings.

How do credits work?

Generation, paid analysis, and rendering use your workspace credits. Searching assets and organizing boards do not spend credits. You set a maximum allowance per operation when connecting, and your assistant can estimate generation and composition costs before starting.

Where does the work go?

Generated images, videos, voiceovers, music, and rendered compositions are saved as workspace assets. When you ask your assistant to generate in a Playground, prompts and results also appear on that board. Your team can open the same board in Ad Army and continue there.

Can my assistant use every feature in Ad Army?

MCP exposes a specific set of creative tools. It supports text, image generation and editing, text-to-video and image animation, voiceovers, instrumental music, media analysis, board collaboration, and video assembly. Model settings vary; your assistant can check the available models and supported operations before starting.