housecall-pro-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@housecall-pro-mcp List my upcoming jobs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
housecall-pro-mcp
A local MCP (Model Context Protocol) server that wraps the Housecall Pro Public API (v1) so Claude Desktop or Claude Code can read and write your Housecall Pro data directly.
Built for personal/local use — it talks to Housecall Pro with a single API key, runs over stdio, and is meant to be added to your own Claude Desktop / Claude Code config.
Before you start
Housecall Pro's own docs and third-party sources disagree on whether full API access requires their MAX plan or is available on lower Pro tiers — that's account-specific. Check your own account: Housecall Pro → Settings → API / App Store card. If you don't see an option to generate an API key there, you may need to request API access from Housecall Pro support first.
Related MCP server: ops-platform-mcp
Setup
npm install
cp .env.example .env
# edit .env and paste your real HCP_API_KEY
npm run buildAdd to Claude Desktop
Edit your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS) and add:
{
"mcpServers": {
"housecall-pro": {
"command": "node",
"args": ["/absolute/path/to/housecall-pro-mcp/dist/src/index.js"],
"env": {
"HCP_API_KEY": "your_housecall_pro_api_key_here"
}
}
}
}Restart Claude Desktop after saving.
Add to Claude Code
claude mcp add housecall-pro --env HCP_API_KEY=your_housecall_pro_api_key_here -- node /absolute/path/to/housecall-pro-mcp/dist/src/index.jsTools
All 23 documented Housecall Pro v1 endpoints are wrapped. Each tool's description links to the exact Housecall Pro docs page for that endpoint — worth checking before using create_*/update_* tools, since their body argument is passed straight through rather than hard-coded (see "A note on accuracy" below).
Area | Tools |
Company |
|
Customers |
|
Jobs |
|
Estimates |
|
Invoices |
|
Employees |
|
Leads |
|
All list_* tools accept page, page_size, sort_by, sort_direction, plus an extra_query object for any endpoint-specific filters (e.g. customer_id, work_status) not modeled explicitly.
Bulk export (for the ServiceTitan migration)
For pulling everything out of Housecall Pro in one shot rather than one call at a time through chat, there's a standalone script:
npm run export-allThis pages through customers, jobs, estimates, invoices, employees, and leads, and writes:
export/<resource>.json— full raw recordsexport/<resource>.csv— flattened, spreadsheet-friendly version
It's a plain script (not an MCP tool) on purpose — paginating through potentially thousands of records and returning them through a single chat tool call would blow past reasonable response sizes. Run it directly, then hand the CSVs/JSON to whatever process you're using to load data into ServiceTitan.
Heads up: the script guesses the response shape of each list endpoint (e.g. assumes GET /customers returns { customers: [...] }). If Housecall Pro's actual shape differs, it won't silently produce a broken export — it stops for that resource and writes the raw first-page response to export/_debug_<resource>_page1.json so you can see the real shape. Check your terminal output after running it.
A note on accuracy
This was built from Housecall Pro's public docs and a third-party consolidated API reference, not by testing against a live account (I don't have your API key). Everything here should work as documented, but:
The exact JSON field names Housecall Pro expects in
create_job,create_customer,create_estimate,create_lead,update_customer,update_job_schedule, andbulk_update_estimate_option_line_itemsrequest bodies were not hard-coded into schemas here, specifically so nothing gets guessed/fabricated. Each of those tools takes a rawbodyobject and links to the exact docs page — check the docs (or make one test call and read the error message) before relying on it.List-endpoint filter params beyond pagination/sorting (e.g.
customer_idon jobs) aren't hard-coded either — useextra_queryand confirm the param name against the linked docs.First real call against your account is the actual test. If something 404s or the auth header format is wrong, the error message will include Housecall Pro's own response body, which should point at the fix.
Project layout
src/
housecallClient.ts Thin fetch wrapper (auth header, pagination, error handling)
index.ts MCP server + all 23 tool registrations
scripts/
export-all.ts Bulk JSON/CSV export script (see above)Available Tools
23 toolsbulk_update_estimate_option_line_itemsBulk Update Estimate Option Line ItemsA
Bulk-update the line items on one option of an estimate. Provide body matching Housecall Pro's bulk_update fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/b3e4391f7853f
Inputs: body (required), option_id (required), estimate_id (required).
convert_leadConvert Lead to Estimate or JobA
Convert an existing lead into an estimate or a job. Provide body matching Housecall Pro's convert fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/d9c8a89ed4e4c-convert-lead-to-estimate-or-job
Inputs: body (required), lead_id (required).
create_customerCreate CustomerA
Create a new customer. Provide body matching Housecall Pro's create-customer fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/4e0bf8c4d65d7-create-customer
Inputs: body (required).
create_estimateCreate EstimateA
Create a new estimate. Provide body matching Housecall Pro's create-estimate fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/4004d373be14c
Inputs: body (required).
create_jobCreate JobA
Create a new job. Provide body matching Housecall Pro's create-job fields (customer_id, addresses, schedule, line_items, etc). Docs: https://docs.housecallpro.com/docs/housecall-public-api/2dcf481ed7d69-create-a-job
Inputs: body (required).
create_leadCreate LeadB
Create a new lead. Provide body matching Housecall Pro's create-lead fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/8961eaf9f1c28-create-lead
Inputs: body (required).
get_companyGet CompanyA
Get the authenticated Housecall Pro account's company profile. Docs: https://docs.housecallpro.com/docs/housecall-public-api/24a5d891a80a8-get-company
Inputs: no named parameters.
get_customerGet CustomerA
Get a single customer by ID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/7599b1ec89338-get-customer
Inputs: customer_id (required).
get_estimateGet EstimateB
Get a single estimate by ID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/eae5e9c092ef2
Inputs: estimate_id (required).
get_invoiceGet InvoiceA
Get a single invoice by its UUID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/0ae16219c3e58
Inputs: invoice_uuid (required).
get_jobGet JobC
Get a single job by ID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/bbabd67bed1ab-get-a-job
Inputs: job_id (required).
get_leadGet LeadA
Get a single lead by ID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/fc11c266161fe-get-lead
Inputs: lead_id (required).
get_schedule_windowsGet Schedule Availability WindowsA
Get company schedule availability windows. Use extra_query for any date-range/employee filters. Docs: https://docs.housecallpro.com/docs/housecall-public-api/898190c92fb8b-schedule-windows
Inputs: extra_query.
list_customersList CustomersB
List/search customers, paginated. Docs: https://docs.housecallpro.com/docs/housecall-public-api/042bd3bf861ae-get-customers
Inputs: page, sort_by, page_size, extra_query, +1 more.
list_employeesList EmployeesA
List employees/techs, paginated. Docs: https://docs.housecallpro.com/docs/housecall-public-api/303ee235f23fa-get-employees
Inputs: page, sort_by, page_size, extra_query, +1 more.
list_estimatesList EstimatesB
List/search estimates, paginated. Docs: https://docs.housecallpro.com/docs/housecall-public-api/e430ba3d520a0
Inputs: page, sort_by, page_size, extra_query, +1 more.
list_invoicesList InvoicesB
List/search invoices, paginated. Docs: https://docs.housecallpro.com/docs/housecall-public-api/65ce9f430d605
Inputs: page, sort_by, page_size, extra_query, +1 more.
list_job_invoicesList Job InvoicesA
List invoices for a specific job. Docs: https://docs.housecallpro.com/docs/housecall-public-api/eb1f5b5f17290
Inputs: job_id (required).
list_jobsList JobsA
List/search jobs, paginated. Use extra_query for filters such as customer_id, employee_ids, work_status, scheduled_start_min/max. Docs: https://docs.housecallpro.com/docs/housecall-public-api/6c97704da8bf3-get-jobs
Inputs: page, sort_by, page_size, extra_query, +1 more.
list_leadsList LeadsA
List/search leads, paginated. Docs: https://docs.housecallpro.com/docs/housecall-public-api/278974bc87e32-get-leads
Inputs: page, sort_by, page_size, extra_query, +1 more.
preview_invoicePreview InvoiceB
Get a customer-facing preview of an invoice by UUID. Docs: https://docs.housecallpro.com/docs/housecall-public-api/ae40a9286ba7c
Inputs: invoice_uuid (required).
update_customerUpdate CustomerA
Update an existing customer. Provide body matching Housecall Pro's update-customer fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/b1c3acd657849-update-customer
Inputs: body (required), customer_id (required).
update_job_scheduleUpdate Job ScheduleB
Update a job's scheduled window / assigned employees. Provide body matching Housecall Pro's schedule fields. Docs: https://docs.housecallpro.com/docs/housecall-public-api/1d344f58672f9-update-job-schedule
Inputs: body (required), job_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Each tool targets a distinct resource and action combination (e.g., list_customers vs. get_customer, list_invoices vs. list_job_invoices). The descriptions clearly differentiate similar-sounding tools, so an agent can reliably select the correct one.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_customers, create_estimate, convert_lead, preview_invoice). Even the longer names like bulk_update_estimate_option_line_items adhere to this pattern, making the naming predictable and uniform.
With 23 tools, the server falls into the 'borderline heavy' range (16-25). While the tools cover a wide range of Housecall Pro features, the count is higher than the typical well-scoped server, and some tools (e.g., get_company, list_employees) are single-purpose, contributing to the total.
The tool set provides robust read and create capabilities for customers, jobs, estimates, invoices, and leads, but notable gaps exist: there are no update operations for jobs (except schedule), estimates, or leads, and no delete operations at all. Invoices are read-only, which may be acceptable but limits full lifecycle management.
Maintenance
Related MCP Connectors
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Hosted CallRail MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for Housecall Pro, providing 5 tools for AI agents to register customers, schedule jobs, create estimates, log leads, and generate invoices (env-gated).5MIT
- FlicenseAqualityBmaintenanceMCP server wrapping a mock internal ops platform (FastAPI + SQLite) so Claude Code can read and write employee, project, task, and time data through natural language.8-
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides tools for managing GoHighLevel (GHL) conversations, tasks, and calendar appointments through AI assistants like Claude.2170 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.MIT