ebase

Outreach that won't get you flagged.

LinkedIn recruiting outreach that runs inside Claude Code — in your own signed-in Chrome, under LinkedIn's safe limits, so your account stays clean.

100% free. Open source. MIT licensed. Read every line before it touches your LinkedIn.

---

Cold to booked call in three sentences

Researched the profile. Wrote a personalized connection request. Sent it. Logged it to the pipeline. One command.

---

Who is this for

• Recruiters and talent partners tired of toggling between LinkedIn, a CRM, and a spreadsheet
• Founders doing their own sourcing who'd rather ship product than write cold DMs
• Anyone replacing Dripify, Expandi, Octopus, or Linked Helper and wanting something that won't get their account restricted

If you spend time on LinkedIn outreach every day, ebase turns that into a conversation with Claude.

---

Install

curl -fsSL https://raw.githubusercontent.com/embeddingvc/ebase/main/install.sh | bash

Then run /setup-outreach in Claude Code to configure your operator profile from LinkedIn.

Requirements: macOS · Python 3.10+ · Claude Code

What the installer does

The script does not require Make (suitable for a fresh Mac before Xcode Command Line Tools). It:

• Installs uv if it is missing, then runs uv sync and playwright install chromium (same as make install).
• Default: registers the LinkedIn MCP with Claude Code --scope user (all projects; stored in ~/.claude.json). Copies each skill under outreach/skills/<name>/ (with SKILL.md) into ~/.claude/skills/<name>/. Set EBASE_SYNC_SKILLS_HOME=0 to skip the skill copy only.
• --local (or EBASE_INSTALL_LOCAL=1): MCP --scope local only (this absolute project path); does not copy skills to ~/.claude/skills. Same idea as make claude-install LOCAL=1.
• Pre-allows ebase in Claude Code settings: MCP (mcp__linkedin), all repo skills (Skill(...)), and maintenance bash (bin/outreach-*, install.sh, uninstall.sh, make upgrade / uninstall / claude-install). Writes to ~/.claude/settings.json in default mode, or <repo>/.claude/settings.local.json with --local.
• If claude is missing, it prints next steps. ./install.sh --help lists options.
• Launches Google Chrome on macOS at the default path with remote debugging (CDP) on port 9222 (same idea as make browser), opens LinkedIn login, and pauses until you press Enter after signing in. Playwright automation attaches to that live Chrome session. Skip the pause with ./install.sh --skip-linkedin-login.
• Starts the cron scheduler via launchd (macOS) or systemd user unit (Linux) for auto-start at login/reboot (health: http://127.0.0.1:3847/health, logs: logs/cron.log). Skip with ./install.sh --no-cron.

Once it finishes, run /setup-outreach in Claude Code to scrape your LinkedIn profile, review the draft persona, and save outreach/config/persona.json. The cron scheduler then runs the workflow unattended; check it with make status.

By default this clones or updates the repo at ~/ebase. Override the directory with EBASE_DIR, the remote URL with EBASE_REPO (for forks), or git clone the repo and run ./install.sh from the repository root so an existing clone is used instead.

---

Why ebase

Your account stays safe

Every other outreach tool eventually gets your LinkedIn flagged. ebase doesn't blast — daily caps match what LinkedIn actually tolerates:

Action	Daily limit
Connection requests	25
Direct messages	50
Profile views	100

It hits the cap and stops with "resume tomorrow." No override, no workaround.

Not computer use — LinkedIn-native MCP

Generic "computer use" tools screenshot the page and guess where to click. ebase is different: it's a purpose-built MCP server that wraps Playwright to execute LinkedIn operations directly — structured profile scrapes, connection requests, DMs, engagement — with typed inputs and JSON outputs. No pixel-guessing, no screenshot parsing, no prompt-injected click coordinates.

The MCP drives your signed-in Chrome session over CDP. Not a headless browser, not a bot account — your real, authenticated session. You keep browsing normally while ebase works the pipeline alongside you.

Every skill is a task you already do

No dashboard to learn. No per-seat fees. Each skill maps to something you already spend time on every day:

What you'd normally do	ebase skill	What happens
Research + connect with a candidate	/send-connection-request	Reads their profile, writes a personalized note in your voice, sends, logs to pipeline
Check which requests got accepted	/sync-pending-connection	Verifies acceptance on LinkedIn, updates your connections list, queues follow-ups
Write a multi-touch DM sequence	/conversation-planner	Plans the next message based on thread history, your persona, and their profile
Set up your outreach voice	/setup-outreach	Scrapes your LinkedIn profile, builds your persona and tone config
Engage on a prospect's post	/reply-to-post	Writes a comment in your voice, confirms with you, posts it

Say what you want in plain English — each ask runs as a Claude skill:

› connect to linkedin.com/in/maya-khatri
› plan outreach for everyone who accepted this week
› reply to this post from jordan-liu
› follow up with last week's accepts

A day with ebase

Morning — "Connect to these 5 profiles from my shortlist." Five personalized connection requests go out in your voice. That's your only input.

Overnight — Routines sync accepts, plan follow-ups for each new connection, and drive conversations toward meetings — all while you sleep.

Next morning — Two meetings are on your calendar. You never opened LinkedIn again.

---

What's inside

Component	Description
LinkedIn MCP server	MCP tools wrapping Playwright — structured profile scrapes, connect, message, engage, persist. Typed inputs, JSON outputs, no screenshot guessing.
Claude skills	5 chainable workflows in ~/.claude/skills
Cron scheduler	Auto-syncs accepts, plans follow-ups, respects rate limits
Per-user state	Isolated prospects, threads, logs (JSON / JSONL)
One-command installer	uv · Playwright · MCP register

---

How it works

1. Install once — one curl command. uv, Playwright, the MCP server and skills register with Claude Code.
2. Sign in to Chrome — ebase drives your real, authenticated Chrome session. Nothing headless, nothing to flag.
3. Ask Claude — "Connect to this profile." "Follow up with last week's accepts." Natural language in, real outreach out.
4. It stays safe — every action is logged and capped to LinkedIn-safe daily limits. The agent refuses to cross them.

---

Documentation

• Quickstart (live + mock) — make browser + make cron, live mode checklist, example prompts
• Architecture & capabilities — components, MCP tool inventory, workflow diagrams
• Claude skills — setup-outreach, conversation-planner, send-connection-request, and more
• Manual install & Claude Desktop MCP — prerequisites, make install, claude_desktop_config.json
• Conversation planner config — runtime persona + campaign config
• Operations — environment variables, data layout, Make targets
• Design notes — internal design docs
• Testing & dev dashboard — web dashboard UI, mock mode, regression suite
• Contributing — dev setup, testing, how to submit changes
• Changelog — version history and release notes

License

MIT