Linkedin Posts

io.github.johnisanerdPublished by GitHub account johnisanerdv1.0.0Updated Oct 26, 2026

Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.

The publisher's own server: posts.design

Overview

AI-generated overview

Apify-hosted MCP server that scrapes public LinkedIn posts into structured JSON with text, engagement counts and author details.

What you can do
  • Discover a public LinkedIn profile's recent posts by profile URL, optionally capped and date-filtered
  • Fetch specific posts directly by post URL, up to 1000 per run
  • Return one consistent JSON row per post with text, hashtags, media, links, post type and date
  • Report reactions, comments and shares, plus author name, headline, follower count and a sample of top comments
  • Include a plain-language summary field per row and an error row for profiles with no public posts
When to use it
Useful for content research, social listening and engagement analytics on public LinkedIn activity, or when you want an assistant to pull a person's recent posts into a sheet, database or BI tool without building collection infrastructure.
Requirements
A remote MCP endpoint at mcp.apify.com, reached through an MCP client; an Apify account with OAuth sign-in or an Apify API token supplied as a Bearer Authorization header. The README's local example also lists Python 3.11 or higher and the APIFY_API_TOKEN environment variable.
Before you install
Usage is billed per post returned, so large runs cost money; cap posts per profile to control spend. The server reads public LinkedIn pages only and asks for no LinkedIn credentials or session cookie, but it does require your Apify account or token, and the requests run on Apify's servers rather than yours.

Installation

In SourceWeft

  1. Open Linkedin Posts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.johnisanerd%2Flinkedin-posts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "linkedin-posts": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-posts-api"
    }
  }
}

README

📝 LinkedIn Posts API: Posts & Engagement to Structured JSON

The most efficient, reliable, and developer-friendly way to use the LinkedIn Posts API.

Actor page: apify.com/johnvc/linkedin-posts-api Input schema: apify.com/johnvc/linkedin-posts-api/input-schema

Give it a public LinkedIn profile URL and it discovers that person's recent posts, or pass specific post URLs to fetch directly. You get back one clean JSON row per post: text, reactions, comments, shares, hashtags, media, and author details. It is built API-first and MCP-ready, so you can call it from Python or drive it as a tool from an AI agent.

Video Walkthrough

[Watch the walkthrough]

Quick Start

Prerequisites

  1. Clone the repository

    bash
    git clone https://github.com/johnisanerd/Apify-LinkedIn-Posts-API.gitcd Apify-LinkedIn-Posts-API
  2. Install dependencies with UV

    bash
    # Install UV if you do not have it:curl -LsSf https://astral.sh/uv/install.sh | sh
    # Install project dependencies:uv sync
  3. Configure your API key

    bash
    cp .env.example .env# Edit .env and add your Apify API key# Get your free API key at: https://apify.com?fpr=9n7kx3
  4. Run the example

    bash
    uv run python linkedin-posts-api-example.py

Alternative: set the API key directly

bash
export APIFY_API_TOKEN="your_api_key_here"uv run python linkedin-posts-api-example.py

Why Use This LinkedIn Posts API?

A URL in, structured data out. You never touch collection infrastructure. Pass a profile URL (or specific post URLs) and get flat, predictable fields you can load straight into a sheet, a database, or a BI tool.

Two ways to collect. Discover a profile's recent posts (newest first, capped and optionally date-filtered), or fetch a known set of posts by URL, up to 1000 per run.

Pay per post. Billing is per post returned, with no per-run setup fee, so you only pay for what is delivered.

Reliable and predictable. Every post comes back with the same field shape, and a profile with no public posts returns a clear error row instead of failing the whole run.

MCP-ready. Call it as a tool from Claude, Cursor, and other AI agents (see the install sections below).

Features

Core Capabilities

  • Discover a profile's recent posts by profile URL, or fetch specific posts by URL
  • Post text, hashtags, media, and links, plus post type and date
  • Reactions, comments, and shares on every post
  • Author name, headline, follower count, and a sample of top comments

Data Quality

  • One consistent JSON row per post, every time
  • A plain-language summary field on every row for quick scanning and AI use
  • A clear error row for a profile with no public posts, so one empty profile never sinks the batch

Usage Examples

Discover a profile's posts

json
{  "profileUrls": ["https://www.linkedin.com/in/williamhgates"],  "maxPostsPerProfile": 5}

Limit discovery to a date range

json
{  "profileUrls": ["https://www.linkedin.com/in/williamhgates"],  "maxPostsPerProfile": 50,  "startDate": "2025-01-01",  "endDate": "2025-12-31"}

Fetch specific posts by URL

json
{  "postUrls": [    "https://www.linkedin.com/posts/williamhgates_activity-7446904645010210816"  ]}

Input Parameters

ParameterTypeRequiredDefaultDescription
profileUrlslist[str]one of these-Public LinkedIn /in/ profile URLs to discover posts from. Up to 25 per run.
postUrlslist[str]one of these-Specific LinkedIn post URLs to fetch directly. Up to 1000 per run.
maxPostsPerProfileintNo20Max posts per profile in discover mode (max 200). Caps cost. Ignored for post URLs.
startDatestrNo-Only discover posts on or after this date (YYYY-MM-DD). Discover mode only.
endDatestrNo-Only discover posts on or before this date (YYYY-MM-DD). Discover mode only.

