MCP, or Model Context Protocol, gives Claude a standardized way to interact with external tools and services. In Claude, these integrations are often presented as connectors. Available options can include Gmail, Google Drive, Slack, databases, deployment platforms, and many other tools.

In this example, the Gmail connector is used to support a personalized outreach workflow. After connecting Gmail and granting the required permissions, it may be necessary to start a new conversation so the connector becomes available to Claude Code.

Claude is asked to:

• Open a prospect’s existing website;
• Review the personalized mockup created earlier;
• Capture screenshots of both versions;
• Find the prospect’s contact details;
• Identify a specific improvement made in the mockup;
• Write a short, personalized outreach email;
• Save the completed message as a Gmail draft.

Claude reviews the prospect’s website and identifies a relevant outreach angle. For example, it might notice that the current site does not provide an easy way for patients to request an appointment, while the redesigned mockup includes a booking button and contact form.

Using this information, Claude creates a message that refers to the prospect’s real website and explains the specific improvement demonstrated in the mockup. The email is saved as a draft so it can be reviewed and sent manually from Gmail.

Not every step in a connected workflow will work perfectly immediately. For example, handling image attachments may require additional formatting or refinement. Testing the process helps reveal which parts can be automated reliably and which still benefit from manual review.

MCP connectors allow Claude Code to work with the tools already used in a business. By combining project context, prospect data, browser research, and Gmail, Claude can produce more relevant outreach while keeping the final sending decision under human control.