Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

Housecall Pro MCP

von hcpapiVersion 1.19.0i★ –iLäuft auf deinem Computer
Name in der Registryio.github.hcpapi/housecall-pro-mcp

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft auf deinem Computer
  • Transport: stdio
  • Kategorie: Sonstiges
  • Das musst du eintragen: HCP_API_KEY

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 1 von 1 bestanden
  • Läuft auf deinem Computer mit den Rechten deines Benutzerkontos (Dateien, Netzwerk, Apps).
  • Das trägst du selbst ein: HCP_API_KEY, HCP_READ_ONLY, HCP_TOOLSETS, HCP_TOOLS

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

  • npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "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"
      }
    }
  }
}

Führe das in deinem Terminal aus

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-mcp

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "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"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "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"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

  • HCP_API_KEY geheim erforderlich env
    A Housecall Pro API key. Generated under My Apps, Go to App store, API Key Management. Requires their MAX plan and an admin login.
  • HCP_READ_ONLY env
    Set to 1 to register no tool that can change anything in Housecall Pro.
  • HCP_TOOLSETS env
    Comma-separated groups to register: company, customers, jobs, estimates, invoices, pricebook, schedule, reports, admin. Also 'all' and 'default'. Fewer tools in context makes a client choose better a…
  • HCP_TOOLS env
    Comma-separated tool names to register in addition to the toolsets, e.g. hcp_list_jobs. Pair with HCP_TOOLSETS=none for exactly these tools. An unknown name stops the server rather than silently regi…

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto hcpapi bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • – Nicht zutreffend

    Endpunkt antwortet

    Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen

  • … Noch nicht geprüft

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen

Im Vergleich mit anderen in Sonstigesi

  • Mehr Sterne als 0 % der anderen 32599 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 63 % der anderen 32599 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 32599 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Housecall Pro MCP sicher?

Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: HCP_API_KEY

Läuft er auf meinem Computer oder in der Cloud?

Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.19.0) kam vor 23 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Zendesk

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Spec Driven Development

von formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Läuft auf deinem Computer★ 440MITAktualisiert vor 14 Monaten
Installieren

Remote Desktop Commander

von desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Läuft in der Cloud★ 211Aktualisiert vorgestern
Installieren

Zendesk

von pipeworx-io

Zendesk MCP Pack — tickets, users, organizations via OAuth.

Computer oder CloudAktualisiert heute
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

Housecall Pro MCP Server

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.

Install

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.

Housecall Pro API quirks, and what this server does about them

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 doesWhat 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.

The hcp command line

The 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.

Documented routes that do not exist

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.

DocumentedReality
POST, PUT, DELETE /appointmentsAbsent. Appointments exist only nested under a job.
PUT /jobs/{id}Absent. PATCH /jobs honours only the nested schedule object.
POST /invoicesAbsent.
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}/tagsAbsent.
PUT /jobs/{id}/lockThe 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/servicesAbsent. Materials and categories create normally.
GET /webhooks/subscriptionAbsent.
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.

What you can ask

  • "How much did we invoice in June, grouped by service?"
  • "List this week's scheduled jobs with outstanding balances"
  • "Pull up the customer record for the Smiths on Elm Street"
  • "Which customers are tagged 'Service Plan'?"
  • "Export Q2 invoices as CSV"
  • "What's in our price book for water heaters?"
  • "When is job_123 booked, and who is going?"
  • "Show me invoice_123 the way the customer sees it"
  • "Add a new customer: John Baker, 22 Elm St, Springfield IL, +1 555 123 4567"
  • "Draft a good/better/best estimate for cus_123: water heater replacement at $2,400 / $3,100 / $3,900"
  • "Book Tuesday 8-10am on job_123 for Mike"
  • "Move that visit to Thursday morning and put Dave on it instead"
  • "Dispatch Mike and Dave to job_123"
  • "Reprice every labor line on job_123 in one go"
  • "The customer went with the middle option on that estimate - mark it approved"
  • "What hours do we work, and what's free next week?"
  • "Default our jobs to 90 minutes with a two-hour arrival window"

Getting your Housecall Pro API key

  1. Sign in to Housecall Pro as an admin. Office staff logins cannot generate keys.
  2. Open My Apps, the grid icon in the top bar
  3. Click Go to App store, search for API, and open API Key Management. It will usually not be sitting in the My Apps menu already, because that menu lists a subset rather than the whole catalogue.
  4. Click Generate new API key, name it, and choose its access level:
  • Read-only, for reporting, lookups and exports. It refuses writes across the account with one exception we have measured: the price-book routes under /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.
  • Full access, which also allows creating customers, jobs and estimates.
  1. Copy the key. Housecall Pro keeps it visible on that page afterwards, so you can come back and copy it again. What you cannot do is edit a key: changing the access level means generating a new one and deleting the old.

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.

Tools

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.

Reading
ToolWhat it does
hcp_get_companyCompany profile, with the account's time zone and its default arrival window
hcp_get_schedule_availabilityThe hours the account works, and how far ahead it takes bookings
hcp_list_booking_windowsThe slots Housecall Pro reports as bookable, and which of them are open
hcp_search_customersSearch or list customers, or filter by tag
hcp_get_customerOne customer's full record
hcp_contactabilityWhether customers are safe to contact - unions every do-not-contact signal the API can read, and names the one it can't
hcp_list_jobsJobs by status, schedule window, or customer
hcp_get_jobOne job's full record
hcp_get_job_notes · hcp_get_job_countA job's notes, and the account's total job count
hcp_list_job_appointmentsA job's booked visits, windows and technicians
hcp_get_job_line_itemsOne job's line items, priced in dollars
hcp_get_job_input_materialsWhat was actually used on a job, as distinct from what was billed
hcp_list_checklistsChecklists attached to jobs or estimates
hcp_list_invoicesInvoices in a date range, filterable by status (paid, open, canceled)
hcp_get_invoiceOne invoice in full, with payments, refunds and balance

| hcp_get_job_invoices | A single job's invoices, without

Nur der Anfang wird gezeigt; den Rest findest du im Repo

PopNx fragen