Linkedin Profile

io.github.johnisanerdPublished by GitHub account johnisanerdv1.0.0Updated Nov 5, 2026

Public LinkedIn profiles as JSON: headline, company, experience, and education, via hosted MCP.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Hosted Apify MCP tool that turns public LinkedIn profile URLs into structured JSON rows with headline, company, experience and education.

What you can do
  • Collect one or many public LinkedIn /in/ profile URLs and return one JSON row per person
  • Read name, headline, about, location, current company and title, follower and connection counts, photo and public URL
  • Retrieve full work experience and education history, plus a plain-language summary field per row
  • Batch up to 1000 URLs in a single run, with per-URL error rows instead of a failed batch
When to use it
Useful when an assistant needs to enrich a list of public LinkedIn profiles into structured fields for a sheet, database or CRM, or to look up one person's headline, employer and background without manual copying.
Requirements
Remote Apify MCP endpoint at mcp.apify.com, preloaded with this Actor. An Apify account and API key or OAuth authorization are required; token auth can be supplied as an Authorization Bearer header. Network access to Apify is needed. The README's local Python example needs Python 3.11+ and the APIFY_API_TOKEN variable, but the hosted MCP path does not.
Before you install
Billing is per profile returned, so runs cost money on your Apify account. It reads only public LinkedIn pages and does not use your LinkedIn login or cookies, but the profile data it returns is sent to Apify's servers and to the assistant. The email field is always null. Only public /in/ URLs are processed; other URLs are skipped.

Installation

In SourceWeft

  1. Open Linkedin Profile 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-profile/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-profile": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/linkedin-profile-api"
    }
  }
}

README

👤 LinkedIn Profile API: Public Profiles to Structured JSON

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

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

Send one or many public LinkedIn profile URLs and get back one clean JSON row per person: name, headline, location, current company and title, work experience, education, and follower counts. 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-Profile-API.gitcd Apify-LinkedIn-Profile-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-profile-api-example.py

Alternative: set the API key directly

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

Why Use This LinkedIn Profile API?

A URL in, structured data out. You never touch collection infrastructure. Pass a public profile URL and get flat, predictable fields you can load straight into a sheet, a database, or a CRM.

Batch friendly. Send up to 1000 profile URLs in one run. They are collected in parallel and returned one row each, so enriching a list is one call.

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

Reliable and predictable. Every profile comes back with the same field shape, and a URL that cannot be collected 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

  • Collect one or many public LinkedIn person profiles by URL
  • Name, headline, about, location, current company and title
  • Full work experience and education history
  • Follower and connection counts, profile photo URL, public profile URL

Data Quality

  • One consistent JSON row per profile, every time
  • A plain-language summary field on every row for quick scanning and AI use
  • Clear per-URL error rows so a single bad link never sinks the batch

Usage Examples

Basic Example

json
{  "profileUrls": ["https://www.linkedin.com/in/satyanadella"]}

Batch Example (collected in parallel)

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

Input Parameters

ParameterTypeRequiredDefaultDescription
profileUrlslist[str]YES-One or more public LinkedIn /in/ profile URLs. Up to 1000 per run; non-/in/ URLs are skipped.

Output Format

Each profile is returned as one JSON row:

json
{  "result_type": "profile",  "name": "Satya Nadella",  "headline": "Chairman and CEO at Microsoft",  "currentCompany": "Microsoft",  "currentTitle": "Chairman and CEO",  "location": "Redmond, Washington, United States",  "countryCode": "US",  "followers": 12056751,  "connections": 500,  "pastCompanies": ["Microsoft", "University of Chicago", "Starbucks"],  "education": [{ "title": "The University of Chicago Booth School of Business" }],  "email": null,  "publicUrl": "https://www.linkedin.com/in/satyanadella",  "summary": "Chairman and CEO at Microsoft, based in Redmond, Washington, United States, 12,056,751 followers"}

The email field is always null; email is not available from this source.


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 Profile 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-profile-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 Profile 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-profile-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-profile-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 Profile 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-profile-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-profile-api, using OAuth when prompted.
  5. Ask Claude to run the LinkedIn Profile 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-profile-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-profile-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 Profile 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-profile-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 Profile API to power your data workflows with reliable, structured results.

🤖 Ask an AI assistant about this Actor

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

Last Updated: 2026.10.27

Source: README.md at commit 3fea471

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.0LatestNov 5, 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.