Supply at least one of profileUrls or postUrls.

Output Format

Each post is returned as one JSON row:

json
{  "result_type": "post",  "postId": "7446904645010210816",  "postUrl": "https://www.linkedin.com/posts/williamhgates_activity-7446904645010210816",  "postType": "post",  "datePosted": "2025-06-01T12:00:00.000Z",  "text": "A few books shaped how I think about clean energy this year...",  "hashtags": ["cleanenergy", "books"],  "authorName": "williamhgates",  "authorHeadline": "Co-chair, Bill & Melinda Gates Foundation",  "authorUrl": "https://www.linkedin.com/in/williamhgates",  "authorFollowers": 37000000,  "numLikes": 12045,  "numComments": 843,  "numShares": 210,  "summary": "Post by williamhgates, 12,045 reactions, 843 comments, posted 2025-06-01"}

The numShares field is returned when the post has shares.


FAQ

Will this put my LinkedIn or LinkedIn Recruiter account at risk?

No. It reads public LinkedIn pages only, the ones anyone can open while signed out. It never logs in and never asks for your cookies: there is no input for an account, a password or an li_at session cookie. Nothing it does is tied to your LinkedIn account, your LinkedIn Recruiter seat or your Sales Navigator license. The requests run on Apify's servers, not in your browser, so nothing connects them to you, and you can keep working in Recruiter while a run is going.


Install in Claude Cowork Desktop

[Install in Claude Cowork Desktop]

Cowork is the desktop app's automation mode. To give it the LinkedIn Posts API as a tool, add the Apify MCP server as a connector.

  1. Open the Claude desktop app and go to Settings → Connectors (or Settings → Developer → Edit Config to edit claude_desktop_config.json directly).
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add the Apify MCP server, preloaded with only this Actor:
json
{  "mcpServers": {    "apify": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api"      ]    }  }}
  1. Restart the app. When Cowork first calls the tool, complete the OAuth prompt in your browser, or add your Apify API token in the connector settings to skip OAuth.
  2. In a Cowork chat, confirm the tool is available and ask it to run the LinkedIn Posts API.

Download the desktop app and start a free trial: https://claude.ai/referral/uIlpa7nPLg More help: https://docs.apify.com/platform/integrations/claude-desktop


Install in Claude Code

[Install in Claude Code]

Claude Code is the command-line tool. Add the Actor's MCP server with one command:

bash
claude mcp add --transport http apify \  "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api"

To use a token instead of browser OAuth:

bash
claude mcp add --transport http apify \  "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api" \  --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Then verify with claude mcp list, or run /mcp inside a session. Ask Claude Code to call the LinkedIn Posts API.

Try Claude Code free: https://claude.ai/referral/uIlpa7nPLg Claude Code MCP docs: https://code.claude.com/docs/en/mcp


Install in Claude (website)

[Install in Claude (website)]

On claude.ai you add Apify as a connector, then enable just this Actor's tool.

  1. Go to Settings → Connectors → Browse connectors and search for Apify MCP server. Install it (enable or update if prompted).
  2. When connecting, authenticate with your Apify API token, and enable the tool johnvc/linkedin-posts-api.
  3. In any chat, open + → Connectors and turn on Apify.
  4. Alternatively, choose Add custom connector and paste the full MCP URL https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api, using OAuth when prompted.
  5. Ask Claude to run the LinkedIn Posts API.

Open Claude on the web: https://claude.ai/referral/uIlpa7nPLg


Install in Cursor

[Install in Cursor]

Cursor reads MCP servers from a project file at .cursor/mcp.json.

  1. In your project, create .cursor/mcp.json:
json
{  "mcpServers": {    "apify": {      "url": "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api"    }  }}
  1. If you prefer token auth over browser OAuth, add a header:
json
{  "mcpServers": {    "apify": {      "url": "https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api",      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }    }  }}
  1. Open Cursor → Settings → MCP and confirm the apify server is connected (green dot).
  2. In Composer or Chat, ask Cursor to call the LinkedIn Posts API.

New to Cursor? Get it here: https://cursor.com/referral?code=XQP4VBLI3NNX


Install in ChatGPT

[Install in ChatGPT]

ChatGPT connects to the Apify MCP server through Developer mode (available on ChatGPT Pro, Plus, Business, Enterprise, and Education plans).

  1. Click your profile icon, then go to Settings > Apps. If you do not see a Create app button, open Advanced settings and enable Developer mode.
  2. Click Create app and fill out the form:
    • Name: Apify
    • MCP Server URL: https://mcp.apify.com/?tools=actors,docs,johnvc/linkedin-posts-api
    • Authentication: OAuth
  3. Click Create and authorize the connection with Apify.
  4. To use the app in a conversation, click + in the chat, choose Developer mode, and select Apify.

More help: https://docs.apify.com/platform/integrations/mcp


Made with care

Use the LinkedIn Posts API to power your content research, social listening, and engagement analytics with reliable, structured results.

🤖 Ask an AI assistant about this Actor

Open a ready-to-send prompt about the LinkedIn Posts API in the AI of your choice:

Last Updated: 2026.10.27

Source: README.md at commit fe3daf3

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Posts integrations