Connect LinkedIn to Claude

The four steps

1. 1

   Create a Blabigo account and connect LinkedIn

   Sign up free, then connect your LinkedIn profile — and any company Pages you manage — from the dashboard. This is the normal LinkedIn authorization screen: you are granting Blabigo access to your own account, exactly as you would for any other approved app. Claude never sees your LinkedIn credentials, because it never handles them.

2. 2

   Add the connector in Claude

   In Claude Desktop or the Claude web app, open settings and add a custom connector pointing at the Blabigo MCP endpoint. In Claude Code, run the one-line command instead. Either way the only thing you paste is the endpoint URL.

3. 3

   Approve the connection in your browser

   Claude runs an OAuth authorization-code flow with PKCE against the endpoint. A browser window opens, you sign in to Blabigo and approve the connection, and the client stores a scoped token. No API key is created and nothing permanent is copied between applications.

4. 4

   Check that the tools are there

   Ask Claude to list your connected LinkedIn accounts. If it comes back with your profile and any Pages you manage, the connection works end to end — that single answer exercises authentication, scope resolution and the LinkedIn API in one call.

The exact configuration

Claude Code

claude mcp add --transport http blabigo https://studio.blabigo.ai/api/mcp/linkedin

Claude Desktop and other config-file clients

{
  "mcpServers": {
    "blabigo": {
      "url": "https://studio.blabigo.ai/api/mcp/linkedin"
    }
  }
}

Fallback: run it locally over stdio

For clients that cannot reach a remote server or do not implement OAuth. Create an API key in the dashboard first, then:

{
  "mcpServers": {
    "blabigo": {
      "command": "npx",
      "args": ["-y", "@blabigo/cli", "mcp"]
    }
  }
}

What to say once it is connected

The connection is only worth having if you know what to ask for. These work from a standing start:

• “List my connected LinkedIn accounts.”
• “How did my posts perform over the last 30 days? Which one got the most impressions?”
• “Draft a post about what we learned migrating our blog off WordPress. Match the voice of my last five posts.”
• “Put that on the queue for Thursday at 9am, then show me everything scheduled for next week.”
• “Actually, tighten the opening of that scheduled post and drop the last line.”

When it does not work

Frequently asked questions

How do I connect LinkedIn to Claude?

Create a free Blabigo account and connect your LinkedIn profile to it, then add Blabigo's MCP endpoint as a custom connector in Claude. Claude opens a browser window for you to approve the connection, and the LinkedIn tools appear in your conversation. The whole process takes about two minutes and requires no code.

Is there an official LinkedIn MCP server from LinkedIn?

No. LinkedIn does not publish one. Blabigo's MCP server is an independent integration that works through LinkedIn's official API using the account access you granted, which is why it can operate without scraping or automating the website.

Does this work with Claude Code as well as Claude Desktop?

Yes. Claude Code adds the server with a single command, Claude Desktop and the web app use the custom-connector screen, and any client that reads an mcpServers config file can take the same URL. Clients that cannot do remote servers or OAuth can run the Blabigo CLI locally over stdio instead.

Do I need an API key?

Usually not. Most clients complete OAuth from the endpoint URL alone, which is both easier and safer than a key, since the token is scoped and tied to the client. Keys exist for scripts, CI and self-hosted agents that cannot run a browser flow.

Can Claude post to LinkedIn immediately once connected?

No. Even fully connected, Claude can only create drafts and queue them for a future time, at least 60 seconds out. Blabigo's scheduler publishes them. You can read anything an agent queued and cancel it before it goes out.

How do I disconnect it?

Remove the connector in Claude, and revoke the client from the Blabigo dashboard so the token stops working regardless of what still holds it. If you used an API key instead, delete the key — that immediately invalidates every session using it.