Outbound Engine Mcp

io.github.closermethodPublished by GitHub account closermethodv1.0.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow Business & Commerce

Server details

Identifier: io.github.closermethod/outbound-engine-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account closermethod for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.closermethod%2Foutbound-engine-mcp.svg)](https://sourceweft.com/mcp/io.github.closermethod%2Foutbound-engine-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A cold-outreach method layer that gives an assistant tools to structure, audit and follow up on cold pitches for brand deals, UGC, jobs, podcasts and client…

What you can do: Structure a cold pitch into HOOK/BRIDGE/SOFT ASK with per-target swap variables
Audit a draft message for violations such as money in a cold message, generic hooks or hard asks, with a rewrite recipe
Build a five-step follow-up ladder and decide the next move for reply types like price questions, ghosting or exposure offers
Build a three-option pricing menu and scan replies or briefs for red flags such as spec work or pay-on-performance
Return the whole method pack as one payload for a system prompt
When to use it: Useful when an assistant drafts or reviews cold outreach and you want a consistent, reply-focused structure instead of long generic pitches. It suits creators and freelancers pitching brand deals, sponsorships, jobs, podcasts or client work who want audits and follow-up plans.
Requirements: Runs as a local process over stdio, installed from the npm package outbound-engine-mcp, so a Node.js runtime is needed. No accounts, API keys or environment variables are declared.

Before you install

It does not send messages or scrape prospects; it only returns frameworks and audits, so sending and research stay with you. Outputs are method guidance, not legal advice, and the README asks users to follow platform rules and outreach law for their channel and region. The README also points to a separate paid product.

Installation

In SourceWeft

Open Outbound Engine Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

// 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

Source: README.md at commit d16a11f

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.