What are the prerequisites for using LinkedInMCP?
You need Node.js 16+, a LinkedIn Developer account, and an MCP-compatible LLM (e.g., Claude, OpenAI).
@Dishant27
Basic information
Model Context Protocol (MCP) server for LinkedIn API integration
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
LinkedInMCP is a Model Context Protocol (MCP) server that provides a flexible, context-rich interface for interacting with the LinkedIn API. It is built for developers and LLMs (like Claude or OpenAI) to enable intelligent, type-safe LinkedIn data retrieval and operations.
Clone the repository, install dependencies with npm, create a .env file with your LinkedIn Client ID and Client Secret, then build and start the server (npm run build, npm start). Integrate with Claude Desktop by adding a tool configuration that points to the server’s executable and provides the same environment variables. The LLM can then use tools such as search-people and get-profile to query LinkedIn.
You need Node.js 16+, a LinkedIn Developer account, and an MCP-compatible LLM (e.g., Claude, OpenAI).
Register an application on the LinkedIn Developer Portal to obtain a Client ID and Client Secret. Set these in a `.env` file or in the MCP server’s environment variables. The server implements OAuth 2.0 for secure token management.
LinkedInMCP processes data in transit without persistent storage. It returns only the requested fields and includes automatic data sanitization, supporting GDPR compliance and minimal data retention.
It offers advanced people search, detailed profile retrieval, job market intelligence, and messaging capabilities, all through a standardized MCP interface.
No. This project is an independent innovation and is not officially affiliated with LinkedIn or Microsoft.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Agent-Native Terminal
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
Comments