Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
An open-source MCP server for the Housecall Pro API. Connect Claude, ChatGPT, Cursor, or any MCP-compatible AI agent to your Housecall Pro account, so you can ask for what you need instead of clicking through reports.
Independent project, not affiliated with, endorsed by, or sponsored by Housecall Pro. We run a service company on Housecall Pro ourselves, which is why it exists.
Needs Node 18 or newer and a Housecall Pro API key. API access comes with the MAX plan and is not available on lower tiers.
Claude Desktop. Open Settings, then Developer, then Edit Config, and add:
Restart Claude Desktop and the Housecall Pro tools will appear.
Claude Code. Add it directly:
Or install it as a plugin, which prompts for the key (stored in your keychain, never in a config file) and exposes the read-only and toolset switches as install-time options:
Cursor, Codex, and other MCP clients. Any client that speaks MCP over stdio
works. Use npx as the command, ["-y", "housecall-pro-mcp"] as the arguments,
and put HCP_API_KEY in the environment.
Getting a key takes about a minute and is described under Getting your Housecall Pro API key.
These are the edges of the Housecall Pro API itself. Each one is a place an integration built from the documentation alone gets a wrong answer rather than an error.
| What the API does | What this server does about it |
|---|---|
Money is integer cents, so $250 is 25000. | Converts in both directions. $250 stays $250 and never arrives as $2.50. |
PATCH /jobs answers 200 and changes nothing when sent a flat schedule key, a description, or tags. | Sends only the nested schedule object the API honours, so a reported success is a real one. |
| A job's description is derived from its line items and cannot be set directly. | Exposes line-item writes rather than a description field that would silently do nothing. |
Invoices filter on created_at, due_at, paid_at and amount_due, but not on service_date or invoice_date. An unsupported filter name is accepted and ignored rather than refused. | Uses the names the endpoint actually takes, and walks a service-date window client-side because no server-side equivalent exists. |
work_status reads back in a different vocabulary than it is written, for example complete unrated rather than completed. | Normalises on read, so a status filter matches real records instead of nothing. |
| Deleted jobs still appear in list responses and count toward totals. | Surfaces deleted_at on every row and warns, so revenue is not overstated. |
| Removing a tag from a job answers with an empty success whether or not the tag was there. | Reports the request as accepted rather than claiming a removal it cannot confirm. |
| An archived job refuses to describe its appointments. | Flags the job as archived and returns an empty list, so a sweep never stops part way. |
| The invoice document is a very long HTML page, not a PDF. | Returns the opening of the page and says how much of it that was. |
Attachments have no route of their own โ GET on a job's attachments path serves an HTML 404 โ but expand[]=attachments returns them with a signed download link. | Asks with expand and hands back the files. The link is minted per request, so it is fetched when given and never stored. |
Some routes answer only on PUT, and a POST to the same path returns an HTML 404 page, which reads as "no such route" rather than as the wrong method. | Uses the method each route actually takes, so dispatching a crew and bulk line-item updates work instead of looking absent. |
Never trust a 2xx on a Housecall Pro write. Read the record back. Several routes answer 200 without changing anything, which is why the rows above exist.
Housecall Pro's published documentation describes these. They are not there. An integration built from the docs alone ships broken code paths for each one.
| Documented | Reality |
|---|---|
POST, PUT, DELETE /appointments | Absent. Appointments exist only nested under a job. |
PUT /jobs/{id} | Absent. PATCH /jobs honours only the nested schedule object. |
POST /invoices | Absent. |
DELETE /customers/{id} | Absent. There is no public customer delete. |
PUT or DELETE /customers/{id}/addresses/{adr} | Absent. Addresses are append-only. |
PUT or DELETE /estimates/{id} and /estimates/{id}/options/{opt} | Absent. |
PUT or DELETE /leads/{id} | Absent as writes: a lead cannot be updated or deleted. Reading works โ GET /leads, GET /leads/{id} and GET /leads/{id}/line_items are all live. |
DELETE /tags/{id} | Absent. A tag can never be deleted through the API. |
DELETE /jobs/{id}/tags | Absent. |
PUT /jobs/{id}/lock | The verb is absent, not the route: POST /jobs/{id}/lock locks one job. The bulk POST /jobs/lock also exists and keys on starting_at rather than a list of job ids. |
POST /api/price_book/services | Absent. Materials and categories create normally. |
GET /webhooks/subscription | Absent. |
/api/price_book/ are not covered by that gate, and a read-only key can
create and delete price-book categories there. If you want a guarantee
rather than nearly one, run this server with --read-only, which does not
register a write tool at all.The walkthrough with screenshots is at https://hcpapi.com/mcp/#key.
The access level you pick is the real boundary. This server follows whatever you generated, so a read-only key cannot reach the write tools at all. If you want an assistant that only answers questions, generate a read-only key and Housecall Pro enforces that limit for you.
Only an admin can generate a key, and admins have full account access, so the key reaches the whole account rather than one person's slice of it.
95 tools. Reading works with any key; writing needs a full-access one. They are grouped into toolsets, so an install can register only the groups it needs - see Choosing which tools to register.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/housecall-pro-mcp)<a href="https://allmcps.com/mcp/housecall-pro-mcp"><img src="https://allmcps.com/api/badge/housecall-pro-mcp?style=directory" alt="Housecall Pro MCP on AllMCPs" /></a>