LinkedGrow MCP server
2026년 10월 28일 커밋Claude, Cursor 또는 ChatGPT가 직접 호스팅한 인스턴스에서 LinkedIn 잠재 고객을 찾고 연락하며, LinkedIn 게시물을 작성하고 예약할 수 있도록 지원합니다.
다른 이름 DigiHold/LinkedGrow
- 스타
- 41
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 10월 28일
- 라이선스
- AGPL-3.0
LinkedGrow MCP란?
Claude, Cursor 또는 ChatGPT가 직접 호스팅한 인스턴스에서 LinkedIn 잠재 고객을 찾고 연락하며, LinkedIn 게시물을 작성하고 예약할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
LinkedGrow MCP server 정보
LinkedGrow는 영업 전문가와 마케터가 자율 에이전트를 통해 LinkedIn 잠재 고객을 발굴하고 소통할 수 있게 해줍니다. Docker를 사용하여 Linux 머신에 이 MCP server를 호스팅하면 Claude, Cursor, ChatGPT와 같은 AI 클라이언트를 소셜 셀링용 26개 도구 세트에 연결할 수 있습니다. 이 시스템은 인간의 행동을 모방하는 실제 Chrome 인스턴스를 실행하여 작동하며, 전용 브라우저 세션을 통해 플랫폼과 직접 상호작용함으로써 공식 API의 제한을 우회합니다.
사용자는 리드 스코어링, 자동 아웃리치, 콘텐츠 생성을 포함한 전체 워크플로우를 셀프 호스팅 대시보드에서 관리할 수 있습니다. 서버가 작동하려면 Anthropic, OpenAI 또는 Google과 같은 제공업체의 AI 키와 각 LinkedIn 계정이 전용 주소를 사용하도록 보장하는 프록시 서비스가 필요합니다. 이 플랫폼은 통합 에디터를 통한 게시물 초안 작성 및 예약부터 중앙 집중식 받은 편지함의 답장 관리까지 모든 것을 처리하며, 계정 안전을 유지하기 위해 사람의 속도에 맞춰 작동합니다.
활용 사례
- 1자동 리드 생성AI 어시스턴트에게 특정 경쟁사 게시물이나 주제에 참여하고 있는 잠재 고객을 찾아달라고 요청하십시오.
- 2아웃리치 대화 관리에이전트가 초기 메시지를 처리하도록 하고, 잠재 고객이 대화할 준비가 되었을 때만 알림을 받으십시오.
- 3콘텐츠 예약 및 생성AI 클라이언트에게 내장된 에디터를 사용하여 일주일 치의 LinkedIn 게시물을 작성하고 간격을 두어 게시하도록 지시하십시오.
- 4시각적 콘텐츠 디자인사전 설정된 템플릿을 사용하여 전문적인 캐러셀을 만들고 피드에 내보내십시오.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능digihold/linkedgrow is public and reachablegithub.com/digihold/linkedgrow ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-28github.com/digihold/linkedgrow ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기LinkedGrow
Autonomous agents that find your clients on LinkedIn, on a server you own.
An MCP server with 26 tools, so Claude, Cursor or ChatGPT can run the whole thing.
Install · Docs · Hosted version · Issues · Contributing

