Connect Housecall Pro to Claude Code

Have Claude draft estimates and schedule jobs in Housecall Pro. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Housecall Pro to Claude Code?

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

claude mcp add --transport http housecall-pro 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 Housecall Pro once connected?

Full read-write Housecall Pro access lets Claude draft an estimate from a job description, schedule or reschedule an appointment, add a line item, update a customer's contact details, and look up an invoice and its payment status. The intake and admin work that used to mean clicking through screens happens where the job record already lives.

Create an estimate with line items from a job description, then hold it for your review
Schedule or reschedule a job and assign it to a technician
Add or update a customer record with contact and address details
Add line items or notes to an existing job before it is finalized
Look up an invoice and its payment status, and add line items to the job it is generated from
Find every open job matching a query 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 Housecall Pro 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 Housecall Pro API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Housecall Pro 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 Housecall Pro 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 Housecall Pro 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 Housecall Pro 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 Housecall Pro'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 Housecall Pro?

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

More on the Housecall Pro connector

Housecall Pro 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