How to Connect LinkedIn Ads to Grok Bot

Grok Bot adds custom connectors when you ask in chat, so the quickest setup is one message. Already have an AdPlug account with LinkedIn Ads connected? Paste this into a chat with your Bot:

Add a custom MCP server called AdPlug - LinkedIn Ads at https://api.adplug.app/mcp/linkedin-ads

The Bot adds AdPlug and posts an Authorize card. Click Authorize, then Continue, and approve AdPlug's sign-in in your browser. Then ask it: List my LinkedIn ad accounts.

New to AdPlug? The same message works. AdPlug's sign-in screen lets you create a free account, and you connect LinkedIn Ads from your AdPlug dashboard. The five steps below walk through it with screenshots.

A Bot can work on LinkedIn Ads in two ways.

• Through its browser, or your exports. Every Bot has a cloud computer with a browser. You sign in to Campaign Manager there and the Bot clicks through it, or you hand it an export. The LinkedIn-ready template in Grok Bot's Marketplace, Paid Media Report Desk, works from the exports you give it.
• Through a connector. A connector hands the Bot LinkedIn's Marketing API instead of a screen. Reports come back as data, and a change is a named operation with exact values. Grok Bot's docs say to prefer a connector when one is available, because it is often more reliable than clicking through a website.

Grok Bot has no official LinkedIn Ads app in Connect apps. AdPlug connects LinkedIn Ads through LinkedIn's official Marketing API, so the Bot gets campaign data as numbers and never has to open Campaign Manager. You add it once and every Bot on your account can use it. Here's how the routes compare.

