lednev01

Topclozer LinkedIn MCP — AI skill for Claude Code

AI community

Hosted LinkedIn MCP server for AI agents — people search, profiles, posts and connections through a managed sender account, not your own LinkedIn profile.

How to install Topclozer LinkedIn MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open lednev01/topclozer-linkedin-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Topclozer LinkedIn MCP does

Hosted LinkedIn MCP server for AI agents — people search, profiles, posts and connections through a managed sender account, not your own LinkedIn profile. Works with Claude, Cursor, ChatGPT and VS Code.

Alternatives in AI

n8n Node Configuration — Node configuration with dependency rules and AI connections 3.6k ★
Proxypal — A desktop app that lets you use your AI subscriptions (Claude, ChatGPT, Gemini, GitHub Copilot) with any codin 1.2k ★
Gptaku Plugins — A Claude Code plugin marketplace for people who want to become AI Native 1.1k ★

README

TopClozer LinkedIn MCP

A hosted [Model Context Protocol](https://modelcontextprotocol.io) server that gives an AI agent real LinkedIn tools — people search, profiles, posts and connections — **through a managed sender account rather than your own profile**.

https://topclozer.com/api/mcp

No install. No npm package, no Docker image, no local browser, no `li_at` cookie. One HTTPS endpoint and a bearer key.

Why another LinkedIn MCP server

There are already good open-source ones, and this repository [links to them](https://topclozer.com/mcp/directory) rather than pretending otherwise. They differ from this one in a single respect that turns out to matter more than the tool list:

Every cookie-based LinkedIn MCP server asks you for **your own** LinkedIn session. LinkedIn's User Agreement prohibits automating a personal profile, and restriction is the ordinary outcome rather than a rare accident — most of those projects say so in their own README.

TopClozer runs every call through a LinkedIn account connected to your workspace, which is one you own separately or rent. Underneath the tool boundary sit the things a raw API has no reason to have: a per-workspace rate limit, warm-up ramps, working-hours windows, randomised gaps between actions, and a human approval queue on anything irreversible.

**If you are experimenting on a throwaway profile, a free server is genuinely the better answer.** This one is for when the account has to survive the month.

Tools

All read-only. There is no tool that sends an invite, a message, a reply, a follow or a like — and that is a boundary, not a backlog item.

Tool	What it does
`search_linkedin_people`	Search LinkedIn for people matching an ICP, with Sales Navigator structured filters when the account has a seat
`get_linkedin_profile`	One profile: role, tenure, follower count, job-change date, latest post
`get_linkedin_posts`	A member's recent posts, newest first, reposts f