linkedin-mcp-local
PulseGate's liveness check found it on 14 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 2 Aug 2026. How this is checked
LinkedIn-MCP-Local is an open-source, typed MCP server that provides authorized, policy-enforced access to LinkedIn capabilities for AI agents. Built with Playwright, it enables secure automation while maintaining strict controls. Designed for developers integrating AI with professional networking platforms.
Inferred · not functionally tested
Overview
4 featuresPurpose: Safely and securely connecting AI agents to LinkedIn capabilities with typed interfaces and policy controls.
Inferred · not functionally tested
Audience: developers
Inferred · not functionally tested
Functions: agents, browser_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the Frameworks & runtimes space, linkedin-mcp-local takes a focused approach. Inferred · not functionally tested: Safely and securely connecting AI agents to LinkedIn capabilities with typed interfaces and policy controls. Inferred · not functionally tested: linkedin-mcp-local is an open-source project aimed at developers. Basis unknown · not verified: linkedin-mcp-local is open source under the Apache-2.0 license. Basis unknown · not verified: linkedin-mcp-local is available on the command line, and it can be self-hosted.
Behind linkedin-mcp-local is Prakhar Agarwal, and it first shipped in 2026. Development happens publicly on GitHub with 26 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include Policy Enforcement, Typed API, and LinkedIn Automation. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Policy Enforcement
- Typed API
- LinkedIn Automation
- Playwright Integration
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed2 Aug · 08:09 UTClinkedin-mcp-local seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about linkedin-mcp-local
- What does linkedin-mcp-local do?
- Inferred · not functionally tested: Safely and securely connecting AI agents to LinkedIn capabilities with typed interfaces and policy controls. It is catalogued under Frameworks & runtimes on PulseGate.
- Who should use linkedin-mcp-local?
- Inferred · not functionally tested: linkedin-mcp-local is an open-source project built for developers.
- Is linkedin-mcp-local free?
- Basis unknown · not verified: Yes — linkedin-mcp-local is open source under the Apache-2.0 license and free to use.
- What platforms does linkedin-mcp-local run on?
- Basis unknown · not verified: linkedin-mcp-local runs on the command line. It can also be self-hosted.
- Is linkedin-mcp-local still maintained?
- PulseGate's liveness check found it on 14 Sep 2026. Its GitHub repository shows 26 commits in the last 90 days.
- What are alternatives to linkedin-mcp-local?
- Similar projects tracked by PulseGate include linkedin-mcp-automation, mcp-server-linkedin, and artigence-linkedin-mcp.linkedin-mcp-automationmcp-server-linkedinartigence-linkedin-mcp
- Who makes linkedin-mcp-local?
- linkedin-mcp-local is developed by Prakhar Agarwal.
- When did linkedin-mcp-local launch?
- linkedin-mcp-local first shipped in 2026.
Similar projects
Closest matches by what these projects do