Newsletter growth loops, welcome-sequence architecture, subject-line and list-metric guidance.
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.
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%.
| Tool | What it returns |
|---|---|
get_growth_loop | 5 growth loops (lead magnet, social repurpose, cross-promo, referral, sponsorship swap) with when each wins and its failure mode |
get_welcome_sequence | The 6-email architecture: deliver → receipt → quick win → segment → soft offer → close |
audit_subject_line | PASS/NEEDS WORK: truncation length, spam phrases, fake Re:, specificity |
interpret_list_metric | Healthy/warning ranges + diagnostics for opens, clicks, growth, unsubs, replies |
get_monetization_readiness | Given your list size + engagement: readiness verdicts for own product, per-click sponsorships, flat placements |
get_full_pack | Everything in one payload |
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"] } } }
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
Elisabeth Hitz — 10+ years enterprise sales; monetizes her own list with per-click sponsorships.
License: MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y newsletter-growth-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-closermethod-newsletter-growth-mcp": {
"command": "npx",
"args": [
"-y",
"newsletter-growth-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencenewsletter-growth-mcpnpmio.github.closermethod/newsletter-growth-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.