top of page
Denver 1.jpeg

My Blog

 

How to Connect Any App to Claude Cowork With an MCP Connection

  • Writer: Jerad Larkin
    Jerad Larkin
  • 13 minutes ago
  • 7 min read

What is an MCP connection in Claude Cowork?

An MCP connection is a bridge that lets Claude Cowork reach apps that are not on its built-in connector list, and gives you fuller access to the ones that are. You set one up through an automation platform like Zapier, Make, or n8n.

If you have been using Claude Cowork for a few weeks, you have probably hit the wall I am about to describe.

You start dabbling. You build a skill. You add a connector. You get a workflow running and it feels like the future. Then you ask Claude to send an email, and it drafts a beautiful one and stops. It will not hit send. Or you go looking for your CRM in the connector list and it simply is not there.

That is the moment most people quietly give up on Cowork, right at the point where it gets good. The thing is, that is not a Claude limitation. It is a connection problem, and it has a fix.

What this video covers

  • Why the built-in Gmail connector drafts your email but will not send it

  • What an MCP connection actually is, in plain language

  • How to add Zapier, Make, or n8n as a connector inside Claude Cowork

  • How to create your MCP server in Zapier and point it at Claude

  • How to connect the CRM and the other apps that are not on Claude's list

The problem: built-in connectors are the trailer, not the movie

Claude Cowork ships with a connector library. You go to Customize, then Connectors, then Browse, and there is a list of apps you can hook up in a couple of clicks. Gmail is there. Zoom is there. Plenty of others are there.

Here is what nobody tells you: those built-in connectors often carry limited functionality compared to what the app itself can actually do.

I run into this constantly. Gmail is the cleanest example. Through the built-in connector, Claude will write the email, format it, and hand it to you as a draft. It will not send it. That is by design, and for a lot of people that is exactly what they want. But if your whole point was to automate the send, you are stuck.

Zoom is the same story. I have Zoom connected in Cowork, and it works fine for what it does, but it does not give me everything I want to do with Zoom. When I connect Zoom through an MCP connection instead, I get a much wider set of actions.

So there are really two problems, not one:

  1. The app is not on the list at all. Most CRMs fall here.

  2. The app is on the list, but the connector only does part of what you need.

An MCP connection solves both.

What an MCP connection actually is

Think of it as a bridge.

Instead of Claude talking directly to one app through a purpose-built connector, Claude talks to an automation platform, and that platform talks to everything else. You connect Claude to Zapier once. Then inside Zapier you connect Gmail, your CRM, your calendar, your project tool, whatever you use. Claude reaches all of it through that single bridge.

The practical effect is that Claude Cowork stops being limited to its own connector list and starts being able to touch anything you have already connected to your automation platform. That is thousands of apps instead of a few dozen.

You have three main options for the bridge:

  • Zapier, what I use, and what the steps below cover

  • Make, a direct competitor, same general idea

  • n8n, more technical, more control

Any of the three will work. I have always used Zapier, so that is what I am used to and what I will walk you through. Pick one and stick with it rather than trying to run all three.

How to set up an MCP connection, step by step

Step 1: Add the connector inside Claude Cowork

Open Claude Cowork and go to Customize, then Connectors, then Browse connectors. Search for Zapier. You will also find Make and n8n in there if you would rather use one of those.

Connect the one you want. This is the Claude side of the bridge.

Step 2: Set up your automation platform account

If you do not already have one, go to zapier.com and create an account. Nothing fancy required to start.

Step 3: Find MCP Servers in the left sidebar

Once you are logged in to Zapier, look at the left-hand navigation and find the option that says MCP Servers. That is where this whole thing lives.

Step 4: Add your MCP server

Click Add MCP Server. It will ask you to choose your AI agent. Since we are talking about Claude Cowork, choose Claude.

Zapier makes this genuinely easy. They even hand you a prompt you can copy and paste straight into Claude to finish the connection. You do not have to figure out the wiring yourself.

Step 5: Connect your apps

This is the payoff step, and it is the one worth spending time on.

Once the MCP server exists, you start adding apps to it. Find the app, connect it, repeat. My own server has Zoom, Gmail, Avoma, and a stack of other tools I use to run my business.

Add the ones you actually use. Do not add thirty apps you touched once. The point is to build a bridge to your real workflow, not to collect connections.

Why this matters more than it sounds like it does

Here is the part I want agents to actually sit with.

