mcpField
L
LinkedIn Company Admin MCP

LinkedIn Company Admin MCP

Local
github.com/negrueuSocial Media0Updated 28w ago

About LinkedIn Company Admin MCP

LinkedIn Company Admin MCP is a browser-based server for administering LinkedIn Company Pages, with tools for analytics, page details, posts, and follower growth. It also includes personal-profile tools for employee-advocacy workflows; browser automation may carry account restriction risks noted by the project.

Key features

  1. 01Read page data and analytics
  2. 02Edit page details and branding
  3. 03Create, edit, schedule, and manage posts
  4. 04Invite connections to follow the page
  5. 05Bridge personal posts and page activity
  6. 06Interactive login with persistent browser session

Use cases

  1. 01Review Company Page metrics and mentions
  2. 02Schedule and revise posts before a launch
  3. 03Invite first-degree connections to follow a page
  4. 04Tag a Company Page in a personal post

MCP support

Exposes 24 tools to MCP clients for LinkedIn Company Page administration and employee-advocacy workflows. It automates a visible Chromium browser session; the README warns that LinkedIn may restrict accounts for automated access.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"linkedin-company-admin": {
"command": "uvx",
"args": [
"linkedin-company-admin-mcp"
]
}
}
}
Run commanduvx linkedin-company-admin-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypilinkedin-company-admin-mcp

Tools

24

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

linkedin-company-admin-mcp

Language: English - Romana

PyPI Python License: MIT CI Code style: ruff Checked with mypy

MCP server for LinkedIn Company Page administration. Read analytics, manage posts, edit page details, grow followers, and bridge your personal profile for employee advocacy workflows.

Complementary to stickerdaniel/linkedin-mcp-server. Stickerdaniel's project covers personal LinkedIn use cases (feed, messaging, search). This project fills the gap nobody else fills: full administrative control of your LinkedIn Company Page, plus a small set of personal-profile bridge tools used exclusively for employee-advocacy flows.

⚠️ Terms of Service & account risk. LinkedIn's User Agreement prohibits automated access to the platform. This server drives a real browser session on your behalf and LinkedIn may detect, rate-limit, or permanently restrict accounts that use it - including loss of access to the Company Page itself. Use at your own risk. Do not use this on a personal or business account you cannot afford to lose. There is no way for the authors to recover a restricted account for you. Prefer LinkedIn's Community Management API if you qualify for it.

🔐 Security note - session dir equals credentials. "No credentials stored" means this server never asks for your password and never puts one in a config file. It does not mean the profile directory is safe to share. After login, ~/.linkedin-company-admin/profile contains LinkedIn session cookies that are functionally equivalent to your password + 2FA combined. Anyone who reads that directory gets full admin access to your account and Company Page. In particular: do not sync this directory to OneDrive / iCloud / Dropbox / any cloud backup. Keep it on local disk only, on a machine you trust.

Why this project

LinkedIn's official Community Management API is invite-only. Scraping personal profiles is already well covered. What was missing: a stable, browser-first MCP that lets a page admin (or their assistant LLM) read analytics, draft posts, edit the about section, invite followers, and tag the page from a personal post - without any of it touching a stored password.

Features at a glance

  • 24 MCP tools across 6 categories - see Tool reference below.
  • Zero credentials on disk. Interactive login via a visible Chromium window; session lives in a persistent profile directory (chmod 0o700 on Unix).
  • Stealth Chromium via Patchright (anti-detection fork of Playwright).
  • Provider abstraction (AdminProvider, PostsProvider) so a future Community Management API backend can slot in without rewriting tools.
  • Rate limiting actually applied (not just imported) - every write tool has a conservative hourly cap.
  • aria-label / role / innerText selectors only - no obfuscated CSS class hashes. When LinkedIn ships a new UI, only selectors/__init__.py changes.
  • No god-files (cap ~300 LOC per file), type-checked with mypy, linted with ruff.

Installation

Option 1: uvx (recommended)

Published on PyPI as linkedin-company-admin-mcp.

uvx linkedin-company-admin-mcp@latest --login