• Grok Bot. The desktop app runs on macOS, Windows, and Linux, and there are mobile apps for iPhone, iPad, and Android. Since 12 October 2026 it comes with The X Subscription on Premium, Super, and Ultra, team seats included (Plus and Free don't include it). Older routes still work: every paid individual Cursor plan and Cursor Teams, a linked SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription, or a seat on a self-serve Grok Business plan. There is also a free trial credit. Cursor's plans page has the current terms.
• An AdPlug account. The free plan is enough to set this up and test it: view only, 500 requests in the first 5 days and 50 a month after that, on one ad platform. AdPlug's LinkedIn Ads MCP is the server your Bot talks to.
• Access to the ad account. A LinkedIn profile with Campaign Manager access to the ad accounts you want the Bot to work on. Viewer access is enough for reporting.

Steps 1 and 2 happen in AdPlug. Steps 3 to 5 happen in Grok Bot. Allow about ten minutes the first time.

1. 1

   Create your AdPlug account

   Go to adplug.app/signup, sign in with Google or email, and follow the short onboarding. It ends on your AdPlug dashboard.

   

2. 2

   Connect LinkedIn Ads to AdPlug

   On the dashboard, click Connect LinkedIn Ads and sign in with the LinkedIn profile that has Campaign Manager access to the ad accounts you want your Bot to work on. Every account that profile can manage becomes available through the one connection.

   

   Already past onboarding? The Connections page has the same button.

   

3. 3

   Ask your Bot to add AdPlug

   Grok Bot calls its connectors apps and installs them as plugins from Connect apps in the sidebar (it used to be called Plugins). AdPlug isn't in that list yet, so you add it as a custom MCP server, and you do that by asking your Bot. Grok Bot's docs describe two kinds, Remote HTTPS and Command. AdPlug is the Remote HTTPS kind and signs you in through your browser, so there is no key to paste.

   Open a chat with your Bot and send:

   Add a custom MCP server called AdPlug - LinkedIn Ads at https://api.adplug.app/mcp/linkedin-ads

   Copy

   Keep the words custom MCP server in the message so the Bot uses this address rather than an app from Connect apps. The Bot adds it and posts an Authorize card. If it asks you to confirm the name and address first, say yes.

   https://api.adplug.app/mcp/linkedin-ads

   Copy

   

   

4. 4

   Authorise the connection

   Click Authorize on the card, then Continue in the dialog that opens. Grok Bot opens AdPlug's sign-in in your browser. Use the same email as your AdPlug account and click Approve. AdPlug's screen says Cursor wants access: Grok Bot connects apps through Cursor's backend, so that's the request to approve. If the card says it is waiting for authorization, choose Reopen to bring the browser tab back.

   

   Your browser then says the authorization is complete. If it asks to open Grok Bot, allow it. Back in Grok Bot, the card says Connected. You can also open Connect apps in the sidebar (on a phone, tap your avatar first) and check that AdPlug - LinkedIn Ads appears under Installed. Cursor's app help covers the other statuses you might see, such as Needs auth.

   

5. 5

   Test the connection

   In a chat with your Bot, ask:

   “List my LinkedIn ad accounts.”

   The Bot calls the linkedin_ads_list_accounts tool and returns the ad accounts you can access, with currencies and statuses. If your accounts are listed, the connection works end to end. If the Bot answers without AdPlug, type @ and pick AdPlug - LinkedIn Ads first.

   

LinkedIn's hierarchy is campaign group, then campaign, then creative (the ad). Name the level you mean and the Bot picks the right one. More copy-paste prompts live in the prompt playbooks.

Run campaigns, not just reports

Reports are the easy start. The same connection builds and changes campaigns on a paid AdPlug plan, and each of these asks for a preview before anything changes:

Thought Leader Ads work too, once the post's author has approved sponsorship in Campaign Manager: LinkedIn has no API for that step. The Thought Leader Ads guide covers the rest.

Grok Bot can also run work on a schedule. It calls this a routine: you ask the Bot in chat, say what it should do and when, and it keeps running in the cloud while your laptop is closed. A weekly report is the obvious first one:

Give the routine a time zone, the account it covers, and what to do when data is missing. A new routine waits for its next scheduled time, so open it and use Test to run it once now. Keep scheduled work read only. Cursor's help pages say an approval raised by a routine expires if nobody answers it in time, and the action doesn't run, so a scheduled job that needs a yes will usually just stop. Every run also uses AdPlug requests, and the free plan drops to 50 a month after the first 5 days, so a routine you keep wants a paid plan.

Routines worth setting up once the weekly report works:

• A morning check that only messages you when something's off: campaigns not delivering, rejected ads, leads or conversions gone quiet, broken landing pages, or spend and clicks far from normal.
• A monthly sweep of your competitors in the LinkedIn Ad Library: what they started running and what they seem to be testing.
• At the start of each month, a client-ready PDF report on last month's LinkedIn Ads: a short summary, results against the month before, the insights behind them, and what changes next.

AdPlug gives the Bot two tools for campaign changes: a preview tool that returns the exact change without applying it, and an execute tool that applies it. That covers campaign groups, campaigns, budgets, targeting, lead gen forms, and ads in nine formats, including Thought Leader Ads. The free plan is view only; creating and editing campaigns needs a paid AdPlug plan.

Grok Bot has its own approval prompts for sensitive actions, with Allow once, Always allow, and Deny. Do not rely on those alone for ad changes. Put the boundary in the request: ask for a draft that shows the current value, the proposed value, and the expected impact, and tell the Bot to wait. Answer with Allow once rather than Always allow, and add an Ask first rule under Auto-review for anything that edits campaigns.

Apps are shared across your account. Grok Bot's docs note that connected apps are not isolated to one Bot, and that all your Bots use the same cloud computer and app logins. Any Bot you create can reach the ad accounts this connection can see.

Teams are different. On a Team Bot, the Team Bots docs say a custom MCP server that signs in with OAuth uses the account of whoever is talking to the Bot. AdPlug signs in that way, so each teammate authorises once with their own AdPlug account. Approvals work as they do on any Bot, with one exception: in a conversation where nobody can answer the approval card, the Bot doesn't stop to ask and stays within the permissions it was set up with. So set the limit in AdPlug too: on the Max and Agency plans the owner can set each teammate to View only or Can edit per platform.

Report calls and executed changes are recorded in your AdPlug Usage and Audit Log, so you can check what a Bot did while you were away.

If you use Grok in the browser rather than Grok Bot, add AdPlug as a custom connector. On grok.com that takes three steps, and the Grok connector docs cover the rest:

1. Click Plugins in the sidebar, or go to grok.com/connectors.
2. Click New Connector, then select Custom.
3. Name it AdPlug - LinkedIn Ads, paste the AdPlug address above as the Server URL, click Add Connector, and complete the sign-in.

Connectors are available to all Grok users. On Grok Business and Enterprise a team admin provisions the connector first.

Click any item to expand the answer.

One address for every ad platform. Running more than LinkedIn Ads? Ask your Bot to add https://api.adplug.app/mcp instead, and the same Bot reaches Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, and Reddit Ads through one connection, once each platform is connected in AdPlug.

Want a whole team of Bots? Grok Bot for PPC sets out five: a specialist for each channel and a Watcher, each with a setup message to paste.

The same AdPlug account connects other platforms and assistants.

Email support@adplug.app with setup questions or bug reports. Most replies come back the same business day.