Docs

Use BulkAdKit from your AI assistant

Connect the AI assistant you already use, and ask it to find your creatives, write copy for each one and launch them. It works in one workspace, as you, with your role.

What it is

BulkAdKit is a connector for your own AI assistant, such as Claude, ChatGPT, Claude Code or Cursor. It uses the Model Context Protocol (MCP), the standard these assistants use to work with other apps.

BulkAdKit runs no AI model. Your assistant does the looking and the writing with its own model, on your plan with its provider. BulkAdKit gives it your library, your presets and your ad accounts, and runs the launches it creates.

What it can do

These are all the tools your assistant gets. The names are what you will see in your assistant.

Media library

list_media
List and search your images and videos by name, with type, size, dimensions, duration and date.
get_media
Look at one file. An image comes back as an image. A video comes back as its details, its thumbnail and a download link that expires after 15 minutes.
create_media_upload, finalize_media_upload
Upload a file from your computer, for tools that can run commands. A file already in the library is not uploaded twice.
import_from_drive, check_drive_import
Bring Google Drive files in by their file IDs, and follow the import. See Google Drive below.

Building a launch

list_presets
Read your presets. It cannot create, change or delete them.
list_ad_accounts, list_pages
List the Meta ad accounts connected to the workspace, and the Facebook Pages each one can advertise for.
find_ads
Find existing ads by name across your ad accounts, to use one as the template ad.
request_template_ad
Send you a link to pick the template ad yourself when the search finds several or none.
create_launch
Create a launch in one request: ad account, media, preset, template ad, campaigns and ad sets, targeting for new ad sets, the copy it wrote for each ad, enhancements and publishing options.

After a launch

get_launch
Check a launch's status, ad by ad, with how to fix what failed.
retry_launch
Retry failed ads. What was already created on Meta is reused, not duplicated.
stop_launch
Stop a queued or running launch. What was already created on Meta stays there.
get_handoff
Learn what you decided on a link it sent you.

What it can't do

  • Anything in Team, Billing or Settings: members, seats, payment, connections or Assistant autonomy.
  • Create, change or delete presets.
  • Roll back a launch, or use the duplicator.
  • Anything your own role in the workspace doesn't allow.
  • Extract frames or transcripts from videos. BulkAdKit doesn't process media for the assistant.

Google Drive

Your assistant finds the files with its own Google Drive connector. It shares them as “Anyone with the link”, BulkAdKit copies them in, and the assistant sets them back to private. BulkAdKit can't change sharing in your Drive, so the assistant is told which files are still shared until they aren't.

If link sharing is blocked, or you'd rather not share the files, the assistant sends you a link that opens Google's file picker with those files already selected. Confirm there to import them.

How launches stay safe

Each workspace has an Assistant autonomy setting that decides how far an assistant's launch goes without a person:

  • Review first (the default): The assistant sends you a link to check each launch. Nothing reaches Meta until you approve it, and then its ads are created paused.
  • Paused: The assistant's launches are created on Meta paused. Someone turns them on in Ads Manager.
  • Active: The assistant's launches go live on Meta as soon as they are created.

Only workspace owners and admins can change it, in Settings → AI assistant. The assistant can never change it, or override it for one launch.

Under Review first, the assistant gives you a Handoff: a link to the launch, laid out like the uploader's review step. Approve it, reject it, or open it in the uploader to change something first. A Handoff opens only when you are signed in as the person the assistant acts for, and it expires after 24 hours. A launch nobody approves in that time is discarded.

Launches made by an assistant are marked “via assistant” in Launches, with who it acted for and what it was asked.

Connecting

Every assistant connects to the same address:

Endpoint
https://bulkadkit.com/api/mcp

When you connect, your assistant opens a BulkAdKit sign-in:

  1. Enter your email. We send you a sign-in link.
  2. Open the link in the same browser, within 10 minutes.
  3. Pick the workspace the assistant works in, and allow it.

A connection is one person in one workspace. To use another workspace, connect again and pick it. The workspace's owners and admins see every connection in Settings → AI assistant.

The same address, the install links and the Claude Code command are in Settings → AI assistant once you are signed in.

Setup by assistant

BulkAdKit isn't listed in any assistant's app directory, so you add it yourself as a custom connector or MCP server.

Claude (claude.ai and Claude Desktop)

Custom connectors work on every Claude plan. On the Free plan you can add one custom connector. Connectors you add on claude.ai also work in Claude Desktop.

On Free, Pro and Max:

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it BulkAdKit and paste the endpoint as the URL. Click Continue.
  3. Leave authentication set to sign in. If Claude asks how to set up its OAuth client, choose Register automatically. Click Add.
  4. Sign in to BulkAdKit and pick your workspace.

On Team and Enterprise, an owner adds it first, in Organization settings → Connectors: click Add, then Custom → Web, and follow the same steps. Members then find BulkAdKit in Customize → Connectors and click Connect. Members can't add a custom connector themselves.

ChatGPT

ChatGPT supports custom MCP servers on Business, Enterprise and Edu, on the web. In those workspaces, admins decide who can add them.

  1. Go to chatgpt.com/plugins and click the plus button, then Add custom MCP server.
  2. Name it BulkAdKit. Under Connection, paste the endpoint.
  3. Choose OAuth for authentication. Read the warning and confirm with I understand and want to continue.
  4. Click Create as a plugin, check the tools it found, and install it.
  5. Sign in to BulkAdKit and pick your workspace.

