LinkedIn MCP Server

The evidence clearly documents local execution, a default 127.0.0.1 HTTP bind, browser-profile and cookie locations, proxy routing scope, automatic import behavior, and a reduced Docker authentication-cookie subset. Proxy passwords can be supplied through environment variables, and CI actions are commit-pinned. Sending a message is marked as confirmation-gated, and terminal logout also requests confirmation. Deductions apply because browser-session import is enabled by default and reads LinkedIn cookies from an everyday browser, while connection requests and other write operations are not shown to share a comprehensive call-time confirmation policy. Python dependencies use lower bounds rather than a fully pinned set, and the recommended installation deliberately resolves @latest at every launch. Sent messages and connection requests have no practical rollback, while logout discards a session, so rollback is thin. The independent-project disclaimer, trademark statement, author identity, email, and license attribution justify full source-attribution credit.

The README, project metadata, CLI options, fixtures, and CI are broadly consistent about the local browser-session model, supported Python versions, and major operating modes. The supplied tests also show deliberate cross-process lease and multi-platform browser-behavior coverage. Self-consistency is reduced because feature status mixes an unexplained “working” label with issue references, and the README describes a broader feature set than the short package description. Dependencies, version floors, installer, and browser setup are identified, but availability still relies on runtime downloads, @latest resolution, LinkedIn page structure, and external login challenges. Failure guidance is unusually thorough and actionable, covering authentication, timeouts, browser contention, proxies, container misdetection, browser-version conflicts, and DLL problems, which justifies full marks for failure messages.

The material explicitly serves developers, Claude Desktop users, generic MCP clients, Docker deployments, local development, and both stdio and HTTP operation, with scenario-specific configuration. The tool catalog and CLI reference establish useful boundaries, and several read tools require explicit section selection. Deductions apply because LinkedIn terms, rate or account restrictions, and a complete confirmation boundary for every state-changing tool are not documented. Tool names and filters support reasonably precise selection, but complete input schemas, ambiguity handling, and model invocation guidance are absent, limiting capability-boundary and trigger-precision scores.

The README has clear organization, a tool catalog, several installation routes, a detailed CLI reference, examples, and extensive troubleshooting. Package, executable, and tool naming are coherent. Concurrent-use constraints, cookie-import limitations, proxy hazards, browser-cache growth, platform differences, and login challenges are documented thoroughly, justifying full known-limitations credit. Apache-2.0 metadata matches the complete LICENSE. A package version and Releases-based changelog route exist, but no actual changelog content or compatibility policy appears in the supplied files, so versioning is not thorough. The author, email, issue tracker, and repository provide a maintenance path, but there is no demonstrated team ownership, support commitment, or dedicated security contact; the publisher's registry status remains unknown rather than adverse.

The tools cover profiles, companies, jobs, feeds, and messages and expose logged-in LinkedIn browser data to general MCP clients, providing strong marginal value. Tool descriptions and explicit section selection improve usability, but no response schemas, representative outputs, pagination semantics, or field-stability commitments are supplied, so output usability is only adequate. The project is free and local, but users bear browser downloads, persistent-session management, login handling, frequent upgrades, scraping maintenance, verification challenges, and cache growth; the benefit appears favorable but is not comprehensively quantified.

Project metadata, the README, CI, and test-support code cross-corroborate claims about versions, dependencies, testing workflow, local sessions, cross-process locking, and browser-identity checks. Several uncertain features are also tied to issue references. Claim traceability is reduced because the supplied evidence omits the primary server and tool implementations, response schemas, full test cases, and CI results; badges and “working” labels alone do not establish functional outcomes. The documentation often distinguishes constraints from recommendations, but some operational, safety, and feature-status statements remain assertions without consistently labeling their evidentiary basis or separating inference from demonstrated fact.