Then add to your Claude Desktop config (~/.config/Claude/claude_desktop_config.json or platform equivalent):

{
  "mcpServers": {
    "linkedin-company-admin": {
      "command": "uvx",
      "args": ["linkedin-company-admin-mcp@latest"]
    }
  }
}
Option 2: Local development
git clone https://github.com/negrueu/linkedin-company-admin-mcp.git
cd linkedin-company-admin-mcp
uv sync
uv run linkedin-company-admin-mcp --login
Option 3: Docker
docker build -t linkedin-company-admin-mcp .
docker run --rm -it \
  -v linkedin_profile:/home/mcp/.linkedin-company-admin \
  linkedin-company-admin-mcp --login

First-time login

Credentials are never stored in this server. Login is interactive:

uvx linkedin-company-admin-mcp --login

A visible Chromium window opens. Sign in to LinkedIn normally (including 2FA). The persistent browser profile is saved to ~/.linkedin-company-admin/profile (chmod 0o700 on Unix). All subsequent MCP calls reuse this session automatically.

To log out: uvx linkedin-company-admin-mcp --logout (wipes the profile directory).

Tool reference

Full argument lists and examples live in docs/TOOL_REFERENCE.md. Summary:

Session (3)
ToolPurpose
session_statusIs the persistent profile live and logged in?
session_warmupPre-open the browser + /feed/ to reduce first-call latency.
session_logoutClose the browser and wipe the profile directory.
Company read (6)
ToolPurpose
company_read_pageName, tagline, followers, about, industry, website.
company_list_postsRecent posts with URN, text, reactions, comments.
company_list_followersFollowers list (admin-only; paginated).
company_list_mentionsPosts that mentioned the page (admin notifications).
company_manage_adminsList admins and their roles.
company_analyticsFollowers / posts metrics for a 7d / 28d / 90d window.
Company admin write (3)
ToolPurpose
company_edit_aboutUpdate the About section (with tagline fallback).
company_edit_logoUpload a new logo (and optional banner).
company_update_detailsWebsite, industry, size, specialties.
Company content (6)
ToolPurpose
company_create_postPublish a text post (optional link / image).
company_edit_postReplace the body of an existing post.
company_delete_postPermanent delete - see docs/RCA_DELETE_POST.md.
company_schedule_postPublish at a future ISO-8601 datetime.
company_reply_commentReply as the page to a comment on one of your posts.
company_reshare_postReshare another post on the page, optional commentary.
Company growth (2)
ToolPurpose
company_invite_to_followSend follow invitations to 1st-degree connections (LinkedIn caps 250/month).
company_list_scheduledList posts queued for future publication.
Personal -> Company bridge (4)
ToolPurpose
personal_tag_companyPublish a personal post that @-mentions the page.
personal_reshare_company_postReshare a page post on your personal profile.
personal_comment_as_adminComment on a page post as the page (or as you).
personal_read_company_mentionsScan your recent activity for posts that tag the page.

Security model

  • No email/password handling. Credentials never touch this code.
  • Session state lives in a persistent browser profile directory, isolated per OS user, outside the repo.
  • .env contains only configuration (log level, transport, tool timeout). No secrets.
  • The profile directory is chmod'd to 0o700 on first login (Unix).
  • Rate limiting is enforced per-tool; the caps are conservative by design, tuned to what LinkedIn tolerates rather than what it allows.

Supported workflows

  • Draft, review, and publish a post on your company page from Claude.
  • Tag the page from a personal post and track how the community responds.
  • Audit who has posted about your page this week (admin mentions).
  • Invite a batch of 1st-degree connections to follow the page, stopping at LinkedIn's monthly quota.
  • Run a full CRUD pass on scheduled posts before a launch.

See docs/TOOL_REFERENCE.md for end-to-end examples.

Troubleshooting

Selector drift, captcha, rate limits, cookie expiry and Chromium launch issues are all covered in docs/TROUBLESHOOTING.md.

Contributing

Contributions welcome. See docs/CONTRIBUTING.md for local setup, test layout, and the workflow for adding a new tool.

Status

Under active development. See CHANGELOG.md for version history and issues for the roadmap.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.