housecallpro-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOUSECALLPRO_API_KEY | Yes | Your Housecall Pro API key. Get it from your account settings. | |
| HOUSECALLPRO_ALLOW_INVOICE | No | Set to 'true' to enable invoice creation. Default is false. | false |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_pro_customerA | Register a new customer in the Housecall Pro CRM. Used by AI receptionists to capture inbound caller details before scheduling a job. |
| schedule_new_jobB | Create and schedule a new trade job associated with an existing customer. Used by AI dispatchers to book service windows on the calendar. |
| create_estimateA | Generate a pricing estimate or service proposal for a customer. Used by AI sales agents to quote work after diagnostic conversations. |
| submit_new_leadA | Log a new marketing or inbound prospect lead in the Housecall Pro sales funnel. Used by AI agents handling inbound chat or web form submissions. |
| generate_job_invoiceA | Post an official invoice against an active job. GATED behind HOUSECALLPRO_ALLOW_INVOICE env var. Returns an error if not enabled. This action creates a billable customer-facing invoice. |
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 5 tools
Each tool targets a distinct business function (estimate, customer, invoice, job, lead) with no overlapping purposes, ensuring clear differentiation for an agent.
All tools follow a consistent verb_noun pattern (create_, generate_, schedule_, submit_), making the surface predictable and easy to navigate.
With 5 tools, the server covers core CRM workflows without being bloated or sparse—appropriate for a focused home service management integration.
The tools cover essential actions (create, schedule, invoice, lead) but lack update/delete operations or search, leaving minor gaps for advanced workflows.