What it does
You describe who you sell to, and an agent goes looking for those people where they already are: under a competitor's post, inside a search you already trust, among the people who reacted to a topic. It reads the profile, scores the fit, likes something real, and sends an invitation with no note attached. Once the person accepts, it runs a short conversation in your name and hands you the ones who want to talk. Every lead keeps the post or the search that produced it, so you always know where it came from.
The posting side is the same product. A generator writes a first draft in your voice, an editor scores the hook and the length before anything goes out, a calendar hands each post to LinkedIn's own scheduler, and the numbers on the analytics page are the ones LinkedIn showed on your posts. All of it, the agents and the publishing, happens in a real Chrome signed in to your account, on one dedicated address reserved for that account, moving at a human pace. There is no LinkedIn API in this product, because LinkedIn revokes the apps that do what this one does.
Everything above is also a tool your own assistant can call. LinkedGrow is an MCP server: 26 tools
covering the agents, the leads and the posting, behind one URL and one key. Point Claude, Cursor or
ChatGPT at /api/mcp and ask for your warmest leads, or for next week's posts to be written and
spaced out, and it calls LinkedGrow to do it. The MCP page
has the configuration, which is three lines.
Install
LinkedGrow is 3 containers and a compose file. Take whichever of the 3 ways below suits you, they all end at the same place.
Hand it to an AI agent
An assistant with shell access to the server does the whole thing, because the run is written down for one in llms-install.md. Paste this into Claude Code, OpenClaw, Cursor or whatever you already point at your servers, with your own domain in it:
Install LinkedGrow on this server by following
https://raw.githubusercontent.com/DigiHold/LinkedGrow/main/llms-install.md
with the domain linkedgrow.example.com. Use no key of your own, create no
account, and give me the address to open once the health check answers.
Drop the domain from that prompt to serve on the server address over plain http instead. The agent reads the page, runs the installer, and comes back with the address in 2 or 3 minutes.
Docker Compose
The install every self hosted project uses, and it is 3 lines with nothing to edit. On a Linux host that already has Docker:
mkdir -p /opt/linkedgrow && cd /opt/linkedgrow
curl -fsSLO https://raw.githubusercontent.com/DigiHold/LinkedGrow/main/docker-compose.yml
docker compose up -d
When it comes up, open http://<your server address>:3000 in a browser. There is no .env to write, no secret to generate and no address to declare. The app generates its own signing and encryption secrets on the first start and keeps them in a Docker volume, it answers on whatever address you opened, and the wizard at first login asks for everything else.
If your server already uses port 3000, the third line stops on a message from Docker about the address being in use. Write the port you want into a .env next to the compose file and run it again:
echo APP_PORT=3001 >> .env
docker compose up -d
To pin a version or run https, see configuration and reverse proxy.
One command
The script runs exactly those commands and adds what a bare server needs: it installs Docker when the command is missing, sizes WORKER_SLOTS from the memory of the machine, starts Caddy for https when you give it a domain, and waits for the health check before printing the address.
curl -fsSL https://raw.githubusercontent.com/DigiHold/LinkedGrow/main/install.sh | sh
It asks one question, your domain, and an empty answer serves over plain http on the server address. Read it first if piping a script into a shell makes you uncomfortable, it is 500 lines of POSIX sh and it does nothing you have not seen above. Its options are in the install page, including --yes for a run that asks nothing.
Removing it
cd /opt/linkedgrow && ./install.sh uninstall
It asks you to type remove, then takes the containers, the volumes and the images with it. Add --keep-data to keep the volumes, so reinstalling later brings the instance back exactly as it was. The folder itself stays, with your compose file and your .env, and the script tells you the one line that removes it.
After any of the 3
The first start pulls about 4 GB, most of it the browser the worker drives. Open the address, create the first account, which administers the instance, and answer the wizard once.

./install.sh --source clones the repository into the stack folder and builds both images there, which takes about 10 minutes. From a checkout you already have, the build override does the same thing:
docker compose -f docker-compose.yml -f docker-compose.build.yml up -d --build
It replaces the 2 published images with a build of the working tree and leaves everything else alone, secrets and address included. Local development, tests and the database rules live in CONTRIBUTING.md.
Finding the leads
An agent is one LinkedIn account, one audience and its own dedicated address. The wizard reads your home page once and fills the targeting for you, then you correct whatever it got wrong: the job titles, the industries, the countries, the company sizes, and the topics your buyers write about. You pick where it looks, from people showing buying signals right now to the ones engaging with a competitor or sitting inside a LinkedIn search you already use. You also pick which moments count, such as a new job, a company hiring for the work you do, or a funding announcement.
After that it runs on its own, inside the working hours you set. It scores every profile it finds, leaves the ones that do not fit alone, and works through the rest inside the daily limit for that account. Replies land in an inbox on the dashboard. The agent answers the ordinary ones itself, and it hands you anything that needs a person, with the thread attached.

Writing the posts
The editor scores your draft on the hook, the length, the formatting and whether it ends on a question, and it says which line to spend 2 minutes on. The first comment is written next to the post and goes out a few minutes after it. A generator drafts from a topic in 4 steps when you would rather not start from a blank page, and Repurpose, Ideas and Hooks all feed the same editor.
Publishing goes through the worker rather than through an API. Press Publish and the post is queued, then written into the composer of your own account and read back off your feed to confirm it landed. A post you schedule for tomorrow is handed to LinkedIn's own scheduler hours before the slot, so nothing of ours has to be awake at 09:00. The analytics page then shows the impressions, reactions, comments and reposts the worker read off each post, and never an estimate.

