Connect Workiz to Claude Code

Make Claude create jobs and schedule visits in Workiz. From the terminal, inside the sessions where you already work.

How do you connect Workiz to Claude Code?

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

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

Full read-write Workiz access lets Claude create a job from a client request, schedule and assign it to a technician, update job details, and create or update a lead for your approval. Clients and invoices stay read-only. The intake and scheduling work that used to mean tabbing between screens happens where the job already lives.

Create a job from a client request with service type and address
Schedule a job and assign it to a technician on the dispatch board
Create or update a lead from an inbound request
Update job details and assign the right technician
Mark a lead as active or lost as it moves through intake
Find every open job matching a filter and propose next steps

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

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

More on the Workiz connector

Workiz connector for claude.ai MyCase + Claude Code PracticePanther + Claude Code Filevine + 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