Housecall Pro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOUSECALLPRO_LINK | No | The Housecall Pro estimate or invoice link provided by the contractor. Example: https://pro.housecallpro.com/mobile_estimate/XXXXXXXXXX | |
| HOUSECALLPRO_LINKS | No | JSON array of objects, each with a label and url, for multiple documents. Example: [{"label":"tankless","url":"..."},{"label":"hvac","url":"..."}] |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| housecallpro_get_estimateA | Read an estimate a Housecall Pro contractor sent you: line items, totals, tax, the company behind it, and whether it is still awaiting your approval. The default |
| housecallpro_get_invoiceA | Read an invoice a Housecall Pro contractor sent you: amount, subtotal, tax, what is still owed, and whether it can be paid online. The default |
| housecallpro_list_linksA | List the Housecall Pro customer links this server is configured with. Labels and document kinds only — retrieval tokens are credentials and are never returned. |
| housecallpro_get_companyA | Look up the contractor behind an estimate: phone, email, website, address and default arrival window. Takes the |
| housecallpro_decline_estimateA | Decline one or more options on an estimate. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call posts nothing and returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Declining tells the contractor you are not proceeding; it cannot be undone from here. |
| housecallpro_approve_estimateA | Approving an estimate is NOT automatable and this tool always refuses. Housecall Pro gates approval behind a reCAPTCHA token only the real page can mint. Use this to get the explanation and the link to approve in a browser. |
| housecallpro_healthcheckA | Check that this server can reach Housecall Pro and that a configured customer link still resolves. Run this first when a tool fails. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: company lookup, estimate/invoice retrieval, estimate decline/approve, health check, and link listing. The only minor overlap is get_estimate including company info, but that's complementary rather than confusing.
All tools follow the consistent pattern housecallpro_ + verb_noun (e.g., get_estimate, decline_estimate, list_links). Verbs are lowercase and snake_case throughout, making the naming predictable and scannable.
With 7 tools, the server is well-scoped for its purpose—reading and acting on estimates/invoices plus administrative utilities. Each tool earns its place, and the count sits comfortably in the ideal 3-15 range.
The core lifecycle is covered: retrieve documents, decline an estimate, and access company details. The main gap is the lack of a tool to list all estimates/invoices (only get by ID), and payment is not addressed, but these are minor given the server's customer-facing scope.