LinkedIn Profile Scraper MCP Server

Created By
codingaslua year ago
This MCP server uses the Fresh LinkedIn Profile Data API to fetch LinkedIn profile information. It is implemented as a model context protocol (MCP) server and exposes a single tool, get_profile, which accepts a LinkedIn profile URL and returns the profile data in JSON format.
Overview

What is LinkedIn Profile Scraper MCP Server?

This MCP server utilizes the Fresh LinkedIn Profile Data API to fetch LinkedIn profile information. It is designed to expose a single tool, get_profile, which accepts a LinkedIn profile URL and returns the profile data in JSON format.

How to use LinkedIn Profile Scraper MCP Server?

To use the server, clone the repository, install the required dependencies, set up your environment variables with your RapidAPI key, and run the server using the command uv run linkedin.py.

Key features of LinkedIn Profile Scraper MCP Server?

  • Fetch Profile Data: Retrieves LinkedIn profile information including skills and other settings.
  • Asynchronous HTTP Requests: Utilizes httpx for non-blocking API calls.
  • Environment-based Configuration: Reads the RAPIDAPI_KEY from environment variables using dotenv.

Use cases of LinkedIn Profile Scraper MCP Server?

  1. Fetching detailed LinkedIn profiles for data analysis.
  2. Integrating LinkedIn profile data into applications for user insights.
  3. Automating the retrieval of LinkedIn profiles for recruitment purposes.

FAQ from LinkedIn Profile Scraper MCP Server?

  • What is required to run the server?

You need Python 3.7+, the MCP framework, and the required libraries installed.

  • How do I obtain the RAPIDAPI_KEY?

You can obtain it from RapidAPI and add it to your .env file.

  • What happens if the RAPIDAPI_KEY is missing?

The server will raise a ValueError if the key is not set.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
codingaslu
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago