Module 6 · Project and quiz
Two Systems, One Workflow
Connect at least two real systems your business uses and run one task that crosses them. The classic version: read leads from your CRM and create personalised follow-up drafts in your email, with nothing sent automatically.
1Pick the two systems that cost you the most copy and paste time (usually CRM plus email).
2Score each connector with the Connector Risk Assessment Checklist and file the results in your project.
3Connect both at local scope and confirm they show as healthy in /mcp.
4Add a deny rule for any tool that sends email or deletes records.
5Run a read-only pass: list leads with no reply in 7 days, with their last interaction.
6Ask Claude to create a follow-up draft for each lead in your email, in your voice, and to list them.
7Review, edit and send the drafts yourself, and note how long the whole task took versus doing it by hand.
Deliverable
Two connected systems, a filled risk checklist for each, and a working CRM to email drafting workflow with a time comparison.
Done when
- Two connectors show as connected in /mcp.
- Each connector has a completed risk checklist saved in the project.
- Send and delete tools are blocked by a permission rule.
- At least five follow-up drafts were created from CRM data and reviewed by you.
- You recorded minutes spent before and after.
In plain English, what is an MCP server?
MCP servers expose a defined set of tools, like buttons on a panel, that Claude can use within the permissions you allow.
Which scope should you use first when testing a connector that touches client data?
Local keeps the connection to you and the current project until it has passed your risk check.
What is the recommended order of trust for email automation in this module?
You build trust in stages and keep the irreversible action, sending, under human control.
Why is prompt injection a concern with connectors?
The official documentation warns that servers fetching external content can expose you to prompt injection, so trust and permissions matter.
Where should an API key for a shared project connector live?
.mcp.json supports environment variable references like ${API_KEY}, which keeps secrets on each person's machine and out of shared files.
