Skip to content
← All products

Independent LinkedIn® workflow source package

Run LinkedIn workflows from a local CLI.

The package works against a LinkedIn account you control. It covers profiles, jobs, feeds, messages, connections, settings, and company pages through a local Node CLI and MCP server. Read-only work is separated from actions that require confirmation or force, and run logs are redacted locally.

Platform warning: LinkedIn says third-party software that scrapes or automates activity violates its User Agreement. Use can lead to account restriction, and the software can stop working when LinkedIn changes its interfaces.

Request handoff See what ships
Validated registry
274
LinkedIn actions · 10 MCP tools
Read-only surface
169
safer discovery actions
Risk-gated surface
105
confirmation required; unsafe actions also require force
Action categories
12
company pages, feed, jobs, profile, messaging, network, more
mcp action registry 10 tools
274 registered actions read-only discovery plus gated execution
  • 169 read-only
  • 105 risk-gated
confirm force redacted log
human-in-the-loop execution local session

What the source actually supports

This is not a generic agent framework. It is LinkedIn-specific source for inspecting account state, preparing work, running reviewed actions, and recording redacted outcomes locally.

  • Recruiting and job workflows

    Search people and jobs, inspect profiles, prepare reviewed connection or outreach plans, work with Easy Apply flows, and record outcomes in local recruiter state.

  • A compact MCP surface

    Let an agent list actions, inspect required inputs, run read-only steps, and stop when confirmation is required. The MCP layer gives a compact 10-tool interface instead of hundreds of exposed primitives.

  • Member and company-page operations

    Read feeds, profiles, networks, jobs, notifications, settings, messages, and managed Page analytics. Prepare or run approved post, profile, connection, messaging, job, and Page actions where the registry supports them.

  • Diagnostics and local records

    Use a separate 27-action diagnostics CLI for capture and HAR research, while account workspaces keep sessions, plans, histories, and redacted logs separated locally.

What ships in the handoff

The handoff contains the working source, documentation, tests, safe sample material where available, and known-limitations notes. Before payment, you receive a draft licence and written order defining the buyer, permitted use, restrictions, delivery, and any support. Source ownership does not transfer.

product
LinkedIn® workflow CLI & MCP source kit
price
$1,499
buyer
Agent builders, recruiters, sourcers, internal ops teams, and technical founders.

included

  • cliActions/ local action runner and registry
  • MCP stdio server with 10 registered tools
  • cliDiagnosis/ capture and HAR-import tooling (27 actions)
  • Recruiter workflow prototype and local CRM file shape
  • Written order with scope, exclusions, delivery, and any agreed support

components

CLI action layer
Manual login, named account workspaces, session status, action list/show/run, smoke checks, run history, licence status, doctor output, and redacted local run logs.
Agent interface
A compact MCP server exposes listing, description, execution, run history, licence status, and recruiter workflow tools instead of hundreds of one-off tools.

How intent becomes output

The operator path, start to finish. Each step is a real command surface, not a promise.

  1. 01

    Inspect

    List the 274 LinkedIn actions, inspect required inputs and risk levels, and keep read-only work separate from externally visible actions.

  2. 02

    Prepare

    Search, read, and build a reviewed plan for recruiting, job, feed, profile, network, messaging, or company-page work.

  3. 03

    Approve

    Low, medium, high, and unsafe actions require confirmation; the 50 unsafe actions also require force.

  4. 04

    Audit

    Redaction is the default, not an option: results are scrubbed before anything touches disk, and only explicitly whitelisted fields on read-only actions are ever exposed. MCP responses are trimmed; the full redacted record stays local.

What's proven, what's excluded

The same diligence a technical buyer would run: what the code demonstrates locally, and what is deliberately left out of a clean handoff.

✓ proven

  • Registry validated

    On 2026-08-16, the validator passed 274 LinkedIn actions: 169 read-only and 105 gated across 12 categories. IDs are unique and declared inputs are checked against their runners.

  • Checks pass locally

    The repository check passed syntax checks, the 274-action primary registry, the separate 27-action diagnostics registry, and the shipped selftest suites. Buyers can request the output and rerun npm run check on the exact bundle.

  • Risk gates are visible

    The registry labels actions read-only, low, medium, high, or unsafe. All non-read-only actions require confirmation; 50 unsafe actions also require force.

! excluded

  • Not a hosted service

    No hosted SaaS, cloud billing, packaged installer, Stripe integration, marketplace listing, customers, or revenue are included.

  • LinkedIn prohibits this automation

    LinkedIn states that third-party software which scrapes or automates activity violates its User Agreement. Use can result in temporary or permanent account restriction, and commands can stop working without notice.

  • Independent, not endorsed

    Pullmesh is not affiliated with or endorsed by LinkedIn Corporation. LinkedIn® is used only to identify the platform this independent software works with.

  • No account or session shipped

    No LinkedIn account, cookies, browser profile, captured session, raw HAR, private messages, or member dataset is included. The buyer logs in manually with an account they control.

  • Live proof needs refresh

    Live behavior depends on account state, UI/API changes, permissions, locale, and rate limits.

  • Buyer controls use

    Commercial launch should add counsel-reviewed terms, warnings, data disclosures, behavior safeguards, and fresh live testing.

  • Licence terms before payment

    The draft licence and written order identify the buyer, permitted internal use and modification rights, restrictions, delivery, and any support. Source ownership does not transfer. Review both documents before paying; the signed order and delivered licence govern.

Build it yourself, or start from the source

Build from scratch Pullmesh handoff
Give an agent unrestricted browser access and discover the risky steps at runtime. Start with a 10-tool MCP surface, explicit action registry, approval gates, and local redacted run logs.
Build the action registry, CLI runner, MCP server, and workflows in separate experiments. Receive the combined action layer as source and decide which surfaces to productize.
Discover risky actions only after a workflow mutates state. Inspect read-only, low, medium, high, and unsafe classifications before execution.

Request handoff

Inspect the LinkedIn source and its risks before you buy.

Request the registry summary, current check output, file tree, known limitations, draft licence, and written platform-risk notice before deciding on the $1,499 source licence.

Request handoff

Opens your mail client. If it doesn't, write to [email protected] and mention the linkedin® workflow cli & mcp source kit.