Skip to main content
Glama
linkedin-company-admin-mcp

linkedin-company-admin-mcp

by negrueu

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.

Related MCP server: linkedin-pages-mcp

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

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)

Tool

Purpose

session_status

Is the persistent profile live and logged in?

session_warmup

Pre-open the browser + /feed/ to reduce first-call latency.

session_logout

Close the browser and wipe the profile directory.

Company read (6)

Tool

Purpose

company_read_page

Name, tagline, followers, about, industry, website.

company_list_posts

Recent posts with URN, text, reactions, comments.

company_list_followers

Followers list (admin-only; paginated).

company_list_mentions

Posts that mentioned the page (admin notifications).

company_manage_admins

List admins and their roles.

company_analytics

Followers / posts metrics for a 7d / 28d / 90d window.

Company admin write (3)

Tool

Purpose

company_edit_about

Update the About section (with tagline fallback).

company_edit_logo

Upload a new logo (and optional banner).

company_update_details

Website, industry, size, specialties.

Company content (6)

Tool

Purpose

company_create_post

Publish a text post (optional link / image).

company_edit_post

Replace the body of an existing post.

company_delete_post

Permanent delete - see docs/RCA_DELETE_POST.md.

company_schedule_post

Publish at a future ISO-8601 datetime.

company_reply_comment

Reply as the page to a comment on one of your posts.

company_reshare_post

Reshare another post on the page, optional commentary.

Company growth (2)

Tool

Purpose

company_invite_to_follow

Send follow invitations to 1st-degree connections (LinkedIn caps 250/month).

company_list_scheduled

List posts queued for future publication.

Personal -> Company bridge (4)

Tool

Purpose

personal_tag_company

Publish a personal post that @-mentions the page.

personal_reshare_company_post

Reshare a page post on your personal profile.

personal_comment_as_admin

Comment on a page post as the page (or as you).

personal_read_company_mentions

Scan 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

Available Tools

24 tools
company_analyticsCompany analyticsA
Read-only

Read metric cards from the analytics page.

Inputs: company_id (required), scope. Returns: object

company_create_postCreate company postA

Publish a text post to the company page.

Inputs: text (required), company_id (required), link_url, image_path. Returns: object

company_delete_postDelete company postA
Destructive

Permanently delete a company post.

This operation is irreversible. LinkedIn does not provide a trash or restore mechanism for company posts.

Implementation note: the click sequence runs entirely through page.evaluate to bypass Playwright's actionability checks. See providers/shared.remove_blocking_modal_outlet for the root cause (phantom #artdeco-modal-outlet overlays).

Inputs: post_urn (required), company_id (required). Returns: object

company_edit_aboutEdit company AboutA

Replace the company page About section.

Inputs: about_text (required), company_id (required). Returns: object

company_edit_postEdit company postA

Replace the body of an existing company post.

Inputs: new_text (required), post_urn (required), company_id (required). Returns: object

company_invite_to_followInvite connections to followA

Send follow invitations to your 1st-degree connections.

LinkedIn caps these at 250 invites per page per month. The tool sends up to max_invites before stopping; LinkedIn will return an error banner once the monthly quota is reached and the run stops gracefully.

Inputs: company_id (required), max_invites. Returns: object

company_list_followersList company followersA
Read-only

List followers of the company page.

Inputs: company_id (required), max_results. Returns: object

company_list_mentionsList company mentions / notificationsB
Read-only

List admin notifications for the page.

Inputs: company_id (required), max_results. Returns: object

company_list_postsList company postsA
Read-only

List posts published by the company page.

Inputs: company_id (required), max_posts. Returns: object

company_list_scheduledList scheduled company posts (optional cancel)A

List posts queued for future publication, optionally cancel one.

LinkedIn renders the company scheduled queue as a dialog over the admin page-posts screen (no dedicated URL, no exposed URN per row). The rows are identified by stable 0-based index and the display datetime parsed from each preview button's aria-label.

Inputs: company_id (required), cancel_index. Returns: object

company_manage_adminsList company adminsA
Read-only

List current admins of the page.

Inputs: company_id (required). Returns: object

company_read_pageRead company pageA
Read-only

Read every structured field for a company page.

