Connect Claude to your CRMBeta
An MCP Server for Home Improvement CRM, So Claude Can Run Your Morning
Ask Claude what happened overnight, which leads are unworked, and who called without booking. Let it fix the gap, but only after it shows you the plan and you say yes. Scoped keys, 31 tools, and an open protocol.
Built by dealers. 30+ years in the trade. The MCP server is in beta.
The short answer
MCP, the Model Context Protocol, is an open standard that lets an AI assistant like Claude use tools from another piece of software. An MCP server for a home improvement CRM turns the CRM into a set of those tools, so a dealer owner can ask questions in plain language and get answers pulled from real leads, appointments, messages and projects. The WindowEdge MCP server, now in beta, exposes 31 tools with keys scoped to each area and a confirm step before anything is written. It works with Claude and any other MCP client.
MCP in Plain Words, for a Dealer Owner
Think of Claude as a sharp new office manager on their first day. They can reason, write, and talk, but they cannot see your CRM. MCP is the badge and the keyring you hand them. The badge says which rooms they can enter. The keyring is the set of things they can actually do in each room: look up a contact, check the calendar, read a transcript, book a slot.
The protocol is open, so the same badge works for Claude today and other assistants tomorrow. And like any new hire, Claude does not get to text a customer or move an appointment without checking with you first. That is the prepare-then-confirm loop, and it is on for every write.
What the 31 tools cover
Profile and team
Who you are, who is on the team, and who owns what.
Metrics and daily brief
Lead flow, booking, and the numbers you would otherwise open a dashboard for.
Contact 360 search
Find a homeowner and see every call, text, chat, quote and project on one record.
Availability and booking
Check open slots and book an appointment on the real calendar.
SMS
Read and send texts through the same lines your team and agents use.
Voice and web chat transcripts
Pull up what was said on a call or in a chat.
Projects
Where each sold job sits on the rail and what is blocking it.
Leads and tasks
What came in, what is unworked, and what is due.
A Morning Briefing, Start to Finish
An example of the loop. Claude reads, finds a gap, proposes the fix, and waits.
You
Give me the morning brief.
Claude
Overnight: 4 new leads, 2 booked by the appointment setter, 1 web chat still open. One thing stands out. Maria Delgado called at 6:42 pm, spoke with the voice agent for four minutes about replacing six windows, and there is no appointment on her record. The transcript ends with her asking to be called back.
You
Book her the first open slot with Dan this week.
Claude
Prepared: in-home estimate for Maria Delgado with Dan, Thursday at 10:00 am, at 1418 Alder Court. Drive time from his 8:00 am stop checks out. I will send her a confirmation text from your main line. Confirm?
You
Yes.
Claude
Booked. Confirmation sent. Her record and the project board are updated.
Illustrative conversation. Names and details are made up.
What to Look For Before You Connect an AI to Your CRM
The data in your CRM is your customer list and your pipeline. Treat access to it the way you would treat a new hire's permissions.
Scoped keys, not one master password
You should be able to give Claude read access to metrics without giving it the power to text a customer. Keys should be scoped to an area and to read or read-write, shown once, and revocable at any time.
Ask before writing
An assistant that books an appointment or sends a text on its own guess is a liability. Every write should follow a prepare-then-confirm loop: Claude shows you what it is about to do, and nothing happens until you say yes.
Coverage of the whole job
A CRM connector that only reads contacts is a demo. Useful tools cover leads, booking, messaging, transcripts, projects, tasks and metrics, because the questions you ask cut across all of them.
An open standard
MCP is an open protocol. A server built on it works with Claude today and with any other MCP client you adopt later, so you are not locked to one assistant.
How WindowEdge Does It
You create a key in WindowEdge and pick the areas it can reach: metrics, contacts, booking, SMS, transcripts, projects, leads, tasks. You pick read or read-write for each. The key is shown once, so copy it into Claude when you make it, and you can revoke it from the same screen whenever you like.
From there Claude can call any of the 31 tools the key allows. Reads happen immediately. Writes go through prepare-then-confirm: Claude assembles the exact action, shows it to you, and executes only on your yes. The server is in beta, and tool coverage will grow.
Who This Is For
Owners who already use Claude
You write with it, plan with it, and want it to know your business. This is how it learns what happened yesterday without a copy and paste.
Sales managers running the morning
One question replaces three dashboards and a scroll through the inbox. The booked-call-with-no-appointment catch is the whole point.
Dealers who want AI on a leash
Scoped keys and a confirm step mean you can hand out read access freely and keep write access rare.
CRM Connector Capability Checklist
Questions to ask any vendor that offers to connect an AI assistant to your CRM.
| Capability | Typical CRM chatbot | WindowEdge MCP (beta) |
|---|---|---|
| Open protocol (MCP), works with Claude and any MCP client | Proprietary chatbot | Yes |
| 31 tools across profile, team, metrics, contacts, booking, SMS, transcripts, projects, leads and tasks | Contacts only | Yes |
| Keys scoped per area, read or read-write | One master key | Yes |
| Keys shown once and revocable | Stored in plain view | Yes |
| Prepare-then-confirm loop before any write | Acts immediately | Yes |
| Book a real calendar slot from the conversation | Not supported | Yes |
| Read call and chat transcripts | Not supported | Yes |
| Daily brief in one question | Open a dashboard | Yes |
Questions dealers ask about MCP
What is an MCP server for a home improvement CRM?
MCP stands for Model Context Protocol, an open standard that lets an AI assistant such as Claude use tools from another system. An MCP server for a home improvement CRM exposes the CRM as a set of tools, so you can ask Claude about leads, appointments, projects and messages in plain language and, with your confirmation, let it act. The WindowEdge MCP server is in beta.
How do I connect Claude to my CRM with WindowEdge?
You create a scoped key in WindowEdge for the areas you want Claude to reach, choose read or read-write, and add the WindowEdge MCP server to Claude. The key is shown once and can be revoked at any time. From then on, Claude can call the tools that key allows.
Can Claude change data in my CRM without asking?
No. Every write goes through a prepare-then-confirm loop. Claude prepares the action, shows you exactly what it will do, and only proceeds when you confirm. Read-only keys cannot write at all.
What can Claude actually do once it is connected?
The server exposes 31 tools covering your profile and team, metrics and a daily brief, contact 360 search, availability and booking, SMS, voice and web chat transcripts, projects, leads and tasks. A typical morning question is "what happened overnight and what needs me today."
Does it only work with Claude?
It works with Claude and with any client that speaks MCP. The protocol is open, so the same server can serve other assistants and internal tools as they adopt it.
See the Features Behind the Connection
The MCP server sits on top of the same records the rest of WindowEdge runs on.
Join the MCP Beta
Bring Claude to the demo. We will create a scoped key, run the morning brief on live data, and show you the confirm step before it books anything.
Built by dealers. 30+ years in the trade.