How I Connected a Contractor's CRM to Claude via MCP — and What It Means for Your Business

Ali Gauhar · CRM · June 28, 2026 · 6 min read

Your CRM has thousands of records, but getting answers means clicking through filters, running reports, or asking your office manager to pull numbers. What if you could ask Claude "how many HVAC leads did we get last week from Google?" and get an answer in seconds — then say "create a follow-up task for the ones nobody called."

CRM data → MCP server → Claude → natural language query → action in CRM

MCP + Claude is the bridge to your CRM

MCP (Model Context Protocol) is the bridge between your CRM and Claude. I built a server that exposes your Jobber, ServiceTitan, or HubSpot data as tools Claude can read and write to — safely, with permissions. Your team asks Claude in plain English: "Show me all open estimates over $5K" or "Which reps have not followed up on leads from this week?" Claude queries your CRM and returns the answer. No report builder. No training. It goes further than read-only. Claude can create tasks, update statuses, and log notes — with guardrails so it cannot delete records or change pricing. This is what I built for a contractor client, and it is the direction every CRM is heading.