24个MCP工作流：将GTM技术栈接入Claude

👋 This is a bi-monthly free edition of MKT1 Newsletter brought to you by our MKT1 MCP Showcase partners: Zapier, Framer, Softr, Attio, Airtable, Profound & Mutiny.

🔌 MKT1-ify your LLM with the MKT1 MCP: Bring ~40 skills we built for B2B Startup marketers to Claude Chat, Cowork, or Code. Add it to Claude in 1 click →

⬆️ Upgrade to a paid MKT1 subscription for: Full access to our MKT1 MCP | 100+ templates & resources | Post to MKT1 Job Board | MKT1 Newsletter Archive | $40K+ in discounts in the MKT1 Perk Stack

Subscribe now

We’ve entered the MCP era of AI at work, and there’s no turning back. You can’t build a truly AI-native system for work without connecting it to the rest of your stack.

Why? While Claude’s pretty useful on its own, when you connect it to other tools in your GTM stack it becomes infinitely more useful. And every GTM product worth its salt already has a robust MCP or CLI (command-line interface).

All of this can be overwhelming. Many marketers are still getting comfortable breaking out of ChatGPT or Claude Chat and moving into Cowork, Code, or Codex, so adding connectors is a whole other can of worms. Whether you’ve never used an MCP, have 20 connected, or are running MCPs and CLIs in Claude Code all day, it can be hard to know if you’re doing it right. Don’t worry, I’ll define all these acronyms and terms in the MCP 201 section below.

If you've been in this marketing-startup game for a while, you'll remember when “platform” and “integrations” swept SaaS tools. That's now happening with AI, and MCPs are the mechanism. We’ve seen this before!

With this in mind, we hosted an MKT1 MCP Showcase on 7/29, with 7 GTM tools live demoing their MCPs in Claude. The goal was to skip the fluff and demo workflows you can try right now.

So let's get to it. I'll break down what you need to know to get the most out of MCPs, define the other ways to connect your tools, and then get into the workflows from our 7 GTM tools (including video replays from the event to bring it all to life).

In this newsletter:

• MCP 201: Ways to connect Claude to other tools, get more out of your MCPs, and solve your most common LLM complaints.
• 21 workflows from 7 GTM tools: How to implement each one, plus video replays of the live demos from our MCP Showcase
• Featuring: Zapier | Framer | Softr | Attio | Airtable | Profound | Mutiny
• 3 workflows using the MKT1 MCP: Add MKT1's B2B marketing skills to your Claude workflows, from hiring and campaign briefs to auditing your finished work
• Watch the full video replay here →
• Some “inside baseball” for my most loyal MKT1 readers: Last edition I kicked off a 3-part series on multiplayer Claude. This newsletter isn’t part 2, it’s more of a first cousin to that series, as you can’t build a multiplayer system without MCPs. Part 2 will be out in 2 weeks though!

Subscribe now

Watch the full replay

We’ve also broken down the replay into chapters for each presenter throughout the newsletter if you’d prefer to watch that way.

Thanks to our Showcase partners

Here's who presented and what they demoed:

Zapier MCP: Run actions across any app you connect in Zapier, including tools with no MCP of their own. Learn more →

Framer CLI: Edit and publish your Framer site from Claude.

Offer: 30% off annual Pro with the code MKT1. Learn more →

Softr MCP: Create and update Softr databases and live apps from Claude. Learn more →

Offer: 2 free months of the Business plan for new users with the code MKT1-2MO.

Attio MCP: Query your CRM records, run reports on deal data, and mine insights from calls, all from Claude. Learn more →

Offer: 15% off your first year, using this link.

Airtable MCP: Bring your bases into Claude to query records, build tables and interfaces, and automate processes. Learn more →

Profound MCP: Analyze your AI search data and run Profound Agents from inside Claude. Free AEO report for MKT1 readers. Learn more →

Mutiny MCP: Build branded landing pages, deal rooms, and decks from Claude. Learn more →

The companies in this showcase and newsletter were hand-selected by me. I use their MCPs and think they’re valuable to my audience of marketers. In full disclosure, they also paid to participate (which makes events like this possible).

MCP 201: How to get the most out of Connectors

Connecting an MCP is just the start. Once connected, you can embed the functionality of these tools into everything you’re already doing in your LLM or AI harness. Before we jump into the workflows, I’ll explain how all of this works so they feel easier to understand and implement.

If you're already comfortable with MCPs, skip on down to the first set of workflows, from Zapier.

1. Ways to connect to Claude to other tools

Let's get some definitions out of the way first:

• MCP (aka MCP Server aka Model Context Protocol Server aka Claude Connector): How a tool tells Claude what it can do, so Claude can use that tool on your behalf. An MCP is essentially a bundle of actions, like send a Slack Message or pull AEO data from Profound.
• AI Harness (Claude Cowork, Claude Code, or Codex): Think of a harness as an infrastructure layer that wraps an AI model and gives it the ability to interact with other things outside the LLM.
• How it fits together: The MCP tells Claude what a tool can do, and the harness is what goes and does it.

Personal aside: My brother and I never had much in common career-wise. He builds ropes courses, using a harness. And now I build with AI, using a harness. Same same. Now strap in (harness pun!), let’s get back to the real content.

No MCP, no problem!

There are other ways to bring tools into your AI system, and sometimes they give you even more functionality than an MCP would.

Once you have an AI harness and/or are willing to run a few slightly more advanced prompts, you can connect to tools that don’t have an MCP yet or go beyond what their MCP supports.

Note: For the rest of this newsletter, I’ll use Claude Code as my default AI harness for simplicity, but you can do much of this in other AI harnesses, from Claude Cowork to Codex.

Here are the main ways to connect your tools to Claude:

2. How to get more out of your MCPs

Skills + MCPs + routines = magic in Claude. Well, most of the time.

You may have connected a bunch of MCPs already (though be careful how many, since they can slow things down). But a lot of people stop there and never really incorporate them into their workflows.

3 concepts will help you get much more out of your connectors: using multiple MCPs in the same session, wrapping a skill around an MCP so it works your way every time, and putting workflows on a schedule so they run without you.

Once you get a handle (or a harness?!) on all of this, it can genuinely change how you work. Claude starts to become a command center for your whole workday.

Here’s how each of these 3 concepts works:

3. How MCPs solve your most common LLM complaints

When helping each company choose workflows to demo, and then watching all 7 demos live, the same handful of patterns kept coming up. MCPs and CLIs solve many of the limitations you run into when using an LLM on its own.

Here’s how connectors help at a high level, across workflows:

Avoiding slop

• The problem: Working from a prompt alone, Claude produces generic output. It doesn't know your product, your customers, or your standards, so what comes back could have been made for any company.
• How MCPs solve it: By connecting Claude to the context that already lives in your tools (e.g. positioning guides in a doc, design guidelines in Figma), it can pull that knowledge directly into your sessions, workflows, and skills instead of relying on the prompt alone.
• Examples: When Claude has your web design guidelines from Framer, it can move much faster making new pages.

Adding a source of truth

There are two distinct use cases here worth separating:

Consolidating reporting from many sources