Outbound MCP Server

One cold-outreach engine for any target: HOOK/BRIDGE/SOFT-ASK, follow-up ladder, reply playbook. The outbound mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

Every AI agent that drafts cold outreach today has the same failure mode: it writes long, polite, generic pitches that ask a stranger for the biggest possible thing on the first touch. Those messages don't get replies, and outreach that doesn't get replies doesn't get deals.

Its toolset

Everything the assistant can do here goes through one of these:

• structure_cold_pitch — HOOK / BRIDGE / SOFT ASK structure + the 4 swap variables (who to pitch, signal to research, proof to lead with, soft-ask object) per target type
• audit_cold_message — PASS/FAIL audit of a draft: money in a cold message, identity-first opener, generic hook, hard ask, length over ~90 words, multiple asks — with a
• build_followup_ladder — The 5-step ladder (Day 3 / 7 / 12 / 18 / 25) — where 80% of deals actually close. The Day 25 break-up alone pulls ~30% of replies
• handle_reply — The next move for any reply type: price question, interested, not now, no budget, exposure offer, spec request, pay-on-performance, ghosted
• build_pricing_menu — The 3-option menu (Starter / Most Popular / Full) + the two scoping questions to ask first. Drop scope, never price
• detect_red_flags — Scans a reply or brief for walk-away signals: exposure-pay, spec work, pay-on-performance, budget mismatch, scope creep
• get_full_pack — The complete engine as one payload — drop it into a Claude Project system prompt

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Outbound's toolset — structure_cold_pitch, audit_cold_message, build_followup_ladder and 4 more — is a fair guide to whether it matches your workflow. It is maintained by closermethod; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the outbound mcp server does with a few real requests.