Carousels and the rest of it
The carousel editor ships 25 preset templates across 6 styles, with text, shapes, frames, image upload and generation, and it exports to PDF for LinkedIn or to images. Around it sit the calendar, A/B testing, network notifications, team seats on one workspace, your own branding, and an API you can point your own tools at: a REST API under /api/v1 and the MCP server described above, both keyed by a token you create in Settings. The self hosted edition has every feature on, with no plan gate anywhere.

What runs
| Service | What it is |
|---|---|
app |
The Next.js dashboard and API on port 3000. It runs the migrations at boot and serves uploads from the uploads volume. |
worker |
A Node 24 process driving one Chrome per LinkedIn account under Xvfb. WORKER_SLOTS sets how many run at once, and it defaults to 2. |
db |
A libSQL server with its data in db-data, reached at http://db:8080 inside the stack, with no published port. |
caddy |
Optional, off unless you ask for it. With a domain it takes ports 80 and 443, gets the certificate and forwards to the app. |
Requirements
- A Linux host, amd64 preferred (see the note on arm64 below).
- Docker with the Compose plugin, which the installer sets up when the command is missing.
- 4 GB of RAM for 2 concurrent browsers (
WORKER_SLOTS=2), 16 GB for 12, and about 10 GB of free disk. - A domain pointing at the server for https, or an open port 3000 for a plain http trial.
- An AI key from Anthropic, OpenAI, Google, Grok or Kimi, which runs every agent on the instance.
- A Proxy-Seller account for one dedicated address per LinkedIn account, or proxies of your own.
Running it
cd /opt/linkedgrow && ./install.sh update pulls the current images and restarts the stack, which is what docker compose pull && docker compose up -d does by hand. Database migrations run when the app starts, and setting LINKEDGROW_VERSION=v1.0.0 in a .env next to the compose file pins a release instead of following the main branch. The updating page covers the tags and the rollbacks.
Four volumes hold everything: db-data for the database, uploads for files, profiles for the signed in browser sessions, and config for the 2 secrets the app generated on its first start. Back up all 4 together, because a database restored beside a different ENCRYPTION_KEY is unreadable and that key lives in config. The backups page has the archive and restore commands, and the reverse proxy page has the nginx and Caddy blocks, both for the bundled Caddy and for a proxy you already run.
Google Chrome ships for amd64 only on Linux, so on arm64 the worker image falls back to Chromium, which LinkedIn can tell apart from Chrome more easily. Release tags carry an arm64 image and latest does not, so an arm64 host runs a release tag or builds from source. Treat it as a way to try the product and run production on amd64. When something refuses to start, the troubleshooting page lists what the logs say and what to do about it.
About your LinkedIn account
LinkedIn restricts accounts that automate, and no tool changes that. LinkedGrow spaces its actions out, keeps one stable address per account, ramps a new account up over 2 weeks and ships conservative daily limits. The account is yours and so is the responsibility for how hard you push it, so start with the defaults and raise them slowly.
Docs and help
The full documentation lives on your instance at /docs, with the self hosting chapter under src/content/docs/self-hosting. Local development, the test commands and the rules a change has to follow are in CONTRIBUTING.md. Bugs and requests go to GitHub issues, and anything security related goes to the address in SECURITY.md rather than a public issue.
Built by Nicolas Lecocq and Maria Lecocq, copyright 2026 Vayalis, licensed under the AGPL-3.0, see LICENSE. A hosted version runs at linkedgrow.ai for people who would rather not run a server.
LinkedGrow MCP 질문
Claude 또는 Cursor를 LinkedGrow에 어떻게 연결하나요?
Settings에서 생성한 토큰과 함께 어시스턴트를 /api/mcp 엔드포인트로 지정하십시오. MCP 페이지에 세 줄로 된 설정 방법이 안내되어 있습니다.
LinkedGrow는 몇 개의 MCP 도구를 제공하나요?
이 MCP server는 에이전트, 리드, 게시물 작성을 아우르는 26개의 도구를 제공합니다.
LinkedGrow를 개인 서버에 어떻게 설치하나요?
세 줄의 명령어로 Docker Compose 스택을 실행하거나, 한 줄 설치 스크립트를 사용하거나, AI 에이전트가 설치 페이지를 따르도록 하십시오.
LinkedGrow에 AI provider 키가 필요한가요?
네, 인스턴스의 모든 에이전트를 실행하기 위해 Anthropic, OpenAI, Google, Grok 또는 Kimi의 AI 키를 제공해야 합니다.
LinkedGrow는 LinkedIn API를 사용하나요?
아니요, LinkedIn이 이러한 앱의 권한을 취소하기 때문에 대신 사용자의 계정에 로그인된 실제 Chrome을 구동합니다.