Log inSubmit server
Lhremote logo

Lhremote

by alexey-pelykh

Controls LinkedHelper through MCP and CLI for LinkedIn accounts, campaigns, messaging, profiles, and engagement workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Lhremote

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "alexey-pelykh-lhremote": {
      "command": "npx",
      "args": [
        "-y",
        "lhremote"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y lhremote

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

alexey-pelykh/lhremote MCP server connects AI assistants and command-line workflows to LinkedHelper through the Model Context Protocol. It detects or launches LinkedHelper with Chrome DevTools Protocol access, manages accounts and instances, and operates campaigns and their action chains. The tooling also covers LinkedIn profile queries, messaging, engagement, search-related operations, and profile enrichment described in the project documentation. Reach for it when LinkedHelper is installed locally and you need agent-driven LinkedIn automation rather than direct API access.

Use cases

  • Launch LinkedHelper and start a LinkedIn account instance
  • Create and monitor campaign execution
  • Import LinkedIn profile URLs into campaign targets
  • Query cached profiles and messaging history
  • Manage campaign action chains and exclusions

Key features

  • LinkedHelper app and instance management
  • Campaign lifecycle and action-chain control
  • LinkedIn profile URL importing
  • Campaign targeting and exclusion management
  • Profile and messaging queries
  • CLI and MCP interfaces

Tools75

What Lhremote lets your agent do. Expand a tool for its parameters.

Self-reported~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · lhremote (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars20Stargazers on the source repository.
npm downloads96Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed75Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Lhremote works

What alexey-pelykh/lhremote MCP server does

alexey-pelykh/lhremote MCP server exposes LinkedHelper automation through both MCP tools and a command-line interface. It can find a running LinkedHelper application, launch or quit it, list available LinkedIn accounts, start or stop account instances, and report connection or database status.

Campaign workflows include creating campaigns from YAML or JSON, reading and exporting configurations, changing metadata, archiving or permanently erasing campaigns, and starting or stopping execution. Agents can inspect campaign status and statistics, retry selected people, manage action chains, move people between actions, and maintain campaign or action exclusion lists. LinkedIn profile URLs can be imported into campaign target lists, and assigned people can be listed or removed.

How it works

alexey-pelykh/lhremote MCP server communicates with the local LinkedHelper desktop application using Chrome DevTools Protocol connection details. The workflow starts by finding an existing application or launching one with remote debugging enabled. After an account is selected, an instance can be started before campaign or LinkedIn actions are used.

The MCP entry point runs as the mcp subcommand. The CLI exposes corresponding commands for the documented MCP operations, with JSON output options on many commands. Campaign creation accepts a file or inline YAML/JSON configuration. Starting a campaign is asynchronous, so status and statistics commands are used to monitor execution.

Setup and configuration

The project requires Node.js 24 or newer and the LinkedHelper desktop application. LinkedHelper requires a paid subscription. Install the npm package globally or run it through npx; for Claude Desktop, configure a local command using npx, the lhremote package, and the mcp subcommand.

A typical operating sequence is to detect or launch LinkedHelper, list accounts, start an account instance, inspect available action types, create a campaign, import profile URLs, start the campaign, and monitor its status. Campaign and targeting commands accept IDs, URLs, files, or inline values depending on the operation.

Tools and capabilities

  • Manage the LinkedHelper application and account instances.
  • Create, inspect, export, update, archive, or erase campaigns.
  • Configure, reorder, remove, and advance campaign actions.
  • Import, exclude, list, retry, and remove campaign people.
  • Query cached LinkedIn profiles and messaging data.
  • Perform documented LinkedIn engagement, enrichment, feed, post, and search operations.
  • Inspect available action types and campaign execution results.

Limitations and notes

alexey-pelykh/lhremote MCP server depends on a locally installed LinkedHelper application rather than operating as a standalone LinkedIn client. Its documented prerequisites include a paid LinkedHelper subscription. LinkedIn monitors automated activity, so the project points users to its rate-limiting guidance. Permanently erasing a campaign removes its related database data and cannot be undone; campaign deletion is described as an archival operation instead.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Lhremote

Install Node.js 24 or newer, then run it with `npx -y lhremote mcp` or install the `lhremote` npm package globally.

Yes. The README provides Claude Desktop configuration using `npx` with the `lhremote` package and the `mcp` subcommand.

It requires Node.js 24 or newer and the LinkedHelper desktop application, which requires a paid subscription.

Yes. It can create campaigns, configure action chains, start or stop execution, and retrieve status and statistics.

Yes. The `import-people-from-urls` operation imports LinkedIn profile URLs into a campaign action target list and skips previously imported URLs.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLhremote AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/alexey-pelykh-lhremote?style=directory)](https://allmcps.com/mcp/alexey-pelykh-lhremote)
HTML Embed
<a href="https://allmcps.com/mcp/alexey-pelykh-lhremote"><img src="https://allmcps.com/api/badge/alexey-pelykh-lhremote?style=directory" alt="Lhremote on AllMCPs" /></a>