Connect ServiceTitan to Claude Code

Have Claude create jobs and update customer records in ServiceTitan. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect ServiceTitan to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ServiceTitan, you add a ServiceTitan MCP server: a small hosted service that exposes ServiceTitan's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ServiceTitan account. No API keys pasted into config files.

claude mcp add --transport http servicetitan https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ServiceTitan once connected?

Full read-write ServiceTitan access lets Claude create and reschedule jobs, draft estimates, update customer and location records, and add notes to a job, all inside the system of record. The dispatch and follow-up work that used to mean clicking through screens happens where the data already lives, after you approve it.

Create a new job and assign it to a customer and location
Reschedule or reassign an existing job on the dispatch board
Draft an estimate from a template and attach it to a job
Update a customer or location record with corrected contact details
Add a note or tag to a job so the field team has full context

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ServiceTitan access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ServiceTitan API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ServiceTitan changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ServiceTitan connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ServiceTitan connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ServiceTitan account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ServiceTitan's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to ServiceTitan?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ServiceTitan account it signs in with. Revoking access is one click in ServiceTitan.

More on the ServiceTitan connector

ServiceTitan connector for claude.ai Custom CRM + Claude Code QuickBooks Online + Claude Code Calendly + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us