LinkedIn Browser MCP Server

Automates LinkedIn interactions and extracts data through browser automation, respecting terms of service and rate limits. The linkedin browser mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

What it actually does

A FastMCP-based server for LinkedIn automation and data extraction using browser automation. This server provides a set of tools for interacting with LinkedIn programmatically while respecting LinkedIn's terms of service and rate limits.

• Secure Authentication —
• Environment-based credential management
• Session persistence with encrypted cookie storage
• Rate limiting protection
• Automatic session recovery
• Profile Operations —

Its toolset

Everything the assistant can do here goes through one of these:

• login_linkedin_secure — Securely log in using environment credentials
• browse_linkedin_feed — Browse and extract posts from feed
• search_linkedin_profiles — Search for profiles matching criteria
• view_linkedin_profile — View and extract data from specific profiles
• interact_with_linkedin_post — Like, comment, or read posts

Configuration

You will need one environment variable: COOKIE_ENCRYPTION_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.8+ - Playwright - FastMCP library - LinkedIn account

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. LinkedIn Browser's toolset — login_linkedin_secure, browse_linkedin_feed, search_linkedin_profiles and 2 more — is a fair guide to whether it matches your workflow. It is maintained by alinaqi; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the linkedin browser mcp server does with a few real requests.