Outbound Engine MCP

One cold-outreach engine for any target: HOOK/BRIDGE/SOFT-ASK, follow-up ladder, reply playbook.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "outbound-engine-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "outbound-engine-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Outbound Engine MCP

The cold-outreach method layer for AI agents. One engine, any target: brand deals, UGC, newsletter sponsorships, jobs, podcasts.

Built from the method behind The Outbound Engine.

Disclaimer. Outputs are structured outreach-method frameworks based on documented practice. Results vary by niche, proof quality, and consistency. Not legal advice. Follow platform rules and outreach law for your channel and region.

Why This Exists

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.

This MCP encodes one rule and enforces it with tools:

A cold pitch is not trying to close a deal. It is trying to get a reply. The deal closes in the follow-up.

It does NOT send messages and does NOT scrape prospects. It is the method layer: give it a draft, a target type, or a reply — get back structure, violations, and the next move.

7 Tools

Tool	What it returns
`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 rewrite recipe
`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

Sample Use

typescript

// Agent drafted a cold DM for a brand deal. Before sending:
mcp.call("audit_cold_message", {
  message: "Hi, I'm a UGC creator with 50k followers! I love your brand. My rate is $500/video...",
  target_type: "brand_deal"
});
// Returns: FAIL — no_money_in_cold_message, no_identity_first_opener,
// specific_hook_required + a 3-move rewrite recipe.

// Prospect replied asking "what do you charge?"
mcp.call("handle_reply", { reply_type: "price_question" });
// Returns: don't send one number — two scoping questions first, then the 3-option menu.

Target Types

brand_deal · ugc · newsletter_sponsorship · job · podcast · client_work

Same engine, four swapped variables per target. That's the whole trick.

The Full System

This MCP is the free method layer. The full Outbound Engine product adds per-target research packs, an onboarding intake that builds your proof inventory, and the daily operating system — at elisabethhitz.com.

Built By

Elisabeth Hitz — 10+ years of B2B enterprise sales experience across ad-tech, SaaS, media, and global hiring. Now building MCP servers for the AI agent ecosystem.

License: MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Outbound Engine MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "outbound-engine-mcp": { "command": "npx", "args": ["-y", "outbound-engine-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Outbound Engine MCP AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/outbound-engine-mcp?style=directory)](https://allmcps.com/mcp/outbound-engine-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/outbound-engine-mcp"><img src="https://allmcps.com/api/badge/outbound-engine-mcp?style=directory" alt="Outbound Engine MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Outbound Engine MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Outbound Engine MCP

The cold-outreach method layer for AI agents. One engine, any target: brand deals, UGC, newsletter sponsorships, jobs, podcasts.

Built from the method behind The Outbound Engine.

Disclaimer. Outputs are structured outreach-method frameworks based on documented practice. Results vary by niche, proof quality, and consistency. Not legal advice. Follow platform rules and outreach law for your channel and region.

Why This Exists

This MCP encodes one rule and enforces it with tools:

A cold pitch is not trying to close a deal. It is trying to get a reply. The deal closes in the follow-up.

It does NOT send messages and does NOT scrape prospects. It is the method layer: give it a draft, a target type, or a reply — get back structure, violations, and the next move.

7 Tools

Tool	What it returns
`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 rewrite recipe
`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

Sample Use

typescript

// Agent drafted a cold DM for a brand deal. Before sending:
mcp.call("audit_cold_message", {
  message: "Hi, I'm a UGC creator with 50k followers! I love your brand. My rate is $500/video...",
  target_type: "brand_deal"
});
// Returns: FAIL — no_money_in_cold_message, no_identity_first_opener,
// specific_hook_required + a 3-move rewrite recipe.

// Prospect replied asking "what do you charge?"
mcp.call("handle_reply", { reply_type: "price_question" });
// Returns: don't send one number — two scoping questions first, then the 3-option menu.

Target Types

brand_deal · ugc · newsletter_sponsorship · job · podcast · client_work

Same engine, four swapped variables per target. That's the whole trick.

The Full System

Built By

Elisabeth Hitz — 10+ years of B2B enterprise sales experience across ad-tech, SaaS, media, and global hiring. Now building MCP servers for the AI agent ecosystem.

License: MIT

Frequently Asked Questions about Outbound Engine MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "outbound-engine-mcp": { "command": "npx", "args": ["-y", "outbound-engine-mcp"] } }