Housecall Pro MCP
A Model Context Protocol server that connects Claude to the of — the estimate or invoice link a contractor (HVAC, plumbing, electrical, cleaning) emails or texts you.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @chrischall/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add chrischall-housecallpro-mcp -- npx -y @chrischall/housecallpro-mcp@1.3.0Execute em um terminal.
{ "mcpServers": { "chrischall-housecallpro-mcp": { "command": "npx", "args": [ "-y", "@chrischall/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
A Model Context Protocol server that connects Claude to the of — the estimate or invoice link a contractor (HVAC, plumbing, electrical, cleaning) emails or texts you.
Housecall Pro customer portal MCP server for Claude — developed and maintained by AI (Claude Code)
[!WARNING] AI-developed project. This codebase was built and is actively maintained by Claude Code. No human has audited the implementation. Review all code and tool permissions before use.
Housecall Pro has two surfaces, and they share nothing:
If you run a business on Housecall Pro, you want the public API instead. This server is for being someone's customer.
npx -y @chrischall/housecallpro-mcp
Configure it with the link your contractor sent you:
HOUSECALLPRO_LINK='https://pro.housecallpro.com/mobile_estimate/XXXXXXXXXX'
Estimate and invoice links both work, short or long form —
pro.housecallpro.com/mobile_estimate/… and /mobile_invoice/…, or
client.housecallpro.com/estimates/… and /invoices/…. For several documents:
HOUSECALLPRO_LINKS='[{"label":"tankless","url":"…"},{"label":"hvac","url":"…"}]'
Then every tool takes an optional link selector; with one configured you never
need it.
[!IMPORTANT] Your link is a bearer credential. Anyone holding it can read the document and, for an estimate, decline it. It is read from the environment, never logged, and never returned in a tool result —
housecallpro_list_linksreports labels only.
Declining asks you first. A client that can show a confirmation prompt (Claude
Code) shows one. On a client that cannot (claude.ai, Claude Desktop) the first
call declines nothing and returns a preview plus a confirmToken; only a repeat
call with that token acts, and only if the estimate still matches what was
previewed.
view)housecallpro_get_estimate and housecallpro_get_invoice take
view: 'compact' | 'raw', defaulting to compact — the fleet vocabulary
from @chrischall/mcp-utils.
There is deliberately no full rung. full means "every field this server
understands, nothing dropped", and the fields this server understands are
exactly the ones the summary names — so it would be compact under a second
name, and everything past it is the upstream document, which is raw. A schema
should never advertise a value that silently aliases another.
If the upstream shape drifts far enough that the projection loses its footing, the whole document is returned (with a warning on stderr) rather than an empty summary: an empty summary is indistinguishable from an estimate with nothing on it.
They use different token shapes — 129 characters for an estimate, 32 for an invoice — and different endpoints. The client checks the shape and refuses a token pointed at the wrong tool before spending a request, rather than passing along an unexplained 404.
An invoice carries no line items and no tax field: a paid invoice renders
as a summary in the portal and the API returns exactly that, so tax_usd is
derived as total - subtotal. is_paid comes from the balance, not the status
string.
The upstream API returns integer cents — the estimate the portal renders as
$346.39 arrives as total_amount: 34639. Reporting that raw overstates every
figure 100×, so each money field is emitted as both *_cents (verbatim) and
*_usd (derived). tax.rate is a fraction (0.0825 = 8.25%) and is never
scaled.
That pairing is what the projection is for, so it exists on compact only.
view: 'raw' is the upstream document, and its money is integer cents with no
dollar sibling — total_amount: 34639 is $346.39. The view parameter's own
description says so at the call site.
housecallpro_approve_estimate always refuses, and that is deliberate.
Approval posts a response_token — a reCAPTCHA v3 token minted in-page for
the action estimates_customer_approvals. No server-side client can produce
one, and neither can a browser-bridge transport: the bridge issues fetch
calls, it does not execute page JS. Declining carries no such token, which is
why decline works and approve does not.
Rather than post a request that would be rejected — or worse, might not be, binding you to a quoted price — the tool refuses and tells you to approve in a browser.
Declining asks you to confirm first (see Confirmations): it reads the estimate, refuses ids that are not its options or are already decided, and shows exactly what would be sent before anything is posted. After a real decline it re-reads the estimate and reports the option's actual status, because a 2xx is not proof a write landed.
skills/housecallpro does the same reads from a
shell with plain curl and jq, for scripts or machines where the server isn't
installed. No browser bridge is involved there either.
Unlike much of this fleet, app.housecallpro.com is not bot-walled — a bare
curl gets a 200. So this server talks to it directly over HTTPS, has no
@fetchproxy/server dependency, needs no extension or signed-in tab, and hosts
cleanly as a remote connector — with no secret to configure, since the link
travels as a tool argument rather than an environment variable.
npm install
npm run build
npm test
MIT
Housecall Pro customer portal MCP server for Claude — developed and maintained by AI (Claude Code)
{ "mcpServers": { "chrischall-housecallpro-mcp": { "command": "npx", "args": [ "-y", "@chrischall/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@chrischall/housecallpro roda localmente via stdio.
Última verificação: 2026-11-17. Housecall Pro customer portal MCP server for Claude — developed and maintained by AI (Claude Code)