Skip to main content
The LinkedIn MCP server lets you govern access to LinkedIn — member profiles, organization pages, social posts, and ads data — as tools your AI clients can call through C1. LinkedIn authenticates with per-user OAuth. Each person authorizes with their own LinkedIn account, so every tool call runs under that user’s LinkedIn identity and permissions. For a deeper comparison of shared versus per-user credentials, see Configure authentication.

How C1 connects to LinkedIn

C1 hosts the LinkedIn MCP server, so your users’ AI clients only ever see MCP tools — they never call LinkedIn directly. When an AI client calls one of these tools, C1 makes the matching request to the LinkedIn API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call LinkedIn on your users’ behalf.

Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • A LinkedIn account with permission to create an app in the LinkedIn Developer Portal, linked to a LinkedIn Page you administer.
If you don’t see LinkedIn in your MCP server catalog, contact the C1 support team to enable it for your tenant.

Create a LinkedIn app

Create an app in the LinkedIn Developer Portal to generate the OAuth credentials C1 uses to connect.
1
In the LinkedIn Developer Portal, select Create app. For details, see LinkedIn’s Authenticating with OAuth 2.0 documentation.
2
Give the app a recognizable name such as C1.
3
Associate the app with a LinkedIn Page you administer.
4
On the app’s Settings tab, select Verify, then Generate URL and send the link to your Page’s super admin. The super admin must approve the request to verify the app. See LinkedIn’s app verification documentation.
5
On the Auth tab, set the authorized redirect URL exactly to whichever matches your C1 tenant’s domain:
  • Default instance: https://accounts.conductor.one/auth/callback
  • EU data residency instance: https://accounts.c1eu.ai/auth/callback
6
On the Products tab, request the two products listed in LinkedIn scopes below. LinkedIn grants a scope only through the product that includes it.
7
Copy the client ID and client secret from the Auth tab.

LinkedIn scopes

C1 requests these scopes automatically. LinkedIn returns an Invalid scope error if C1 requests a scope that your app’s products don’t grant, so both products below must be approved on your app before anyone connects.
Sign In with LinkedIn using OpenID Connect is self-service. Advertising API requires LinkedIn’s approval. Don’t add the Community Management API product to this app: LinkedIn requires it to be the only product on an app, and the Advertising API product already grants the organization scopes C1 requests. Members need the matching Company Page or ad account role to act on that data.
Members consent to all requested scopes together and can’t pick individual scopes. Scope changes take effect the next time a user connects, so if you change your app’s products after users have connected, each user must reconnect their LinkedIn account.

How LinkedIn credentials are shared

Each user authorizes with their own LinkedIn account, so tool calls run under that user’s LinkedIn identity and inherit only the access they already have. LinkedIn attributes each action to the individual user. For how shared and per-user credentials work across MCP servers, see Configure authentication.

Register the LinkedIn MCP server in C1

With your app ready, register the server and provide your credentials.
1
Follow Register an MCP server and select LinkedIn from the catalog.
2
When you configure authentication, choose per-user OAuth and enter your app’s client ID and client secret.
3
Enter the LinkedIn API Version in YYYYMM format, for example 202603. See LinkedIn’s API versioning documentation for supported versions.
4
Save your changes. The first time a user calls a LinkedIn tool from their AI client, they’re prompted to connect their LinkedIn account.

Discover and govern tools

After you register the server, C1 runs tool discovery against LinkedIn. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification. Before anyone can call a LinkedIn tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your LinkedIn credentials when an approved user successfully calls a LinkedIn tool from their AI client.

Manage your LinkedIn credentials

  • Rotate the client secret in your LinkedIn app under the Auth tab, then update the secret on the server’s authentication settings in C1.
  • Adjust access by requesting or removing products on the app’s Products tab in LinkedIn.