Claude + ServiceTitan Integration: What Works in 2026
No — there’s no official Claude ServiceTitan connector and no ServiceTitan-built MCP server. ServiceTitan isn’t in Anthropic’s connectors directory, and developer.servicetitan.io documents an API v2 but no MCP. What exists on the Claude side are third-party community MCP servers (the most-cited has about 4 GitHub stars) and middleware like Zapier MCP. Claude can use a connection when you ask and can run fixed scheduled tasks, but ServiceTitan events do not trigger those tasks. A job booking, estimate change, or dispatch update does not start Claude on its own.
Here’s what’s actually available, how to connect it, where the limits bite, and how Carly provides a simpler interface for the ServiceTitan work you delegate.
What ServiceTitan ships — and what it doesn’t
ServiceTitan has a broad, capable API, but it’s a developer platform, not a Claude hookup:
- API v2 at developer.servicetitan.io, with a wide surface: jobs, customers, dispatch, invoices, estimates, pricebook, payroll, marketing, and reporting.
- OAuth 2.0 client-credentials auth — you need an App Key, Client ID, Client Secret, and Tenant ID; access tokens expire roughly every 15 minutes.
- Two app types. A Private App (your own single tenant) needs no ServiceTitan review — a contractor can self-serve and integrate their own account. A Public App (multi-customer) requires ServiceTitan approval on a weekly review cadence; allow a few business days. It’s a one-time approval, and adding tenant IDs or scopes later doesn’t require re-approval.
What you won’t find is anything Claude-native. ServiceTitan’s AI story is its own brand, Titan Intelligence, and its plain-English “sidekick” Atlas, unveiled at Pantheon 2025 to run reports, find jobs, and dispatch techs from the ServiceTitan mobile app. Impressive — but it’s an in-product feature, not an MCP server, and it doesn’t connect to Claude. This is the classic “vendor AI is not connectable AI” case.
How you’d actually connect Claude to ServiceTitan today
No first-party path exists, so the options are unofficial:
- A community MCP server — the most-cited (around 4 stars, ~60 tools across CRM, jobs, accounting, estimates, dispatch, pricebook, inventory, memberships, payroll, and reporting) runs against API v2 using your App Key, Client ID, Client Secret, and Tenant ID.
- Middleware MCP — Zapier MCP exposes ServiceTitan actions to Claude without your maintaining code.
- Your own app — register a Private App in the developer portal (no review needed for your own tenant) and point a local MCP server at API v2.
Any of these adds ServiceTitan as a custom MCP connector. Remote custom connectors on claude.ai require a paid Claude plan; local servers run through Claude Desktop or Claude Code. Vet any community server before handing over credentials — the field is small and repos come and go.
The limits that actually matter
However you connect it, three limits define the setup:
- No ServiceTitan event triggers. There’s no “when a job is booked, text the customer a confirmation and assign a tech.” Claude can respond in a conversation or run on a schedule, but the trigger is you or the clock—not the ServiceTitan event.
- The integration is yours to maintain. A community MCP server or private app needs ServiceTitan credentials, scopes, token refresh, hosting, and ongoing vetting. The API may be capable; the connection is still an implementation.
- Unattended writes need careful testing. A scheduled Claude task can read through connectors, but write behavior depends on the client, connector, approval requirements, and the MCP server’s tools. Do not assume a scheduled task can dispatch or update production jobs safely just because an interactive prompt worked.
So Claude is good for “summarize this week’s completed jobs by tech” and not built for “confirm every new booking the moment it comes in.”
ServiceTitan answers on demand and on a recurring schedule: Carly
The most credible Carly use case here is not “replace ServiceTitan’s dispatch automation.” It is giving field teams and managers a faster way to reach ServiceTitan without opening the desktop interface.
Carly connects to ServiceTitan so you can ask for a job, customer, equipment history, or technician schedule over email or text. A technician can send an address and get the past service history before walking in. A dispatcher can ask what’s on a technician’s board tomorrow. After a call, send Carly the job number and notes and have it update the record. Because Carly also works with email and calendar, you can request the ServiceTitan lookup and the related administrative step in the same exchange.
Carly workflows also cover recurring work. Set a morning workflow to pull today’s booked jobs and email dispatch a digest, send each technician a schedule brief, or summarize yesterday’s completed work for a manager. The workflow can query ServiceTitan, format the result, and deliver it through email or Slack on the cadence you choose, whether or not anyone opens a chat.
ServiceTitan’s own workflows and notifications are still responsible for ServiceTitan-native event triggers such as a newly booked job. Carly does not claim to passively monitor every job or estimate change. The accurate distinction is: Carly handles on-demand work and scheduled cross-app routines here; ServiceTitan handles its own native events.
Carly offers free, unlimited Zapier-style workflow steps; AI agents start at $35/month. See the ServiceTitan integration and the full integration catalog.
Claude vs Carly
| Claude (community/middleware MCP) | Carly | |
|---|---|---|
| Look up jobs & customers | Yes | Yes |
| Pull reports | Yes | Yes |
| ServiceTitan-native event triggers | No | Use ServiceTitan workflows |
| Looks up jobs from email or text | No | Yes |
| Recurring job and schedule digests | Read-only scheduled task | Yes, with delivery and downstream steps |
| Sends email as part of the flow | Microsoft 365 yes; Gmail draft-only | Yes (Gmail + Outlook) |
| Carly connector | — | Yes |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with a community MCP is a ServiceTitan query inside a chat. Carly is an email-and-text interface for ServiceTitan lookups, updates, and related administrative work.
Frequently Asked Questions
Does Claude work with ServiceTitan?
Not officially. There’s no Claude ServiceTitan connector in Anthropic’s directory and no ServiceTitan-built MCP server. You can connect them through a third-party community MCP server against API v2, or through middleware like Zapier MCP. Claude can use that connection in a conversation or a fixed scheduled task, but ServiceTitan events do not trigger it.
Isn’t Titan Intelligence or Atlas a Claude integration?
No. Titan Intelligence and Atlas are ServiceTitan’s own in-product AI. Atlas runs inside the ServiceTitan app to dispatch techs and run reports; it’s not an MCP server and it doesn’t connect to your Claude account.
How do I connect Claude to ServiceTitan?
Register a Private App in the developer portal — no ServiceTitan review needed for your own tenant — to get an App Key, Client ID, Client Secret, and Tenant ID, then run a community or self-built MCP server against API v2 and add it to Claude as a custom connector (paid plan for remote connectors). Middleware like Zapier MCP is an alternative.
What if I want ServiceTitan to act on its own — confirm bookings, send digests?
Use ServiceTitan’s own workflows for events such as a new booking. Carly complements them with on-demand instructions and recurring routines—for example, pulling today’s jobs every morning, emailing the dispatch digest, and sending the relevant schedule brief to each technician. It can also look up jobs, add notes, and handle related email or calendar work from an email or text instruction. AI agents start at $35/month.
More: Claude connectors · Claude + Jobber · Claude + Housecall Pro · Can Claude send emails · Claude vs Carly · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
