Run the Business · Connect to ClaudeBeta
Your business, in Claude's hands. With a safety catch.
WindowEdge ships an MCP server. Create a scoped key, paste it into Claude, and ask for your morning briefing. Claude reads the calls, the calendar and the projects, then asks before it writes.
Built by dealers. 30+ years in the trade.
Claude
WindowEdge connected · read + calendar write
Tuesday, Sep 8. Three appointments today, two quotes waiting on signatures, and one thing that needs you:
Yesterday at 4:12 PM a call from Dana Whitfield was logged as booked, but no appointment was ever created. Earliest open slot is Tue 10:30 AM, and Pat Sullivan has the best close rate this quarter.
Want me to book it?
Confirm before writing
Book Tue 10:30 with Pat Sullivan?
In-home estimate · Dana Whitfield · 1 hr 30 min
How it connects
Three steps, done by a dealer admin. No developer required.
Pick the scopes
A dealer admin opens Settings, then Integrations, then Developer. Choose what Claude may see: numbers, contacts, calendar, agent conversations, projects, tasks. Each one is read or read-write.
Create the key
WindowEdge shows the key once. Copy it, along with the server address on the same screen. If you lose it, revoke it and make another.
Paste it into Claude
Add WindowEdge as a connector in Claude with the server address and the key. Claude sees the tools your scopes allow and nothing else. Any MCP client works the same way.
31 tools, grouped the way the business runs
Claude only sees the tools your scopes allow.
Tenant and team
Your company profile and the people on the team, so Claude knows who Pat is and who closes best.
Metrics and daily brief
The numbers behind the dashboard and a ready-made morning briefing tool.
Contact 360 search
Find a customer by name and get everything attached to them.
Appointments and availability
Read the calendar, check open slots, and book with the right rep when you say so.
SMS, voice and web chat transcripts
What was said on every call, text thread and website chat.
Projects, leads and tasks
Where every job sits, which leads are open, and what is assigned to whom.
“Give me my morning briefing.”
One sentence, and Claude reads the day. In the demo it catches a call that was logged as booked even though no appointment was ever created, finds the earliest open slot, and offers to book it with the rep who closes best. The booking waits on a confirmation card.
- Reads the daily brief, the calendar and the call log
- Flags the gap: booked on the call, missing on the calendar
- Checks availability and picks the best closer from the team
- Asks: Book Tue 10:30 with Pat Sullivan? Confirm or cancel
The write loop
- 1
Prepare
Claude calls the prepare tool with the slot, the rep and the contact. Nothing changes yet.
- 2
Show
You see exactly what would be created, in plain language, with a Confirm and a Cancel.
- 3
Confirm
Only your yes commits the appointment. The audit log records both calls.
What Claude can and cannot do
Can
- Read anything inside the scopes you granted
- Summarize calls, texts and chats by customer or by day
- Build a morning briefing that spots what fell through the cracks
- Check availability and propose an appointment with a specific rep
- Draft a text or a task, and send or assign it once you confirm
- Answer questions across contacts, projects, leads and metrics
Cannot
- Write anything without asking you first
- See a scope you did not grant, or keep working after a key is revoked
- Act on another dealer's data, ever
- Bypass the audit log: every call is recorded with the key that made it
- Change billing, users, permissions or integrations
- Delete records
The safety catch
Prepare, then confirm
Every write is a two-step loop. Claude prepares the change, shows it to you, and only commits it after you say yes. Reads never need confirmation.
Revocable keys
A key is scoped when it is created and can be revoked any time from the same Developer screen. Revocation takes effect on the next call.
Every call audited
Each tool call is logged with the key, the scope it used, and what it read or wrote, so an admin can see exactly what Claude did and when.
Any MCP client
MCP is an open protocol. Claude is the client we demo, but the same key and server address work in any client that speaks MCP.
Questions dealers ask about MCP
What is MCP?
MCP, the Model Context Protocol, is an open standard that lets an AI assistant such as Claude call tools on an outside system. WindowEdge ships an MCP server, so Claude can read your calls, calendar, contacts, projects and tasks, and take an action when you confirm it.
Who can create a key?
A dealer admin, from Settings, then Integrations, then Developer. The admin picks the scopes, chooses read or read-write for each, and creates the key. The key is shown once.
Can Claude change my data on its own?
No. Every write goes through a prepare-then-confirm loop. Claude proposes the change, for example booking a slot with a named rep, and commits it only after you confirm in the conversation.
What can Claude see?
Only the scopes on the key. If you granted calendar and contacts as read-only, Claude can read those two and nothing else, and it cannot book. The 31 tools cover tenant profile, team, metrics, the daily brief, contact 360 search, appointments and availability, SMS, voice and web chat transcripts, projects, leads and tasks.
How do I turn it off?
Revoke the key from the Developer screen. Every call made with the key is in the audit log, so you can review what happened before you decide.
Does it only work with Claude?
No. It works with any MCP client. Claude is what we demonstrate and what most dealers ask for, but the server is standard MCP.
Is this the same as Ask Edgy?
They share the same records. Ask Edgy is the built-in chat inside the WindowEdge console and app. Connect to Claude brings that data into a client you already use, with the scopes and confirmation loop described here.
See Claude run a morning briefing
A 20-minute demo. We will create a key, connect Claude, and let you watch it catch the gap.
Built by dealers. 30+ years in the trade.