> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install the buyer plugins in Claude

> Which Apostra plugins a buyer installs in Claude, Cowork, or Claude Code, how to install and update them, and how to check that Claude is using them.

Apostra publishes its buyer workflows as Claude plugins. A plugin adds the
Apostra connection and the skills that tell Claude how to run a workflow
correctly: set up the account, build a campaign, upload creatives, launch, and
read delivery. Install them so Claude follows Apostra's workflow instead of
working it out from the tool list.

The plugins are in the public marketplace
[apostra-public/apostra](https://github.com/apostra-public/apostra). They work
in Claude (web and desktop), Cowork, and Claude Code.

## Which plugins to install

A buyer installs these four:

| Plugin | What it is for | Skills it adds |
| - | - | - |
| `buyer-account-setup` | Get the buyer account ready to transact: terms, billing authority, provider connections, and readiness blockers. | `get-account-ready-to-buy` |
| `buyer-campaign-management` | Create a campaign from a brief, request proposals, stage media buys, launch, and manage a live campaign. | `set-up-a-campaign`, `manage-a-campaign`, `buy-from-seller`, `set-up-an-event-source` |
| `buyer-creative-management` | Inspect tag sheets and generate campaign creatives. | `inspect-tag-sheet`, `generate-campaign-creatives` |
| `buyer-reporting` | Set up conversion tracking for delivery and reporting. | `set-up-an-event-source` |

The marketplace also lists plugins for other jobs. The `amc-` plugins are for
media companies selling on Apostra, `amc-self-serve-buyer` is a bundle a media
company puts in its own plugin, `sales-agent-testing` tests a sales agent, and
`apostra-developer` is for building software on Apostra (see the
[developer quickstart](https://docs.apostra.com/v3/quickstart.md)). A buyer does not need them.

A plugin only adds instructions. What you can do still depends on your account
and its permissions, and every change that commits spend still asks you to
confirm it.

## Claude and Cowork

1. Open **Customize > Plugins**, select **Add**, then **Add marketplace**.
2. Enter `https://github.com/apostra-public/apostra` and add it.
3. Install each of the four buyer plugins above.
4. Open a plugin's **Connectors** tab and connect Apostra. Sign in when your
   browser opens. Installing a plugin does not sign you in.

Skills need **Code execution and file creation** turned on under
**Settings > Capabilities**. On a Team or Enterprise plan, an owner can turn off
user-added plugins and skills, or code execution, for the whole organization.
If **Add** is missing or the skills do not load, ask your Claude owner.

The plugins connect to `https://api.apostra.com/mcp/v3`. If you already added
Apostra as a custom connector (see [MCP client setup](https://docs.apostra.com/v3/client-setup.md#claude-and-cowork)),
you do not need both. Keep one Apostra connection so you always know which
account Claude is signed in to.

## Claude Code

Run these inside a Claude Code session:

```text theme={null}
/plugin marketplace add https://github.com/apostra-public/apostra.git
/plugin install buyer-account-setup@apostra
/plugin install buyer-campaign-management@apostra
/plugin install buyer-creative-management@apostra
/plugin install buyer-reporting@apostra
```

Complete the sign-in when Claude Code first calls Apostra.

## Keep the plugins current

Apostra updates the skills as the product changes. In Claude Code, run
`/plugin marketplace update apostra` to get new versions, or open `/plugin`,
select the `apostra` marketplace on the **Marketplaces** tab and turn on
auto-update. In Claude and Cowork, update from **Customize > Plugins**.

## Use one set of Apostra instructions

Turn off any other skills you use for Apostra: ones your team wrote, or older
copies of Apostra skills you uploaded yourself. When two sets of instructions
disagree, Claude can follow the wrong one, for example by reporting creatives
as saved when they were not.

* **Claude and Cowork:** turn the skill off or remove it in **Customize > Skills**.
* **Claude Code:** open `/skills`, select the skill and turn it off. To turn off
  a whole plugin, use the **Installed** tab in `/plugin` or
  `claude plugin disable <plugin>@<marketplace>`.

## Check that Claude is using them

Start a new conversation and ask:

```text theme={null}
Which Apostra skills do you have loaded? Then show me my current Apostra
account and anything blocking it from buying, without changing anything.
```

Claude should name the skills in the table above and read your account with
`get_status`. If it names other skills for Apostra work, turn those off. If it
cannot reach Apostra, connect the plugin's connector again and sign in.

To continue, see [Manage ads](https://docs.apostra.com/v3/manage-ads.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.