Uses LinkedIn's ?editPage=true admin modal - the only place that exposes name, tagline, description, website, industry, size, type, phone and founded year all at once. The modal closes on navigation away; no state is modified.

Inputs: company_id (required). Returns: object

company_reply_commentReply to comment as companyB

Reply as the company to a comment on one of its posts.

Inputs: post_urn (required), company_id (required), reply_text (required), comment_author_name (required). Returns: object

company_reshare_postReshare post to company pageA

Reshare another post on the company page, optionally with commentary.

Inputs: company_id (required), source_post_urn (required), thoughts_text. Returns: object

company_schedule_postSchedule company postB

Publish a post at a future date/time.

Inputs: text (required), company_id (required), scheduled_at_iso (required). Returns: object

company_update_detailsUpdate company detailsA

Update the page's website, industry, size bracket or specialties.

All arguments are optional; supply only the fields you want to change. Fields not passed are left as-is on LinkedIn.

Inputs: company_id (required), website, industry, size_range, +1 more. Returns: object

personal_comment_as_adminComment on company post as adminA

Post a comment on a company post, optionally as the page itself.

When comment_as_company is True (default) the tool flips the identity selector to the Company Page before submitting; when False the comment is posted as the signed-in personal account.

Inputs: company_id (required), comment_text (required), source_post_urn (required), comment_as_company. Returns: object

personal_read_company_mentionsRead company mentions in personal timelineA
Read-only

List personal posts that tag the given company page.

Scans your recent activity page for posts whose body contains the company name as a mention link. Useful to locate employee-advocacy posts for response/engagement.

Inputs: company_name (required), max_results. Returns: object

personal_reshare_company_postReshare company post on personal profileA

Share a Company Page post onto the signed-in user's profile.

Inputs: source_post_urn (required), thoughts_text. Returns: object

personal_tag_companyTag company in personal postA

Publish a personal post mentioning your company page.

The post is assembled as <lead_text>@<company>[first match]<trailing_text>.

Inputs: lead_text (required), company_name (required), trailing_text (required). Returns: object

session_logoutLogoutA
Destructive

Wipe the persistent browser profile. Forces re-login next run.

The operation is local - it deletes the profile directory. It does not sign you out on LinkedIn's side (cookies remain valid until they expire on the server). Run --login to sign in again.

Inputs: no named parameters. Returns: object

session_statusSession statusA
Read-only

Report whether a persistent LinkedIn profile is present.

This is a fast local check - it does NOT open the browser or hit LinkedIn. Useful to decide whether a --login step is required.

Inputs: no named parameters. Returns: object

session_warmupWarm up browser sessionA
Read-only

Launch the browser, navigate to /feed/, confirm authentication.

Call this after --login to verify the session works before running other tools. Returns the current LinkedIn URL and a success flag.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools are largely distinct with clear prefixes for session, company, and personal actions. A few pairs like company_list_mentions and personal_read_company_mentions could be confused, but descriptions clarify the difference. Overall boundaries are clear.

    Naming Consistency4/5

    Most tools follow a <scope>_<verb>_<object> pattern, such as company_read_page and company_create_post. Minor deviations like company_analytics and session_status (nouns rather than verbs) exist but do not disrupt the overall predictable scheme.

    Tool Count3/5

    With 24 tools, this falls into the heavy range (16-25). The count is justified by the breadth of LinkedIn admin features, but it borders on too many for easy navigation. Each tool serves a distinct purpose, yet some trimming or grouping could improve focus.

    Completeness4/5

    The set covers a wide range of admin workflows: page reading and editing, post lifecycle (create, edit, delete, schedule), comments, analytics, followers, invites, and personal advocacy actions. Notable gaps include listing or deleting comments, and fetching a single post by ID, but these are workable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn, enabling posting, liking, commenting, and profile retrieval via official OAuth 2.0. Features CLI, HTTP admin, and optional Telegram bot.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing LinkedIn Company Pages via the official Community Management API. Post content, manage comments, track analytics, and more through the Model Context Protocol.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for LinkedIn Company Page analytics, providing follower growth, demographics, page views, and engagement stats via the Community Management API.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn API integration. Enables authentication, profile access, connections, search, messaging, and feed management via OAuth2.
      MIT