Most of the time you save with AI does not come from the writing. It comes from removing the handoffs. Right now your workflow probably looks like this: Claude drafts something, you copy it, you open another tab, you paste it, you fix the formatting, you hit send. Every one of those steps is a place where the task stalls out and sits in your open loops for another day.

An MCP connection is what closes those loops. The follow-up email actually goes out. The new lead actually lands in your CRM. The meeting notes actually get filed. The workflow finishes instead of ending in a draft you never get back to.

That is the difference between AI being a neat toy and AI being a system.

One honest note, and I say this in every class I teach: AI gets you 85 to 95 percent of the way there. You are still the expert and you still make the final call. Connecting your CRM to Claude does not mean you stop reading what goes out under your name. Build the bridge, then review what crosses it.

A few things to keep in mind before you build

  • Start with one app, not ten. Get Gmail or your CRM working end to end before you add anything else. You want to understand the pattern before you scale it.

  • Watch what you are giving access to. An MCP connection is real access to real accounts. Be deliberate about which apps go on the bridge and who can trigger them.

  • Built-in and MCP can coexist. You do not have to delete the built-in Gmail connector to add Gmail through Zapier. I run both.

  • Check your brokerage rules. If you work at a shop with policies around client data and third-party tools, get the connection cleared before you wire your CRM into anything. Rules vary by brokerage.

Where I fit in all this

I am Jerad Larkin, Account Executive with Chicago Title of Colorado, and this is the kind of thing I teach constantly.

Chicago Title has been the title partner for agents across Colorado for a long time, and part of how I see my job is making sure the agents I work with are not falling behind on the tools that are changing how this business runs. I teach over a hundred classes and events a year across Denver Metro, a lot of them on AI, marketing, and building systems that hold up when you get busy.

Title is the part I get paid for. The AI training is the part I do because agents keep asking for it and because I would rather work with agents who are growing.

FAQ

Do I need to know how to code to set up an MCP connection?

No. Zapier walks you through it and even hands you a prompt to paste into Claude to finish the connection. If you can set up a connector inside Claude Cowork, you can do this. n8n is more technical, so start with Zapier or Make if you are not a developer.

Why won't Claude Cowork send my emails through the built-in Gmail connector?

The built-in connector is scoped to drafting rather than sending. It will compose the email and hand it to you, and you approve the send yourself. If you want Claude to actually send, route Gmail through an MCP connection instead.

Is Zapier better than Make or n8n for this?

They all do the same core job. Zapier is what I use and what I am comfortable recommending because I know it. Make is a close competitor with a similar feel. n8n gives you more control if you are technical. Pick one and go, rather than splitting your setup across platforms.

Can I connect my CRM to Claude Cowork this way?

Most likely yes. If your CRM is not in Claude's built-in connector list, there is a good chance it is available through Zapier. That is the whole reason the bridge is worth building.

Does this cost extra?

You will need an account on whichever automation platform you choose, and those have their own pricing tiers depending on how much you run through them. Check the current plans on the platform's site before you build a workflow you depend on.

Want more of this?

Subscribe to my weekly emails at milehightitleguy.com. I share real estate tools, marketing tactics, AI workflows, and invites to upcoming classes and events across Colorado. If you are in the Denver Metro area, come out to one of my classes. I would love to have you there.

Reach out any time if you have questions on this or want help thinking through what to automate first.

Jerad Larkin

The Mile High Title Guy

Chicago Title of Colorado

303.630.9430 | Info@MileHighTitleGuy.com

milehightitleguy.com

Comments


LOOKING FOR IDEAS TO GROW YOUR REAL ESTATE BUSINESS?

Do you have any title, escrow, or real estate marketing questions?

Jerad Larkin, Chicago Title Logo

The information on this website is for general informational and educational purposes only. All content reflects my personal opinions and industry experience, including insights related to real estate, marketing, and title insurance. Nothing on this site should be interpreted as legal, financial, or tax advice, nor does it replace guidance from qualified professionals. Real estate laws, title insurance regulations, and market conditions change frequently. Although every effort is made to ensure accuracy, Chicago Title and Jerad Larkin make no guarantees and assume no responsibility for errors, omissions, or outcomes resulting from the use of this website or any linked resources. Users should independently verify all information before making decisions.

Copyright © All Rights Reserved by Mile High Title Guy.

  • Facebook
  • Instagram
  • LinkedIn
  • Pinterest
  • Youtube
bottom of page