MCP Server for LinkedIn

Created By
Hritik003a year ago
A MCP server for LinkedIn to seamlessly apply for jobs๐Ÿš€
Overview

what is MCP Server for LinkedIn?

MCP Server for LinkedIn is a Model Context Protocol (MCP) server designed to facilitate seamless job applications and feed searches on LinkedIn.

how to use MCP Server for LinkedIn?

To use the MCP Server, clone the repository, adjust the local path in the configuration, and run the server using the provided commands. You can test it using the MCP-client.

key features of MCP Server for LinkedIn?

  • Profile retrieval to fetch user profiles and key information.
  • Advanced job search functionality with customizable parameters.
  • Retrieval of LinkedIn feed posts with pagination support.
  • Resume analysis to extract key information from PDF resumes.

use cases of MCP Server for LinkedIn?

  1. Applying for jobs on LinkedIn using automated processes.
  2. Searching for job opportunities based on specific criteria.
  3. Analyzing resumes to match job requirements.
  4. Retrieving and displaying LinkedIn feed posts for updates.

FAQ from MCP Server for LinkedIn?

  • Can I use this server for any job application?

Yes! It is designed to work with LinkedIn job applications.

  • Is there a limit to the number of profiles I can retrieve?

No, but be mindful of LinkedIn's API usage policies.

  • How do I configure the server?

Adjust the <LOCAL_PATH> in the configuration file after cloning the repo.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Hritik003
Star
10
Language
Python
License
-
Tags

Recommend Servers

View All
Gpt Scrambler

2 days ago
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