lessie-skill MCP — Use Cases, Install & Live Demo

Why use it

Key features

People search with filters: titles, companies, locations, domains
Contact enrichment returning verified emails and phones
Company research: industry, funding, tech stack, hiring signals
Integrated email send/manage across Gmail, Outlook, other providers
Delivered via CLI (@lessie/cli) or MCP server across Claude Code / Cursor / Codex

Live Demo

What it looks like in practice

lessie-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "lessie-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/LessieAI/lessie-skill",
        "~/.claude/skills/lessie-skill"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "lessie-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/LessieAI/lessie-skill",
        "~/.claude/skills/lessie-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "lessie-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/LessieAI/lessie-skill",
        "~/.claude/skills/lessie-skill"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "lessie-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/LessieAI/lessie-skill",
        "~/.claude/skills/lessie-skill"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "lessie-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/LessieAI/lessie-skill",
        "~/.claude/skills/lessie-skill"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "lessie-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/LessieAI/lessie-skill",
          "~/.claude/skills/lessie-skill"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add lessie-skill -- git clone https://github.com/LessieAI/lessie-skill ~/.claude/skills/lessie-skill

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use lessie-skill

Build a B2B prospect list for a sales sequence

👤 Founders, SDRs, agency owners running targeted outreach ⏱ ~45 min intermediate

When to use: You need 50 qualified contacts for a specific campaign without a Sales Navigator seat.

Prerequisites

Skill cloned + Lessie account — git clone https://github.com/LessieAI/lessie-skill ~/.claude/skills/lessie-skill; sign up at lessie for API key

Flow

Define the ICP

Use lessie-skill — find Engineering Managers at SaaS companies, 50-500 employees, using Stripe, HQ in EU.✓ Copied

→ Lessie find-people call with filter JSON, not generic search
Enrich contacts

Enrich the top 25 with verified email.✓ Copied

→ Emails plus validation status returned
Draft personalized emails

Draft individualized openers using each person's recent company news. No spam phrases.✓ Copied

→ Per-contact personalization, not copy-paste

Outcome: A usable prospect list with personalized opener drafts.

Pitfalls

Treating 'verified' email as guaranteed deliverable — Warm your sending domain and monitor bounces — verification is probabilistic

Combine with: github

Source engineering candidates for a specific role

👤 Recruiters and hiring managers on small teams ⏱ ~30 min intermediate

When to use: You need a shortlist before pinging a recruiter.

Flow

Search

lessie-skill — find Senior Rust engineers in Berlin or remote EU, with distributed systems background.✓ Copied

→ Targeted list with signals (seniority, stack evidence)
Qualify

For the top 10, summarize each in two sentences: strongest fit signal + one reservation.✓ Copied

→ Honest summaries, not just enrichment fields

Outcome: A human-readable shortlist ready for outreach.

Combinations

Pair with other MCPs for X10 leverage

lessie-skill + github

Research GitHub activity of candidates alongside Lessie profile data

For the Rust shortlist, cross-reference each person's GitHub contributions to Rust projects.✓ Copied

lessie-skill + claude-content-writer-skill

Draft personalized outreach sequences in your brand voice

Using claude-content-writer voice profile, draft 3-email sequences for the top 10 prospects.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
find-people	title / company / domain / location filters	Starting from ICP filters	Lessie plan-dependent
enrich-contact	person id or profile	Shortlist narrowed and ready to contact	Per-enrichment credit
find-company	company name or domain + optional filters	Account research before outreach	Plan-dependent
send-email	Gmail/Outlook account + to/subject/body	Only after you review drafts — don't auto-send at scale	Uses your own mailbox

Cost & Limits

What this costs to run

API quota: Depends on Lessie plan — the skill itself is just the prompt wrapper
Tokens per call: Moderate; responses can be large when listing 50+ contacts
Monetary: Free — skills are local files. Lessie's data API is paid; consult current plans.
Tip: Filter aggressively before enrichment; every enrichment call costs credits.

Security

Permissions, secrets, blast radius

Credential storage: Lessie API key in env var; Gmail/Outlook via OAuth if you use send-email

Data egress: Queries go to Lessie's API. Email sending goes via your provider.

Contact enrichment must comply with GDPR / CAN-SPAM / local laws — Lessie provides data, compliance is on you.
Don't automate bulk sends without warming; volume without domain reputation = spam folder.

Troubleshooting

Common errors and fixes

Skill not invoked — Claude offers generic LinkedIn advice

Say 'use lessie-skill' explicitly.

Verify: ls ~/.claude/skills/lessie-skill/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives activation.

Verify: head ~/.claude/skills/lessie-skill/SKILL.md

Wrong trigger keywords — enrichment runs before filtering narrows the list

Explicitly: 'first find-people, then I'll pick who to enrich'.

Alternatives

lessie-skill vs others

Alternative	When to use it instead	Tradeoff
Apollo.io / Clay	You want a full GTM suite with sequencing tools	Much heavier platforms; pricier
LinkedIn Sales Navigator	LinkedIn-native prospecting with InMail	Expensive, no agent integration

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills