LinkedIn Ads MCP serverLinkedIn Ads MCP Server for any AI client.
NotFair connects your LinkedIn Ads account to Claude, Codex, Cursor, and any MCP client — 41 tools to inspect campaigns, find issues, and stage approved changes.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/linkedin_adsLive tools
41New to MCP? Read the spec at modelcontextprotocol.io.
Tools exposed
41What your AI client can read and change
Read tools provide live ad-account context. Write tools propose changes — every write requires explicit human approval before it hits the LinkedIn Marketing API.
| Tool | Type | What it does |
|---|---|---|
runScript | Read | Sandboxed JS over the LinkedIn Marketing API — fan out parallel calls in one pass for audits and analysis. |
getAnalytics | Read | Performance analytics with all pivots: spend, impressions, clicks, CTR, CPM, conversions, member company and industry demographics. |
listCampaigns | Read | List campaigns with status, objective, budget, bid, and schedule. |
listCampaignGroups | Read | Campaign group details: status, budget envelope, and campaigns underneath. |
listCreatives | Read | Creatives with status, parent campaign, and creative content. |
getAccount | Read | Account snapshot: currency, status, and account-level settings. |
| and more | ||
Ready to wire up your client?
Sign in to NotFair, link your LinkedIn ad accounts, then paste a config above into your MCP client.
FAQ — NotFair LinkedIn MCP server
Common questions about authenticating, configuring, and using the NotFair LinkedIn Ads MCP server.
It's a hosted Model Context Protocol server that exposes your LinkedIn ad accounts to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools propose fixes that you approve in chat.
Any client that speaks the MCP Streamable HTTP transport — Claude.ai (Web, Desktop, Cowork), Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients. The server URL is the same; only the client-side config differs.
No. The LinkedIn Ads MCP server is hosted at https://notfair.co/api/mcp/linkedin_ads. You just point your client at it and authenticate.
OAuth 2.0 with PKCE is the recommended flow — Claude.ai and Codex run it automatically. For clients that don't support OAuth, you can use a Bearer token via the Authorization header. Generate either at notfair.co/connect/linkedin-ads.
Yes. Connecting to NotFair's LinkedIn MCP is free with no credit card. Paid plans unlock higher usage limits and team features.
Only with your explicit approval. Write tools propose changes (pause campaigns, adjust budgets, update targeting, etc.), the client surfaces them, and you confirm before anything hits the LinkedIn Marketing API. New campaigns and campaign groups start as drafts, so nothing serves until explicitly activated. Read access is unrestricted; write access is gated.
LinkedIn Ads follows a four-level hierarchy: the ad account holds campaign groups, campaign groups hold campaigns, and campaigns deliver creatives. The MCP exposes everything LinkedIn surfaces through the Marketing API: campaign groups, campaigns, creatives, targeting, analytics, audiences, conversions, and lead forms.
Per-client setup guides
Walkthroughs for each supported client.
Claude × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in Claude.
Read setup guideClaude Code × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in Claude Code.
Read setup guideCodex × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in Codex.
Read setup guideCursor × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in Cursor.
Read setup guideOpenClaw × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in OpenClaw.
Read setup guideHermes × LinkedIn Ads
Set up the NotFair LinkedIn Ads MCP in Hermes.
Read setup guide