LeadAce
About
Outbound sales agent for Claude Code: per-prospect research, email writing, Gmail sending, reply tracking, and structured rejection feedback.
Details
- Author
- aitit-inc
- Categories
- Marketing, Other, AI
Jump to
Setup
Install LeadAce in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/aitit-inc/leadace
Follow the installation instructions in the repository README, then restart your MCP client.
Autonomous lead generation plugin for Claude Code. Builds prospect lists, runs outbound outreach, and iterates on strategy — all hands-free.
Two ways to run it.Use the hosted service atapp.leadace.ai(Free tier — 5 outreach/day, paid plans from $29/mo), orself-hostthe backend on your own Cloudflare + Supabase. The plugin is the same in either case — point it at the hosted MCP or your own.
claude plugin marketplace add aitit-inc/leadace && claude plugin install leadace@leadace
Or, from inside a running Claude Code session:
/plugin marketplace add aitit-inc/leadace /plugin install leadace@leadace
/plugin marketplace update /plugin update leadace@leadace
The first time the plugin calls a LeadAce tool, your browser opens for Google sign-in (the same Google account as the web app). The token is cached locally for subsequent runs. Seeplugin/README.mdfor details and troubleshooting.
Most commands take your project name as the first argument (chosen during/leadaceonboarding);/leadaceitself takes a free-form question or homepage URL.
Projects, prospects, outreach logs, and strategy documents live in the cloud — there are no local files to manage. Review everything in the web app athttps://app.leadace.ai.
flowchart TD LA["/leadace<br/>onboard · setup · strategy"] --> P{add prospects} P -- web search --> BL["/build-list"] P -- CSV / Excel --> IP["/import-prospects"] P -- reuse tenant --> MP["/match-prospects"] BL --> OB["/outbound"] IP --> OB MP --> OB OB --> CR["/check-responses"] CR --> EV["/evaluate"] EV -- next round --> P CR -. PMF signals .-> CF["/check-feedback"] CF -. revisit strategy .-> LA DC["/daily-cycle<br/>check + outbound + build, one shot"] SC["/setup-cron<br/>OS schedule"] --> DC DC -. replaces manual loop .-> P DEL["/delete-project"]
Solid arrows = the main loop. Dashed = optional / occasional / wrapper./evaluatealso consumes the tactical slice of rejection feedback (recontact requests, decision-maker referrals,not_relevantindustry clusters) recorded by/check-responses— no separate user step.
LeadAce is released under theLeadAce Open Source License— a modified Apache 2.0 with two additional conditions:
- No multi-tenant SaaSfor third parties without a commercial license from SurpassOne Inc. Self-hosting for your own organization is fine.
- Frontend logo and copyrightmust be preserved in any deployment exposing the LeadAce console.
- Free tier:1 project, 500 prospects, 5 outreach actions per day (100 lifetime cap)
- Paid plansstart at $29/month. Manage your subscription from the web app.
Seedocs/self-host.md. The self-hosted edition runs on the unlimited tier — no Stripe, no caps. For commercial-license inquiries, contactleo.uno@surpassone.com.
plugin/ # Claude Code plugin ├── .claude-plugin/plugin.json # Manifest ├── .mcp.json # MCP server config (uses LEADACE_MCP_URL) ├── skills/ # Slash commands (each directory has SKILL.md) ├── scripts/fetch_url.py # Local web fetch helper └── references/ # Shared reference docs backend/ # API + MCP servers (Cloudflare Workers, Hono, Drizzle) frontend/ # Web app (SvelteKit, Cloudflare Pages) docs/ # Project-wide docs (deploy runbook, self-host, architecture) docker-compose.yml # Bare Postgres for non-Supabase local dev
- Plugin conventions and the schema-change workflow:CLAUDE.md
- Self-hosting and local dev:docs/self-host.md
One-time setup — copy the env templates:
cp backend/.dev.vars.example backend/.dev.vars cp frontend/.env.example frontend/.env
Fill in the Supabase keys fromsupabase status— it prints them once the local stack is running, so runmake devonce first (it starts Supabase), then paste the keys in.
For Google sign-in to your local stack, also create a Google OAuth client and exportSUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_ID/_SECRETin your shell (via.envrc)beforethe firstmake dev— it boots Supabase, which reads them from the shell at start time. Seedocs/self-host.md → Local development. (These shell vars gate sign-in; theGOOGLE_CLIENT_ID/_SECRETinbackend/.dev.varsare separate — they power Gmailsend.)
Then start the whole stack with one command — Supabase, migrations, the master seed, the API/MCP Workers, and the frontend, all together. Ctrl-C tears the dev servers down (Supabase stays up for a fast restart;make stophalts it):
To run on different ports (e.g. one is taken by another dev server), copydev.ports.env.exampletodev.ports.envand set the ports there —dev.shrewires every dependent URL (and Google sign-in keeps working). Defaults are unchanged when the file is absent.
npx supabase start # Auth + Postgres on ports 54321/54322 cd backend npm install npm run db:migrate npx tsx scripts/seed-master-documents.ts npm run dev:api # API → http://localhost:8787 npm run dev:mcp # MCP → http://localhost:8788 (separate terminal) cd ../frontend npm install npm run dev # → http://localhost:5273
cd backend && npm run typecheck cd frontend && npm run check
npm installwithnode_modulesalready present can prune other-platform optional deps (@emnapi/,@img/sharp-,esbuildbinaries) frompackage-lock.json(npm/cli#7961, npm 10.3+–11.x). CI then runsnpm ciagainst that pruned lockfile and fails withMissing: … from lock file. This bites bothbackend/andfrontend/, and is what makes Dependabot's npm PRs go red.
When you change apackage.json/package-lock.json(or repair a Dependabot PR), regenerate the lockfile under the repo's pinned toolchain —notin Docker:
nvm use # node 22 (repo .nvmrc) — matches CI cd backend # or cd frontend rm -rf node_modules # removing this first is what avoids the prune npm install --no-audit --no-fund
Then commit the regeneratedpackage-lock.json. Code-only changes don't need this — CI consumes the committed lockfile as-is.
Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.
A shared campaign canvas for you and your AI agent: briefed by your brand rules, gated by your approval.
Run your Linkedin account from claude or chatgpt
Chat with any brand's Meta (Facebook/Instagram) ads inside Claude — research a competitor's ad library, surface their longest-running winners, extract hooks/formats, and clone winning ads for your own brand.
Market & competitive intelligence for Claude & AI assistants: trends, alerts, keywords & more.
Intelligent Growth: Product Marketing MCP Server
Run positioning, messaging, competitive analysis and launch planning from Claude or ChatGPT with a hosted product marketing MCP server.
Manage mailtani email marketing from Claude, Cursor, or any MCP-compatible AI agent — contacts, lists, campaigns, segments, and event tracking.
Google Ads reporting and campaign management for Claude; everything it creates starts paused, nothing spends until you turn it on.
Agent-operated social media management for agencies — publish, schedule, approve, and analyze posts across 11 networks (www.aidelly.ai).
Scores text and landing-page copy for AI-writing style tells; deterministic, offline, no LLM call and no network access.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
