{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/65d4445a7e29af00164868b8/6a7df2dcf8e81c4395876a2a?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Ep. 135 - How I Use Kit's MCP + Claude to Market More Effectively","description":"<p>Whitney has a confession: for years, her entire Kit routine has been logging in, glancing at her subscriber count, and closing the tab. The data was always there — who opens what, who clicks, where people came from — but getting at it meant exporting reports and crunching numbers, and it never made it to the top of the list. This episode is about what changed. Kit now has an MCP connector, which lets you plug your account into Claude or another AI tool and simply ask questions about your own list. Whitney covers what MCP actually means, how to set the connection up, the prompts Kit suggests, the two use cases earning their keep in her business right now, and the one feature she tried that wasn't ready for her workflow.</p><p><br></p><h5><strong>Takeaways:</strong></h5><ul><li><strong>MCP is a common language between your software and your AI tool.</strong> It stands for Model Context Protocol, and it lets a platform like Kit hand your AI tool a reliable set of instructions for reading subscribers, reading emails, and pulling activity data. Whitney compares it loosely to Zapier connecting two tools, with the difference that an MCP isn't a paid layer.</li><li> <strong>Good analysis depends entirely on good data going in.</strong> Whitney's caveat throughout: if your tagging and attribution are sloppy, the AI has nothing meaningful to work with. Her example is giving a talk at a conference — build a separate landing page, automation, and tag for that specific event, even if you offer the same resource elsewhere, so you can actually trace who came from it and whether any of them became clients.</li><li> <strong>The strongest use case is analysis, not drafting.</strong> Whitney tried Kit's suggested workflow for importing an external draft into a broadcast and it came in as code she couldn't edit in the native block builder. She still makes small tweaks to every email inside Kit, so that broke her workflow.</li><li> <strong>Whitney's first real use case: profiling subscribers coming in from ads.</strong> She has Claude look at what new subscribers are clicking and opening, pushes that into Airtable, and uses it to identify specific people worth reaching out to directly. That kind of data crunching used to take repeated manual passes.</li><li> <strong>Her second: using past emails as source material for new content.</strong> She had Claude pull the emails from an existing sequence on a topic and reference them while writing new marketing content, so the new work carries her actual philosophy, themes, and voice rather than starting from scratch. You can also surface which subject lines performed best and repurpose emails that landed months ago.</li></ul><p><br></p><h5>Resources Mentioned</h5><ul><li>Kit (formerly ConvertKit) — the MCP connector lives in the left sidebar under Automation, on a paid plan</li><li> Claude — the AI tool Whitney uses for these connections</li><li> EmailOctopus — a simpler, lower-cost starter email platform a colleague introduced her to</li><li> Airtable — where she pushes subscriber activity data for further analysis</li><li> Zapier — referenced as a loose analogy for connecting two tools</li></ul><p><br></p><h5><strong>Connect with Whitney</strong>:</h5><p>Follow Whitney on Instagram<a href=\"https://instagram.com/whitneybateson\" rel=\"noopener noreferrer\" target=\"_blank\"> @whitneybateson</a></p><p><br></p><h5><strong>Subscribe &amp; Review:</strong></h5><p>If you’re enjoying the podcast, don’t forget to follow and leave a review! Your support helps others discover the show.</p>","author_name":"Whitney Bateson"}