Skip to main content
How I AI

How this PM uses MCPs to automate his meeting prep, CRM updates, and customer feedback synthesis | Reid Robinson (Zapier)

40 min episode · 2 min read
·
Reid Robinson

Episode

40 min

Read time

2 min

Topics

Remote Work, Leadership, Artificial Intelligence

AI-Generated Summary

Key Takeaways

  • MCP Implementation Strategy: Think of MCPs as app integrations for AI tools rather than technical infrastructure. Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL. Zapier's MCP platform exposes 30,000 actions across 8,000 apps, letting users build role-specific tool sets that work automatically when employees log in.
  • Claude Projects for Tool Orchestration: Use Claude Projects to provide detailed instructions on which MCP tools to use, in what sequence, and how to populate specific fields. This approach solves the tool-calling priority problem where models struggle to select the right tool. Create separate projects for different workflows like CRM updates or daily planning, each with customized instructions that dramatically improve execution accuracy across multiple sequential tools.
  • Automated CRM Workflow: Build a post-meeting workflow that searches internal databases for existing customer records, looks up company usage data through internal tools like Glean, and creates or updates CRM entries with meeting notes and next steps. Train the model on your specific CRM fields and custom choices since every organization uses unique configurations. This eliminates the manual task customer-facing teams universally hate.
  • Model Selection by Data Type: Choose Google Gemini models specifically for file-based workflows, particularly PDFs and HTML documents. Gemini handles large file contexts more effectively and uses fewer tokens than OpenAI or Anthropic models. For customer research workflows that pull HTML data from internal systems, convert to files before processing to optimize both performance and cost while maintaining output quality.
  • Self-Improving Knowledge Base: Create a system where closed support tickets and chatbot transcripts automatically analyze conversations to identify core FAQs, compare against existing knowledge bases, and propose new entries for human review. Approved entries feed directly into customer-facing chatbots. This maintains up-to-date help content without manual quarterly reviews, improving answer quality while operating at scale that manual teams cannot achieve.

What It Covers

Reid Robinson, Product Manager at Zapier, demonstrates how Model Context Protocol servers transform AI tools into automated assistants for customer-facing work. He shows practical implementations using Claude Projects with Zapier's 8,000-app MCP platform to automate CRM updates, meeting preparation, and customer feedback synthesis while maintaining data quality through human-in-the-loop workflows.

Key Questions Answered

  • MCP Implementation Strategy: Think of MCPs as app integrations for AI tools rather than technical infrastructure. Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL. Zapier's MCP platform exposes 30,000 actions across 8,000 apps, letting users build role-specific tool sets that work automatically when employees log in.
  • Claude Projects for Tool Orchestration: Use Claude Projects to provide detailed instructions on which MCP tools to use, in what sequence, and how to populate specific fields. This approach solves the tool-calling priority problem where models struggle to select the right tool. Create separate projects for different workflows like CRM updates or daily planning, each with customized instructions that dramatically improve execution accuracy across multiple sequential tools.
  • Automated CRM Workflow: Build a post-meeting workflow that searches internal databases for existing customer records, looks up company usage data through internal tools like Glean, and creates or updates CRM entries with meeting notes and next steps. Train the model on your specific CRM fields and custom choices since every organization uses unique configurations. This eliminates the manual task customer-facing teams universally hate.
  • Model Selection by Data Type: Choose Google Gemini models specifically for file-based workflows, particularly PDFs and HTML documents. Gemini handles large file contexts more effectively and uses fewer tokens than OpenAI or Anthropic models. For customer research workflows that pull HTML data from internal systems, convert to files before processing to optimize both performance and cost while maintaining output quality.
  • Self-Improving Knowledge Base: Create a system where closed support tickets and chatbot transcripts automatically analyze conversations to identify core FAQs, compare against existing knowledge bases, and propose new entries for human review. Approved entries feed directly into customer-facing chatbots. This maintains up-to-date help content without manual quarterly reviews, improving answer quality while operating at scale that manual teams cannot achieve.

Notable Moment

Robinson shares how he solved family calendar chaos by photographing a physical wall calendar and using Claude with Google Calendar MCP tools to automatically create events, calculate drive times for school pickups during work hours, and block his schedule. This prevents meeting conflicts while maintaining his wife's preferred analog system and his digital workflow needs.

Know someone who'd find this useful?

Episode Transcript

MCPs, I will say, it's a concept that's really hard to understand for folks. Yeah. Definitely don't think about the word. It really just is like app integrations for your AI tools. You can create these collections of tools from all the apps you use and give them access to Claude, to Chatubit, to Cursor, all the places that have inputs for MCP servers today. I use agents all the time, but it is hard to break that muscle memory of this is a deterministic workflow versus an instructive agent, even if it has access to the same tools and can do the same things. And when it comes down to it, the two things we see people wanting to do is, one, giving their favorite AI tool the access to knowledge that lives in their apps, as well as giving them the ability to actually do things in those apps. Those are the two things that if that sounds like something that you need in an AI app you use, look for MCP or connectors as it's often being called now as well for that. Welcome back to How I AI. I'm Claire Vaux, product leader and AI obsessive here on a mission to help you build better with these new tools. Today, I'm talking to Reid Robinson, product manager on AI at Zapier. And what I love about my conversation with Reid is he's gonna show us how to put MCPs to work inside Quad to take over tasks that you really hate. We also talk about whether AI can be the perfect always on team that works while you sleep and some use cases to make your kids and your partner a little happier. Let's get to it. This episode is brought to you by Work OS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch. These tools only work well when they have deep access to company systems. Your copilot needs to see your entire code base. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where WorkOS comes in. WorkOS gives you drop in APIs for enterprise features so your app can become enterprise ready and scale up market faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at workos.com. Start building today. Hey, Reed. Thanks for joining How IAI. Thanks for having me here, Claire. Excited to chat today. What I love about how you've described your role at Zapier, which I use all the time I say …

Get the full transcript (7,496 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all How I AI transcripts →

You just read a 3-minute summary of a 37-minute episode.

Get How I AI summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • Claude ProjectsRecommended

    by Anthropic

    Use Claude Projects to provide detailed instructions on which MCP tools to use, in what sequence, and how to populate specific fields. This approach solves the tool-calling priority problem where models struggle to select the right tool.
  • Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL.
  • Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL.
  • Build a post-meeting workflow that searches internal databases for existing customer records, looks up company usage data through internal tools like Glean, and creates or updates CRM entries with meeting notes and next steps.
  • by Google

    Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL.
  • Google GeminiRecommended

    by Google

    Choose Google Gemini models specifically for file-based workflows, particularly PDFs and HTML documents. Gemini handles large file contexts more effectively and uses fewer tokens than OpenAI or Anthropic models.
  • by OpenAI

    Create custom collections of tools from apps like Slack, Google Calendar, and CRM systems, then connect them to Claude, ChatGPT, or Cursor through a single URL.

company

  • SPONSORS [{'name': 'WorkOS', 'url': 'workos.com'}
  • ZapierBy guest
    Reid Robinson, Product Manager at Zapier, demonstrates how Model Context Protocol servers transform AI tools into automated assistants for customer-facing work.
  • SPONSORS {'name': 'Vanta', 'url': 'vanta.com/howiai'}

More from How I AI

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into How I AI.

Every Monday, we deliver AI summaries of the latest episodes from How I AI and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime