Writing the email is not the hard part anymore.

That part is easy.

The real work starts after the draft.

You still need to build the list, set up the sequence, check sender health, make sure the infrastructure is fine, and figure out why performance dropped. Most teams are still doing that across too many tools.

That is what makes Forge MCP interesting.

It connects six parts of the Forge stack through one MCP server, so Claude can do more than just help with copy. It can work across the actual systems behind outbound.

One MCP server for the rest of outbound

Salesforge
Sequences, contacts, sender profiles, enrollments, validation, and DNC lists.

Leadsforge
Lead search, enrichment, phone numbers, emails, LinkedIn data, and lookalikes.

Primeforge
Prewarmed sending setup, domains, DNS, and workspace setup.

Infraforge
Dedicated infrastructure, domains, DNS, and private IP setup.

Warmforge
Warmup, heat score checks, and placement tests.

Mailforge
Shared IP email infrastructure with domains, DNS, and credits.

You can ask Claude to build the sequence, pull the list, and check what is hurting performance across the stack.

That is the value. Here is the guide

See it in action

I’m doing a live session with Arty Jurkevich on how to build 50 multi-channel sequences in a day with Claude Code.

One more session worth joining

I’m doing a live session with Deborah Stiernon from HubSpot for Startups on what a real outbound engine needs to drive more replies, more meetings, and more pipeline.

This is what outbound looks like when the full stack runs as one system.