Blabigo LinkedIn MCP Server

by blabigo Your server? Claim it

answering

Blabigo LinkedIn is answering right now. Last checked 6 min ago.

LinkedIn analytics, media uploads and scheduling for AI agents. Agents queue; Blabigo publishes.

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

129 ms

Response time

average over 24h

authentication required

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Blabigo LinkedIn every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://studio.blabigo.ai/api/mcp/linkedin

~/.codex/config.toml

[mcp_servers.linkedin-agent]
url = "https://studio.blabigo.ai/api/mcp/linkedin"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "linkedin-agent": {
      "type": "http",
      "url": "https://studio.blabigo.ai/api/mcp/linkedin"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://studio.blabigo.ai/api/mcp/linkedin	streamable-http	needs auth	131 ms	6 min ago

Alternatives to Blabigo LinkedIn

same job, measured the same way

Bynor

by bynor

Social media for brands: editorial plans, on-brand images, scheduling, publishing and analytics.

answering

BAMF.ai

by bamf

LinkedIn and X content, scheduling, analytics and outreach agent for founders, via your BAMF login.

148 tools answering

Maeve Social

by maevesocial

A hosted MCP server for planning, scheduling, media, analytics, and social publishing.

answering

Schedii

by schedii

Publishing, scheduling, analytics, ads, AI, sites, flows... everything. Anywhere, anytime, for all.

answering

2pr.io

by 2pr

Draft, schedule and publish LinkedIn posts, reply to comments and read analytics via 2pr.io.

answering

Blotato

by blotato

Social media APIs for scheduling, analytics, and DM automation.

answering

Writio

by alexlarcheveque

LinkedIn-native AI content creation, scheduling & analytics via MCP.

39 installs/wk local only

Swonkie

by swonkie

Manage social media from your AI client: analytics, posts, scheduling, media, and AI images.

answering

Blabigo LinkedIn — questions

Answers built from our own checks of this server.

Why is there no tool list for Blabigo LinkedIn?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Blabigo LinkedIn working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 129 ms. The bar chart above shows every period we have measured.

How do I connect Blabigo LinkedIn?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Blabigo LinkedIn need an API key?

Yes. Every time we knock, Blabigo LinkedIn answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Blabigo LinkedIn?

It answers our handshake in 129 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.