Connect Tekmetric to Claude Code

Make Claude answer shop questions and book appointments in Tekmetric. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Tekmetric to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Tekmetric, you add a Tekmetric MCP server: a small hosted service that exposes Tekmetric'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 Tekmetric account. No API keys pasted into config files.

claude mcp add --transport http tekmetric 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 Tekmetric once connected?

Tekmetric's partner API is read-deep and write-narrow, and the connector matches it honestly. Claude gets full reads across shops, customers, vehicles, repair orders, jobs, employees, and inventory, so it can answer nearly any question about the business, plus it can book and confirm appointments once you approve. Repair order edits stay in Tekmetric.

Pull open repair orders with jobs, totals, and status for any shop
Look up a customer's contact details and full vehicle service history
Book an appointment for a customer and vehicle after you approve
Confirm or cancel an existing appointment after you approve
Check parts inventory across your locations
Summarize repair order volume and totals across shops for any period

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 Tekmetric 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 Tekmetric API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Tekmetric 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 Tekmetric 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 Tekmetric 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 Tekmetric 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 Tekmetric'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 Tekmetric?

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 Tekmetric account it signs in with. Revoking access is one click in Tekmetric.

More on the Tekmetric connector

Tekmetric connector for claude.ai ServiceTitan + Claude Code Housecall Pro + Claude Code QuickBooks Online + 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