LinkedIn Model Context Protocol (MCP) Server

Created By
Rayyan9477a year ago
A powerful Model Context Protocol server for LinkedIn interactions that enables AI assistants to search for jobs, generate resumes and cover letters, and manage job applications programmatically.
Overview

What is LinkedIn Model Context Protocol (MCP) Server?

The LinkedIn MCP Server is a powerful Model Context Protocol server designed for LinkedIn interactions, enabling AI assistants to programmatically search for jobs, generate resumes and cover letters, and manage job applications.

How to use LinkedIn MCP Server?

To use the LinkedIn MCP Server, clone the repository, set up a virtual environment, install the dependencies, configure your LinkedIn credentials, and start the server. You can then make JSON-RPC style requests to interact with LinkedIn.

Key features of LinkedIn MCP Server?

  • Secure LinkedIn authentication with session management
  • Access and update LinkedIn profile information
  • Job search with flexible filtering options
  • Generate customized resumes and cover letters
  • Submit and track job applications

Use cases of LinkedIn MCP Server?

  1. Automating job searches for specific roles
  2. Generating tailored resumes for job applications
  3. Managing job applications programmatically

FAQ from LinkedIn MCP Server?

  • Can I use this server for any LinkedIn account?

Yes, as long as you have valid LinkedIn credentials, you can use this server.

  • Is there a limit to the number of job searches I can perform?

There may be rate limits imposed by LinkedIn's API, so it's advisable to check their documentation.

  • Is the LinkedIn MCP Server free to use?

Yes, the server is open-source and free to use under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rayyan9477
Star
5
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