mcpField
N
newsletter-growth-mcp

newsletter-growth-mcp

Local
github.com/closermethodBusiness & Marketing0Updated 15w ago

About newsletter-growth-mcp

newsletter-growth-mcp gives newsletter publishers and creators practical frameworks for audience growth, onboarding, and monetization readiness. Its tools cover list engagement metrics as well as growth and email content checks.

Key features

  1. 01Outlines five newsletter growth loops
  2. 02Provides a six-email welcome sequence
  3. 03Audits subject lines for common issues
  4. 04Explains list-metric ranges and diagnostics
  5. 05Assesses monetization readiness
  6. 06Returns the complete guide in one payload

Use cases

  1. 01Choose a growth loop for a newsletter
  2. 02Build or review a welcome sequence
  3. 03Check subject lines before sending
  4. 04Evaluate readiness for sponsorships or products

MCP support

The MCP server exposes six tools for newsletter growth, email review, list metrics, and monetization readiness. MCP clients can retrieve individual guidance or the full pack.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"closermethod-newsletter-growth": {
"command": "npx",
"args": [
"-y",
"newsletter-growth-mcp"
]
}
}
}
Run commandnpx -y newsletter-growth-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmnewsletter-growth-mcp1.0.1

Tools

6

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
loopenumNolead_magnet | social_repurpose | cross_promo | referral | sponsorship_swap

Details

From the project README

Newsletter Growth MCP

Growth loops, welcome sequences, and monetization readiness for the only audience you actually own.

Disclaimer. Practitioner frameworks; thresholds are ranges, not guarantees. The author runs paid per-click sponsorships on her own list — these are the numbers sponsors actually pay on.

Why This Exists

Platform followers are rented; the list is owned. But most creators (and their AI agents) treat the newsletter as a broadcast afterthought: no welcome sequence, no growth loop, monetization guesses based on list size instead of engagement.

The house rule: engagement monetizes; size impresses. A 520-person list at 43% opens out-earns a 10k list at 12%.

6 Tools

ToolWhat it returns
get_growth_loop5 growth loops (lead magnet, social repurpose, cross-promo, referral, sponsorship swap) with when each wins and its failure mode
get_welcome_sequenceThe 6-email architecture: deliver → receipt → quick win → segment → soft offer → close
audit_subject_linePASS/NEEDS WORK: truncation length, spam phrases, fake Re:, specificity
interpret_list_metricHealthy/warning ranges + diagnostics for opens, clicks, growth, unsubs, replies
get_monetization_readinessGiven your list size + engagement: readiness verdicts for own product, per-click sponsorships, flat placements
get_full_packEverything in one payload

Install

npx newsletter-growth-mcp        # once published to npm
# or from source:
git clone https://github.com/closermethod/newsletter-growth-mcp && cd newsletter-growth-mcp && npm i && npm run build && node dist/main.js

Claude Desktop config:

{ "mcpServers": { "newsletter-growth": { "command": "npx", "args": ["newsletter-growth-mcp"] } } }

The Family

Own the audience (this one) ← get seen (content-hooks-mcp) ← get the reply (outbound-engine-mcp). Sponsorship deal terms live in creator-deals-mcp; inbox placement in outreach-deliverability-mcp. Full catalog: MCP Hub

Built By

Elisabeth Hitz — 10+ years enterprise sales; monetizes her own list with per-click sponsorships.

License: MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.