Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
HCP_API_KEY, HCP_READ_ONLY, HCP_TOOLSETS, HCP_TOOLSLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"housecall-pro": {
"command": "npx",
"args": [
"-y",
"housecall-pro-mcp"
],
"env": {
"HCP_API_KEY": "your-value",
"HCP_READ_ONLY": "your-value",
"HCP_TOOLSETS": "your-value",
"HCP_TOOLS": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add housecall-pro --env HCP_API_KEY=your-value --env HCP_READ_ONLY=your-value --env HCP_TOOLSETS=your-value --env HCP_TOOLS=your-value -- npx -y housecall-pro-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"housecall-pro": {
"command": "npx",
"args": [
"-y",
"housecall-pro-mcp"
],
"env": {
"HCP_API_KEY": "your-value",
"HCP_READ_ONLY": "your-value",
"HCP_TOOLSETS": "your-value",
"HCP_TOOLS": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"housecall-pro": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"housecall-pro-mcp"
],
"env": {
"HCP_API_KEY": "your-value",
"HCP_READ_ONLY": "your-value",
"HCP_TOOLSETS": "your-value",
"HCP_TOOLS": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
HCP_READ_ONLY envHCP_TOOLSETS envHCP_TOOLS envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub hcpapi, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: HCP_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.19.0) llegó al registro hace 23 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, SuperCollider
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
An open-source MCP server for the Housecall Pro API. Connect Claude, ChatGPT, Cursor, or any MCP-compatible AI agent to your Housecall Pro account, so you can ask for what you need instead of clicking through reports.
Independent project, not affiliated with, endorsed by, or sponsored by Housecall Pro. We run a service company on Housecall Pro ourselves, which is why it exists.
Needs Node 18 or newer and a Housecall Pro API key. API access comes with the MAX plan and is not available on lower tiers.
Claude Desktop. Open Settings, then Developer, then Edit Config, and add:
{
"mcpServers": { "housecall-pro": { "command": "npx", "args": ["-y", "housecall-pro-mcp"], "env": { "HCP_API_KEY": "your-api-key-here" } } } }
Restart Claude Desktop and the Housecall Pro tools will appear.
Claude Code. Add it directly:
claude mcp add housecall-pro -e HCP_API_KEY=your-api-key-here -- npx -y housecall-pro-mcp
Or install it as a plugin, which prompts for the key (stored in your keychain, never in a config file) and exposes the read-only and toolset switches as install-time options:
/plugin marketplace add hcpapi/housecall-pro-mcp
/plugin install housecall-pro@hcpapi
Cursor, Codex, and other MCP clients. Any client that speaks MCP over stdio works. Use npx as the command, ["-y", "housecall-pro-mcp"] as the arguments, and put HCP_API_KEY in the environment.
Getting a key takes about a minute and is described under Getting your Housecall Pro API key.
These are the edges of the Housecall Pro API itself. Each one is a place an integration built from the documentation alone gets a wrong answer rather than an error.
| What the API does | What this server does about it |
|---|---|
Money is integer cents, so $250 is 25000. | Converts in both directions. $250 stays $250 and never arrives as $2.50. |
PATCH /jobs answers 200 and changes nothing when sent a flat schedule key, a description, or tags. | Sends only the nested schedule object the API honours, so a reported success is a real one. |
| A job's description is derived from its line items and cannot be set directly. | Exposes line-item writes rather than a description field that would silently do nothing. |
Invoices filter on created_at, due_at, paid_at and amount_due, but not on service_date or invoice_date. An unsupported filter name is accepted and ignored rather than refused. | Uses the names the endpoint actually takes, and walks a service-date window client-side because no server-side equivalent exists. |
work_status reads back in a different vocabulary than it is written, for example complete unrated rather than completed. | Normalises on read, so a status filter matches real records instead of nothing. |
| Deleted jobs still appear in list responses and count toward totals. | Surfaces deleted_at on every row and warns, so revenue is not overstated. |
| Removing a tag from a job answers with an empty success whether or not the tag was there. | Reports the request as accepted rather than claiming a removal it cannot confirm. |
| An archived job refuses to describe its appointments. | Flags the job as archived and returns an empty list, so a sweep never stops part way. |
| The invoice document is a very long HTML page, not a PDF. | Returns the opening of the page and says how much of it that was. |
Attachments have no route of their own, GET on a job's attachments path serves an HTML 404, but expand[]=attachments returns them with a signed download link. | Asks with expand and hands back the files. The link is minted per request, so it is fetched when given and never stored. |
Some routes answer only on PUT, and a POST to the same path returns an HTML 404 page, which reads as "no such route" rather than as the wrong method. | Uses the method each route actually takes, so dispatching a crew and bulk line-item updates work instead of looking absent. |
Never trust a 2xx on a Housecall Pro write. Read the record back. Several routes answer 200 without changing anything, which is why the rows above exist.
hcp command lineThe same package installs hcp, which reaches the same Housecall Pro surface from a terminal. It is the same code: every command is one of the tools below, with the same conversions, the same filters and the same refusals.
It exists because an MCP server only runs while an assistant is in the room. A scheduled task that writes an aging report every Monday morning is not something an MCP client can do.
npm install -g housecall-pro-mcp # or run it once with: npx -p housecall-pro-mcp hcp
export HCP_API_KEY=your-api-key-here
hcp list jobs --work-status completed --page-size 20 hcp jobs list --page-size 20 # the same command, read either way round hcp get customer cus_1a2b3c hcp search customers "smith" hcp list invoices --csv > unpaid.csv
Windows, macOS and Linux, wherever Node 18+ runs.
Output. A table sized to your terminal by default, --json for the full records, --csv for a spreadsheet or a scheduled export. Data goes to stdout and commentary to stderr, so a redirect gets the data and nothing else.
Before you change anything. --dry-run prints exactly what a command would send and sends nothing. --read-only refuses any command that could change your account, and says which switch stopped it.
Finding your way around. hcp on its own lists the commands by group. hcp commands prints them one per line, and hcp commands --json gives the whole table, including which ones write. hcp --describe prints that command's parameters without running it.
hcp create customer --first-name Alex --last-name Rivera --dry-run
hcp list jobs --describe
Every switch below that applies to the server applies here too, including --toolsets.
Housecall Pro's published documentation describes these. They are not there. An integration built from the docs alone ships broken code paths for each one.
| Documented | Reality |
|---|---|
POST, PUT, DELETE /appointments | Absent. Appointments exist only nested under a job. |
PUT /jobs/{id} | Absent. PATCH /jobs honours only the nested schedule object. |
POST /invoices | Absent. |
DELETE /customers/{id} | Absent. There is no public customer delete. |
PUT or DELETE /customers/{id}/addresses/{adr} | Absent. Addresses are append-only. |
PUT or DELETE /estimates/{id} and /estimates/{id}/options/{opt} | Absent. |
PUT or DELETE /leads/{id} | Absent as writes: a lead cannot be updated or deleted. Reading works: GET /leads, GET /leads/{id} and GET /leads/{id}/line_items are all live. |
DELETE /tags/{id} | Absent. A tag can never be deleted through the API. |
DELETE /jobs/{id}/tags | Absent. |
PUT /jobs/{id}/lock | The verb is absent, not the route: POST /jobs/{id}/lock locks one job. The bulk POST /jobs/lock also exists and keys on starting_at rather than a list of job ids. |
POST /api/price_book/services | Absent. Materials and categories create normally. |
GET /webhooks/subscription | Absent. |
GET /employees/{id} | Absent. There is no employee detail route: an id that GET /employees just returned serves an HTML 404. Read the row from the listing. |
/api/price_book/ are not covered by that gate, and a read-only key can create and delete price-book categories there. If you want a guarantee rather than nearly one, run this server with --read-only, which does not register a write tool at all.The walkthrough with screenshots is at https://hcpapi.com/mcp/#key.
The access level you pick is the real boundary. This server follows whatever you generated, so a read-only key cannot reach the write tools at all. If you want an assistant that only answers questions, generate a read-only key and Housecall Pro enforces that limit for you.
Only an admin can generate a key, and admins have full account access, so the key reaches the whole account rather than one person's slice of it.
96 tools. Reading works with any key; writing needs a full-access one. They are grouped into toolsets, so an install can register only the groups it needs - see Choosing which tools to register.
| Tool | What it does |
|---|---|
hcp_get_company | Company profile, with the account's time zone and its default arrival window |
hcp_get_schedule_availability | The hours the account works, and how far ahead it takes bookings |
hcp_list_booking_windows | The slots Housecall Pro reports as bookable, and which of them are open |
hcp_search_customers | Search or list customers, or filter by tag |
hcp_get_customer | One customer's full record |
hcp_contactability | Whether customers are safe to contact - unions every do-not-contact signal the API can read, and names the one it can't |
hcp_list_jobs | Jobs by status, schedule window, or customer |
hcp_get_job | One job's full record |
hcp_get_job_notes · hcp_get_job_count | A job's notes, and the account's total job count |
hcp_list_job_appointments | A job's booked visits, windows and technicians |
hcp_get_job_line_items | One job's line items, priced in dollars |
hcp_get_job_input_materials | What was actually used on a job, as distinct from what was billed |
hcp_list_checklists | Checklists attached to jobs or estimates |
hcp_list_invoices | Invoices in a date range, filterable by status (paid, open, canceled) |
hcp_get_invoice | One invoice in full, with payments, refunds and balance |
| hcp_get_job_invoices | A single job's invoices, without
Solo se muestra el principio; lee el resto en el repo