Read B2B campaign performance
Report on account, campaign, and creative-level spend and available conversion metrics. The connector does not invent an ad-group level that LinkedIn does not have.
LinkedIn Ads MCP server
Your LinkedIn Ads.
In your AI agent.
Bring LinkedIn advertising reports and campaign controls to your AI agent. Review campaign groups, compare performance, and prepare changes without confusing a campaign with a complete creative setup.
Available locally with npm. Set up LinkedIn Ads
Built for this platform
What you can do with LinkedIn Ads MCP
Navigate campaign groups
List campaign groups and campaigns, including inactive ones. Select an existing group before preparing a paused campaign under it.
Make budget and status changes explicit
Preview daily or total budget updates. Campaign creation and activation require the advertiser’s explicit non-political confirmation; your agent should not infer that consent.
Know what the data means
Reporting has a 15,000-element response ceiling; ceiling results are flagged as potentially truncated. Campaign creation does not create creatives or lead forms. Political campaigning and group-shared dynamic-budget creation are not exposed.
Local setup · Bring your own credentials
Prefer local setup for LinkedIn Ads?
The npm CLI and MCP server run on your machine. You need Node.js 22.13 or newer, your own provider credentials, and permission to access the ad account.
01 Install Adport
npm install -g adport02 Connect LinkedIn Ads
adport connect linkedinThe local wizard imports your authorized token and checks account discovery. Access-only tokens require reauthorization when they expire; an account appearing in discovery does not by itself prove reporting permission.
03 Check your connection
adport doctor
adport accounts --provider linkedinCheck that the intended account appears before asking your agent to report on it. Never paste tokens, client secrets, or private keys into chat.
Register a local stdio client
For Claude Code:
claude mcp add --transport stdio adport -- adport mcpFor Cursor, merge this entry into your MCP configuration:
{
"mcpServers": {
"adport": {
"command": "adport",
"args": [
"mcp"
]
}
}
}ChatGPT uses an HTTP MCP endpoint instead of launching this local process.
Your tools. Your choice.
Use LinkedIn Ads from your agent.
Use the same Adport MCP endpoint and OAuth sign-in in each client. First connect your ad accounts in your Adport workspace. No platform secrets belong in chat.
Use LinkedIn Ads in ChatGPT
Enable developer mode, then open Settings → Apps → Create. Choose OAuth and use the endpoint below.
https://app.adport.dev/mcpScan the tools, finish Adport authorization, and enable the new app in your chat.
Developer mode and custom apps must be enabled for your ChatGPT account or workspace. In newer layouts, enable Developer mode under Settings → Security and login, then use the + button in Plugins to create your app. ChatGPT connects over HTTP; the local stdio command is for clients that can launch a process.
Use LinkedIn Ads in Codex
Run this command once and complete the browser authorization. Codex stores the MCP configuration and starts OAuth automatically.
codex mcp add adport --url https://app.adport.dev/mcpOnly if authorization did not start or you need to sign in again, run “codex mcp login adport”. Otherwise, check “codex mcp list” and ask Codex to list your ad accounts.
Use LinkedIn Ads in Claude Code
Add Adport at user scope so it is available across your local projects.
claude mcp add --transport http --scope user adport https://app.adport.dev/mcpRun /mcp inside Claude Code if the browser authorization does not open automatically.
Use LinkedIn Ads in Claude
Open Customize → Connectors → Add custom connector. Name it Adport and use the endpoint below.
https://app.adport.dev/mcpSelect Connect, approve the workspace, then enable Adport from the + menu in a conversation.
Use LinkedIn Ads in Cursor
Add this server to ~/.cursor/mcp.json, then restart Cursor.
{
"mcpServers": {
"adport": {
"url": "https://app.adport.dev/mcp"
}
}
}Approve the browser sign-in when prompted. Cursor will keep the OAuth session refreshed.
Use LinkedIn Ads in VS Code
Open the Command Palette and choose “MCP: Open User Configuration”, then add this server.
{
"servers": {
"adport": {
"type": "http",
"url": "https://app.adport.dev/mcp"
}
}
}Start the Adport server from VS Code and complete the browser authorization.
Use the MCP URL from Agent access if you run your own Adport deployment. Client settings, workspace permissions, and advertising-platform approvals still apply. The Cloud waitlist below is separate from these connection instructions.
You stay in control
A suggestion is not a live change.
The first mutation call returns a preview and a short-lived pending-operation token. Applying requires that token and the same arguments. Budget caps and protected accounts are checked by the policy engine; new campaigns are paused by policy.
Local operations are recorded in an append-only audit log. An approved preview is not a guarantee of provider acceptance, and a connected agent does not grant additional account permissions.
LinkedIn Ads MCP questions
Can LinkedIn reports be grouped by ad group?
No. LinkedIn has campaigns, campaign groups, and creatives, but no native ad-group entity. Adport rejects the unsupported ad_group report level instead of relabeling campaigns.
Can I use LinkedIn Ads locally without Adport Cloud?
Yes. Install Adport from npm, connect your own LinkedIn Ads credentials, and register the local MCP server with a stdio-compatible agent such as Claude Code or Cursor. Your provider may have its own approval, access, or billing requirements.
Why can I connect an account but not read a report or apply a change?
Account discovery, reporting, and mutations can require different permissions. Check the requested account, provider app scopes, advertiser eligibility, and environment. Start with adport doctor and the connection guide above. Do not bypass a denied operation by sharing secrets with the agent.