Connect Housecall Pro to Claude Desktop
Claude Desktop reads a small JSON config that tells it which MCP servers to start. You paste one block, restart, and Claude can read your Housecall Pro account.
Setup
-
Generate a Housecall Pro API key
In Housecall Pro: My Apps, then Go to App store, then API Key Management. Choose Read-only unless you specifically want the MCP to be able to make changes. API access is a MAX-plan feature and you need an admin login.
-
Open the config file
In Claude Desktop: Settings → Developer → Edit Config. That opens claude_desktop_config.json in your editor.
-
Add the MCP
Paste this, replacing the key with your own. If the file already has an mcpServers block, add the housecall-pro entry inside it rather than adding a second block.
{ "mcpServers": { "housecall-pro": { "command": "npx", "args": ["-y", "housecall-pro-mcp"], "env": { "HCP_API_KEY": "your-api-key-here" } } } } -
Restart Claude Desktop
Fully quit and reopen it. A window reload is not enough. The MCP appears in the tools list once it has started.
Your first ask
Ask something you already know the answer to. If it agrees with you, everything is wired correctly. If it does not, you have found something worth knowing about your book.
Worth knowing
- Needs Node 18 or newer on the machine, because npx runs the server.
- Claude asks before running a tool the first time. That prompt is your confirmation layer, and it is reasonable to allow the read tools and keep asking on anything that writes.
If it does not work
The two commonest causes are the plan and the header. API access is a MAX-plan feature, so
on a lower plan there is no key to generate. And if you are hand-rolling requests rather
than using the MCP, the auth header is Token, not Bearer.
That one accounts for most "my key does not work" reports.
The API guide covers the rest.
Still stuck: hello@hcpapi.com, or read the source, which is open.