New — works with Claude and any MCP assistant

Set up your scheduling by describing it

Connect Cartoply to your AI assistant and skip the clicking. Tell it your hours, your team, and who covers what — it builds the event types, invites the techs, draws the territories, and hands you a link for the few things only you can approve.

One prompt, whole setup

This is a real instruction, not a demo script

"Set up Cartoply for my 4-person HVAC company: 60-minute service calls,
8am–6pm weekdays. Here's a CSV of my techs with their home addresses —
give each one a territory covering a 45-minute drive from home, invite
them all, and send me links for anything that needs me."

The assistant sets the schedule, creates the event type, invites every tech, geocodes each address, traces a 45-minute drive-time polygon along the real road network for each one, and assigns it. What comes back to you: a checkout link and two calendar consent screens. That's the whole setup.

And it keeps running things after setup

Bookings

Cancel, reschedule, approve requests, reassign a sick tech’s day to whoever is free, mark no-shows.

Territories

Redraw coverage when a tech moves, import your Google My Maps zones, or ask for drive-time areas by address.

Team

Invite new hires, organize crews into groups, set who is eligible for which appointment types.

Reporting

“How did bookings do last month, by rep?” — answered from your real data, in the conversation.

You stay in control

Money and deletions stay human

You approve the connection once, on a consent screen that spells out exactly what the assistant may touch. By default it cannot issue refunds, remove team members, delete your organization, change your subscription, or enter payment details — when one of those comes up, it hands you a link and waits. Refunds and member removal can be granted separately, with a clearly-marked high-risk permission, if you want a trusted assistant handling them; deleting the organization and billing changes are never grantable. Every action lands in an audit trail.

Access can be read-only if that's all you want, and every agent action goes through the same permission checks as the dashboard — an assistant can never do something you couldn't.

Three ways to connect

Claude app

Settings → Connectors → Add custom connector, with the Cartoply server URL. Two minutes.

Claude Code

One command in the terminal, authenticate in the browser, done.

No account yet

Your agent starts the signup itself; you click one emailed link to create the account and approve it.

Frequently asked questions

Which AI assistants work with Cartoply?

Any assistant that supports MCP (Model Context Protocol) with OAuth — including Claude on web and desktop (as a custom connector) and Claude Code. The assistant registers itself automatically; you approve access on a consent screen.

Can an AI assistant create my Cartoply account?

Yes. An agent can start the signup with your email address; you get a single-use claim link that creates the account, records your acceptance of the terms, and approves the agent — one click, and the agent continues setting up.

What can the assistant NOT do?

Issue or deny refunds, remove team members, delete your organization, change your subscription or seats, or enter payment details. Those stay in the web app, done by you. Payment and calendar connections are links the assistant hands you.

What is a drive-time territory?

Tell the assistant "give this tech everything within 45 minutes of their home address" and it creates a polygon traced along the real road network — not a crow-flies circle — then assigns it. Works for 5 to 120 minutes of drive time.