ChatGPT asks you to confirm actions that change something, such as creating a launch.

Claude Code

Add the server, then sign in from a session:

Terminal
claude mcp add --transport http bulkadkit https://bulkadkit.com/api/mcp

Run /mcp in Claude Code, choose bulkadkit and sign in in your browser. Add --scope user to the command to use it in every project. To use an API key instead, see API keys.

Cursor

Or add it to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

mcp.json
{
  "mcpServers": {
    "bulkadkit": {
      "url": "https://bulkadkit.com/api/mcp"
    }
  }
}

Cursor asks you to sign in to BulkAdKit the first time it connects.

VS Code (GitHub Copilot)

Or run MCP: Add Server from the Command Palette, choose HTTP and paste the endpoint. As a file, it looks like this:

mcp.json
{
  "servers": {
    "bulkadkit": {
      "type": "http",
      "url": "https://bulkadkit.com/api/mcp"
    }
  }
}

VS Code asks you to sign in to BulkAdKit the first time it connects.

On Copilot Business and Enterprise, an admin has to turn on the “MCP servers in Copilot” policy first. It is off by default.

Devin Desktop (formerly Windsurf)

Add it to ~/.config/devin/mcp_config.json (on Windows, %AppData%\devin\mcp_config.json):

mcp_config.json
{
  "mcpServers": {
    "bulkadkit": {
      "url": "https://bulkadkit.com/api/mcp"
    }
  }
}

Then click Authenticate next to BulkAdKit in the MCP list and sign in. On Teams and Enterprise, an admin may need to allow MCP or add BulkAdKit to the team's MCP allowlist.

OpenAI Codex CLI

Terminal
codex mcp add bulkadkit --url https://bulkadkit.com/api/mcp
codex mcp login bulkadkit

The second command opens a browser to sign in to BulkAdKit.

Other MCP clients

Add a remote MCP server with the endpoint above, using the streamable HTTP transport. Sign in over OAuth if the client supports it, or send an API key.

Videos

Images come back to your assistant as images. There is nothing to set up.

A video comes back as its details, its thumbnail and a download link that expires after 15 minutes. To download it, your assistant's code sandbox must be allowed to reach this address:

Address to allow
9d003676303031cef4218edba5dcdfe4.us.r2.cloudflarestorage.com
  • Claude Team and Enterprise: an owner adds it in Organization settings → Capabilities, as one of the specific domains code execution may reach.
  • Other assistants: add it wherever the assistant lists the domains its sandbox may reach.
  • Tools that run commands on your own computer, such as Claude Code or Codex, can usually download it directly.

Without this step your assistant still sees the video's details and thumbnail.

API keys

For tools that don't sign in over OAuth, or scripts, use a workspace API key. Owners and admins create one in Settings → AI assistant → API keys. It is shown once, so copy it then.

A key acts as the person who created it, with their role, in the workspace it was created in. Your tool sends it as a header: Authorization: Bearer bak_your_key.

Claude Code
claude mcp add --transport http bulkadkit https://bulkadkit.com/api/mcp --header "Authorization: Bearer bak_your_key"
Cursor mcp.json
{
  "mcpServers": {
    "bulkadkit": {
      "url": "https://bulkadkit.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:BULKADKIT_API_KEY}"
      }
    }
  }
}
VS Code mcp.json
{
  "inputs": [
    {
      "type": "promptString",
      "id": "bulkadkit-key",
      "description": "BulkAdKit API key",
      "password": true
    }
  ],
  "servers": {
    "bulkadkit": {
      "type": "http",
      "url": "https://bulkadkit.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:bulkadkit-key}"
      }
    }
  }
}
Codex ~/.codex/config.toml
[mcp_servers.bulkadkit]
url = "https://bulkadkit.com/api/mcp"
bearer_token_env_var = "BULKADKIT_API_KEY"

Cursor and Codex read the key from the BULKADKIT_API_KEY environment variable. VS Code asks for it once and stores it.

Troubleshooting

The sign-in link didn't connect my assistant
Open the link in the same browser you connected from, within 10 minutes. If it was another browser or took longer, start connecting again from your assistant.
My organization won't let me add a custom connector
On Claude Team and Enterprise, an owner adds it in Organization settings → Connectors. On ChatGPT Business, Enterprise and Edu, ask your workspace admin. On Copilot Business and Enterprise, an admin turns on the “MCP servers in Copilot” policy. On Devin Desktop teams, an admin allows it in the team's MCP settings.
ChatGPT has no option to add a custom MCP server, or no developer mode
Your plan or workspace doesn't allow custom MCP servers. On Business, Enterprise and Edu, ask your workspace admin.
A video download fails with 403
Either the sandbox isn't allowed to reach the address above (see Videos), or the link is older than 15 minutes. Ask your assistant to open the video again for a fresh link.
My assistant says to sign in again
The connection was revoked, or you are no longer in that workspace. Connect again. If it used an API key, ask an owner or admin for a new one.
It's working in the wrong workspace
Remove the connection and connect again, and pick the right workspace.

Disconnecting

In BulkAdKit, open Settings → AI assistant and click Revoke next to the connection or key. Its next request is refused. Members can revoke their own connections; owners and admins can revoke anyone's.

You can also remove BulkAdKit from your assistant's connector or MCP settings.

Questions? [email protected]. Or sign in to find the address and install links in Settings.

AI assistants — BulkAdKit