# Housecall Pro MCP Server and API by Cotlet (remote · cotlet.dev)

Housecall Pro home service management MCP server: create job, create estimate, create invoice.

- Trust score: 70/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-11). See the changelog below before you install this server.

## Components

- remote · `cotlet.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro.md), [page](https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro)
- remote · `cotlet.dev`: 40/100, [markdown](https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro-connect.md), [page](https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro-connect)

## Channel facts

- Endpoint: `https://cotlet.dev/mcp/v1/housecall-pro`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cotlet_browser_click).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 8039 tokens (~160/item across 50 items; 48 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 92/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "housecall_pro_send_invoice" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Housecall Pro MCP Server and API by Cotlet server?

Housecall Pro MCP Server and API by Cotlet is a hosted endpoint at https://cotlet.dev/mcp/v1/housecall-pro, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-cotlet-housecall-pro 'https://cotlet.dev/mcp/v1/housecall-pro'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-cotlet-housecall-pro": {
      "url": "https://cotlet.dev/mcp/v1/housecall-pro"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-cotlet-housecall-pro": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/housecall-pro"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-cotlet-housecall-pro]
url = "https://cotlet.dev/mcp/v1/housecall-pro"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-cotlet-housecall-pro": {
      "type": "remote",
      "url": "https://cotlet.dev/mcp/v1/housecall-pro",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-cotlet-housecall-pro --url 'https://cotlet.dev/mcp/v1/housecall-pro' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-cotlet-housecall-pro:
    url: "https://cotlet.dev/mcp/v1/housecall-pro"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-cotlet-housecall-pro": {
      "Transport": "http",
      "Url": "https://cotlet.dev/mcp/v1/housecall-pro"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-cotlet-housecall-pro -t streamable-http -u 'https://cotlet.dev/mcp/v1/housecall-pro'
```

### Other

```json
{
  "mcpServers": {
    "dev-cotlet-housecall-pro": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/housecall-pro"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 70, −3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cotlet_browser_type” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 100% → 50%
- [functional] New resource “cotlet-refresh-button”

### 2026-11-19 (score 73, +1)

- [security] Tool “cotlet_upload_file” rewrote its description, which is the text the model reads

### 2026-11-17 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 141 → 160
- [cosmetic] “cotlet_browser_download” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_drag” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_evaluate” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_fill_form” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_find” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_hover” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_navigate” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_press” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_read” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_screenshot” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_scroll” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_select” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_type” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_upload” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_wait” added an optional parameter “tab”
- [cosmetic] “cotlet_browser_click” added an optional parameter “tab”

### 2026-11-15 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cotlet_whoami” rewrote its description, which is the text the model reads

### 2026-11-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 70, 0)

- [security] Tool “cotlet_browser_download” rewrote its description, which is the text the model reads

### 2026-11-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 69, +43)

- [critical regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 67
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

## MCP tools (48)

### `cotlet_whoami` (~80 tokens)

Cotlet: who am I

The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call, its credit balance, and the app the user signed up for with its first task and sign-in link. Free. Needs the user's Cotlet API key or sign-in.

### `cotlet_apps` (~85 tokens)

Cotlet: apps I can use

The apps of the user's workspace and whether each works now: the app account in the user's Cloud Browser (connected, signed out, signed in but not connected), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.

Input parameters:

- `app` (string): Only this app, e.g. skool.

### `cotlet_request_apps` (~170 tokens)

Cotlet: request access to apps

Requests access to apps for the user's workspace, as Request access in the console: every app is granted at once. Not needed to work in an app: the user's AI works in any web app in their Web browser with cotlet_app_guide. An app with dedicated tools gets them after the user signs in to it in their Cloud Browser. Access says nothing about whether a task works there: check that in the browser. Takes app slugs as listed at https://cotlet.dev/api/v1/apps. Free. Needs the user's Cotlet API key or sign-in.

Input parameters:

- `apps` (array, required): App slugs, e.g. ["skool", "substack"].
- `use_case` (string): What the user wants the agent to do in these apps, in their words.

### `cotlet_get_call` (~76 tokens)

Cotlet: check a call

Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.

Input parameters:

- `call_id` (string, required): call_id from the earlier call

### `cotlet_upload_file` (~125 tokens)

Cotlet: upload a file for a tool

Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL takes one stored file (a failed PUT can be sent again). Free. Needs the user's Cotlet API key or sign-in.

Input parameters:

- `content_type` (string): MIME type, e.g. image/jpeg.
- `name` (string): File name, e.g. photo.jpg.

### `cotlet_report_issue` (~364 tokens)

Cotlet: report a bug or a missing feature

Sends a report to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a step the browser could not do, with the page, the step and what you saw. A missing dedicated tool is not a problem to report: do the task in the browser. A feature the user asks for goes as feature_request. A report promises nothing: tell the user it was sent, never that something will be built or fixed, or when. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.

Input parameters:

- `app`: App slug the report is about, e.g. 'skool', or for a site in the web browser its host, e.g. 'app.example.com'.
- `call_id`: call_id of the call that went wrong, if any.
- `client`: Agent or tool sending this, e.g. 'Claude Code'.
- `description` (string, required): What the user asked for, what you tried, what you expected and what happened, with the error text if there was one. No passwords, tokens or other secrets.
- `kind` (string, required): bug: a tool did the wrong thing or returned wrong data. error: a call failed or returned an error you could not get past. feature_request: something new the user asked for. missing_feature: a step th…
- `title` (string, required): One line, e.g. 'skool_list_members stops after 50 members'.
- `tool`: Tool or endpoint name, e.g. 'skool_list_members'.

### `cotlet_browser_open` (~128 tokens)

Open the browser

Starts the user's Housecall Pro Cloud Browser (a real Chrome on Cotlet, signed in to Housecall Pro as the user; use it for what the Housecall Pro tools do not cover) and opens `url`. Call it first. Only Housecall Pro pages open. Answers the page after it: the elements and text in view, with the same numbers. In Housecall Pro it serves these actions: Create job, Create estimate, Create invoice, Send invoice, List customers.

Input parameters:

- `url` (string): A public http or https address, e.g. https://example.com.

### `cotlet_browser_navigate` (~200 tokens)

Go to a page

Opens `url` in the current tab, or goes `history` back or forward. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `history` (string): Instead of `url`.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `url` (string): A public http or https address, e.g. https://example.com.

### `cotlet_browser_read` (~154 tokens)

Read the page

The whole current page: its text (up to 20,000 characters) and a numbered list of its links, buttons, fields and other controls, open dialogs first. Use it on a new page or when a step's answer is not enough; `element` reads only inside one element (a dialog, a form, a list). Never returns field values, cookies or storage.

Input parameters:

- `element` (integer): Read only inside this element.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_find` (~141 tokens)

Find on the page

Finds `text` on the whole current page, frames included: the elements whose label holds it, with their numbers, and each line of text that holds it. Use it instead of reading or scrolling a long page for one thing.

Input parameters:

- `kind` (string): Only elements of this kind. Default: any.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `text` (string, required): Words to look for, any case.

### `cotlet_browser_screenshot` (~110 tokens)

See the page

A JPEG of the visible part of the page. Use it for boards, canvases, maps, charts and layout that the text does not show, then click or drag by `x`, `y` of the image.

Input parameters:

- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_scroll` (~193 tokens)

Scroll the page

Scrolls with the mouse wheel: `down` or `up` by `screens`, to `top` or `bottom`, until `element` is in view, or inside a panel or list (`inside`). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `direction` (string): Default: down.
- `element` (integer): Scroll until this element is in view.
- `inside` (integer): Scroll inside this element, not the page.
- `screens` (number): Viewport heights, for down and up. Default: 0.8.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_click` (~300 tokens)

Click on the page

Clicks element `element`, or point `x`, `y` of the screenshot; `double` double-clicks, `button: right` right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.

Input parameters:

- `button` (string): right opens the page's own context menu. Default: left.
- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `double` (boolean): Double-click.
- `element` (integer): The element's number from the last read or step answer.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `x` (number): Instead of `element`: pixels from the left of the screenshot.
- `y` (number): With `x`: pixels from the top of the screenshot.

### `cotlet_browser_hover` (~160 tokens)

Point at the page

Rests the pointer on an element or a point, to open a hover menu, a tooltip or a preview. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `element` (integer): The element's number from the last read or step answer.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `x` (number): Instead of `element`: pixels from the left of the screenshot.
- `y` (number): With `x`: pixels from the top of the screenshot.

### `cotlet_browser_drag` (~211 tokens)

Drag on the page

Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `from` (object, required): An element number, or x and y of the screenshot.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `to` (object, required): An element number, or x and y of the screenshot.

### `cotlet_browser_type` (~334 tokens)

Type on the page

Types `text` into field `element`, replacing what it held; `submit` presses Enter after it. For several fields use fill_form. Without `element` the text goes where the focus is, as a person types after clicking: for spreadsheet cells and editors that read does not number (Google Sheets, Docs), click the place first; there a tab in `text` presses Tab and a line break Enter, so one call fills a table. Answers the page after it: the elements and text in view, with the same numbers. A password or code the user gave you goes in like any text; card fields are refused.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `element` (integer): The field's number from the last read. Leave it out to type where the focus is.
- `slowly` (boolean): Key by key, for a search or address field whose suggestions do not appear.
- `submit` (boolean): Press Enter after typing, e.g. to search.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `text` (string, required): The text to type.

### `cotlet_browser_fill_form` (~220 tokens)

Fill in a form

Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `fields` (array, required): The fields in the order a person fills them.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_select` (~212 tokens)

Choose from a list

Chooses `option` (its label as listed, or its value) in drop-down `element`. For a home-made drop-down, click it, then click the option. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `element` (integer, required): The element's number from the last read or step answer.
- `option` (string, required): The option.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_press` (~262 tokens)

Press a key

Presses a key on the focused element: Enter to send, Tab to the next field, Escape to close a pop-up, arrows in a list or slider, or one character (a site's shortcut). Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `dialog` (string): How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
- `dialog_text` (string): Text for a prompt dialog this step opens; implies accept.
- `key` (string, required): One of Enter, Tab, Shift+Tab, Escape, Backspace, Delete, Space, ArrowDown, ArrowUp, ArrowLeft, ArrowRight, PageDown, PageUp, Home, End, or one character such as a or 5.
- `repeat` (integer): Times to press it. Default 1.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_upload` (~158 tokens)

Upload a file

Puts files into file field or upload button `element`: each file is {"url": "https://..."} or {"file_id": "..."} of a file uploaded to Cotlet; up to 10 files, 20 MB each. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `element` (integer, required): The element's number from the last read or step answer.
- `files` (array, required): The files.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_download` (~160 tokens)

Download a file

Gets the file that clicking `element` (a download link or button) or opening `url` starts, also an image or PDF it only opens: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.

Input parameters:

- `element` (integer): The element's number from the last read or step answer.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `url` (string): A public http or https address, e.g. https://example.com.

### `cotlet_browser_evaluate` (~165 tokens)

Run a script on the page

Runs a JavaScript function body on the page and answers what it returns, as JSON. Use it to extract data the page holds (a table, a list, attributes); act with the other tools. It cannot send requests, click, submit, or read cookies or storage; a filled field's value reads [hidden by Cotlet]. Example: return [...document.querySelectorAll('h2')].map(h => h.innerText)

Input parameters:

- `script` (string, required): A function body that returns.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…

### `cotlet_browser_wait` (~144 tokens)

Wait for the page

Waits until `text` shows on the page (at most `seconds`, default 5, up to 20), or just `seconds`: for results that load slowly. Says whether the text appeared. Answers the page after it: the elements and text in view, with the same numbers.

Input parameters:

- `seconds` (number): At most.
- `tab` (string): The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th…
- `text` (string): Text to wait for.

### `cotlet_browser_close` (~43 tokens)

Close the browser

Ends the browser session when the task is done: the browser keeps its cookies and sleeps, and the per-minute charge stops. Answers the session's minutes and credits.

### `cotlet_app_guide` (~171 tokens)

Cotlet: how to work in an app

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Housecall Pro it covers these actions: Create job, Create estimate, Create invoice, Send invoice, List customers.

Input parameters:

- `app` (string): The app's name or Cotlet slug. Default: Housecall Pro.
- `task` (string): What the user wants done in the app, in their words.

### `get_estimate` (~53 tokens)

Get estimate

One estimate with its customer, status and every option with its lines and total.

Input parameters:

- `estimate_id` (string, required): estimate_id from list_estimates (best_…); an option_id (est_…) works too.

### `get_invoice` (~68 tokens)

Get invoice

One invoice with its customer, amount, amount due, due terms and when it was sent and paid. amount is this invoice's part; job_total is the whole job's total (progress invoices bill a part).

Input parameters:

- `invoice_id` (string, required): invoice_id from list_invoices or get_job.

### `get_job` (~40 tokens)

Get job

One job with its line items, schedule, employees, balance and the invoices made from it.

Input parameters:

- `job_id` (string, required): job_id from list_jobs.

### `get_schedule` (~113 tokens)

Get schedule

Scheduled jobs and estimate visits on the calendar for a date range, with the assigned employees. Days are in the company's time zone; start and end come back in UTC. record_id is a job or estimate.

Input parameters:

- `employee_id` (string): Only this employee's visits (list_employees).
- `end_date` (string): Last day, YYYY-MM-DD, at most 31 days on. Default: 7 days on.
- `start_date` (string): First day, YYYY-MM-DD. Default: today.

### `list_customers` (~116 tokens)

List customers

Customers of the company with contact details; search by name, email, phone or address. Newest customers first, 25 per page by default (up to 100); pass next_cursor back as cursor. Phone numbers come as the app stores them, and only mobile_number can receive texts.

Input parameters:

- `cursor` (string): next_cursor from the previous call.
- `limit` (integer): 1 to 100. Default: 25.
- `search` (string): Part of a name, email, phone number or address.

### `list_employees` (~59 tokens)

List employees

The company's employees (field techs, office, admins) with role and contact, for dispatch. Use employee_id in create_job and create_estimate to assign work.

Input parameters:

- `include_archived` (boolean): Also archived employees. Default: false.

### `list_estimates` (~72 tokens)

List estimates

Estimates, newest first, with customer, pipeline status and value. value is the highest option's total. Use estimate_id in get_estimate for options and lines.

Input parameters:

- `cursor` (string): next_cursor from the previous call.
- `limit` (integer): 1 to 100. Default: 25.

### `list_invoices` (~137 tokens)

List invoices

Invoices, newest number first, with customer, amount, amount due and last payment. Filters by status only (open, pending_payment, paid); there is no date or customer filter. To find past-due invoices, read the open ones and compare due_at with today where due_amount is above 0. Statuses come back as the list shows them (Paid); get_invoice returns them in lowercase.

Input parameters:

- `cursor` (string): next_cursor from the previous call.
- `limit` (integer): 1 to 100. Default: 25.
- `status` (array): Only invoices in these statuses. Default: all.

### `list_jobs` (~145 tokens)

List jobs

Jobs, newest first, with customer, schedule, assigned employees, total and balance. Filters by work status (unscheduled, scheduled, in_progress, completed) and, after each page is read, by customer_id, so a page can come back short while next_cursor is still set: keep paging. Line items and invoices come from get_job.

Input parameters:

- `cursor` (string): next_cursor from the previous call.
- `customer_id` (string): Only this customer's jobs (customer_id from list_customers).
- `limit` (integer): 1 to 100. Default: 25.
- `status` (array): Only jobs in these work statuses. Default: all four.

### `list_price_book` (~99 tokens)

List price book

Services or materials of the company's price book with price, cost and category. Use the name, description and price as line items in create_job or create_estimate.

Input parameters:

- `cursor` (string): next_cursor from the previous call.
- `kind` (string): services or materials. Default: services.
- `limit` (integer): 1 to 100. Default: 25.
- `search` (string): Part of a name or description.

### `add_estimate_option` (~88 tokens)

Add estimate option

Add another option (a separate price) to an estimate, with its own lines. The customer picks one option when approving. Returns the estimate with all its options.

Input parameters:

- `estimate_id` (string, required): estimate_id from list_estimates.
- `line_items` (array, required): Lines of the new option, in order.
- `name` (string): Option name. Default: Option #N.

### `create_customer` (~234 tokens)

Create customer

New customer with an optional service address; returns its customer_id and address_id.

Input parameters:

- `city` (string): Service address: city.
- `company` (string): Company name. Needed for a business customer without a first name.
- `email` (string): Email address. Housecall Pro sends job, estimate and invoice emails here.
- `first_name` (string): First name.
- `home_number` (string): Home phone.
- `kind` (string): homeowner or business. Default: homeowner.
- `last_name` (string): Last name.
- `mobile_number` (string): Mobile phone, US 10 digits.
- `notes` (string): Private notes on the customer.
- `notifications_enabled` (boolean): Let Housecall Pro send the customer job and invoice notifications. Default: true.
- `state` (string): Service address: state, e.g. OH.
- `street` (string): Service address: street.
- `street_line_2` (string): Service address: unit or suite.
- `work_number` (string): Work phone.
- `zip` (string): Service address: ZIP code.

### `create_estimate` (~132 tokens)

Create estimate

New estimate for a customer with its first option (Option #1) and lines. Sends nothing. Add more options with add_estimate_option, then email it with send_estimate.

Input parameters:

- `address_id` (string): Service address of the customer (create_customer). Default: the billing address.
- `customer_id` (string, required): customer_id from list_customers.
- `employee_ids` (array): Employees to assign (list_employees). Default: none.
- `line_items` (array, required): Lines of the first option, in order.
- `message` (string): Message to the customer shown on the estimate.

### `create_job` (~218 tokens)

Create job

New job for a customer with line items, optionally scheduled and assigned to employees. Creates the job as the New job form does. With start, it is scheduled in the company's time zone and assigned to employee_ids; the customer gets a scheduled email only with notify_customer.

Input parameters:

- `address_id` (string): Service address of the customer (create_customer). Default: the billing address.
- `customer_id` (string, required): customer_id from list_customers.
- `duration_minutes` (integer): Default: 60.
- `employee_ids` (array): Employees to assign (list_employees). Default: none.
- `end` (string): Scheduled end. Default: start plus duration_minutes.
- `line_items` (array, required): Lines, in order.
- `note` (string): Private job note.
- `notify_customer` (boolean): Email the customer that the job is scheduled. Default: false.
- `start` (string): Scheduled start, 2026-11-04T09:00 in the company's time zone. Default: unscheduled.

### `create_progress_invoice` (~189 tokens)

Create progress invoice

Invoice part of a job (an amount or a percent of its total); the rest stays to invoice later. Adds an invoice to the job as Invoice > Add invoice does with progressive invoicing on. Without amount or percent it bills everything left. Sends nothing: email it with send_invoice.

Input parameters:

- `amount` (number): Amount to bill in dollars.
- `due` (string): Payment terms: upon receipt, or net_days after the invoice date. Default: upon_receipt.
- `invoice_date` (string): YYYY-MM-DD. Default: today.
- `job_id` (string, required): job_id from list_jobs.
- `net_days` (integer): Days for net. Default: 30.
- `percent` (number): Or a percent of the job total. Default (neither): all that is left to invoice.
- `reference_number` (string): Customer reference (PO) number.

### `record_invoice_payment` (~166 tokens)

Record invoice payment

Record a cash or check payment on a job's invoices. No money is charged. Marks money already received as paid, as the job's Pay dialog does with Cash or Check. Housecall Pro applies it to the job's open invoices, oldest first. It can't be more than what is invoiced and unpaid; invoice the rest with create_progress_invoice first.

Input parameters:

- `amount` (number): Amount received in dollars. Default: everything invoiced and unpaid on the job.
- `job_id` (string, required): job_id of the invoiced job (get_job).
- `method` (string, required): cash or check.
- `note` (string): Payment note, e.g. the check number.
- `receipt_email` (string): Email a receipt to this address. Default: no receipt.

### `send_estimate` (~159 tokens)

Send estimate

Email an estimate to the customer with a link to approve one of its options. Sends as the Send button of the estimate page does, by email only. The customer gets the email at once and the estimate shows Awaiting Approval. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

Input parameters:

- `email` (string): Send to this address. Default: the customer's email.
- `estimate_id` (string, required): estimate_id from list_estimates.
- `message` (string): Email text. Default: the panel's greeting.
- `option_ids` (array): Options to include (get_estimate). Default: all.
- `subject` (string): Default: Estimate #N from <company>.

### `send_invoice` (~132 tokens)

Send invoice

Email an invoice to the customer as a PDF with the company's default or your own message. Sends as the Send invoice dialog does, by email only. The customer gets it at once. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

Input parameters:

- `email` (string): Send to this address. Default: the customer's billing email.
- `invoice_id` (string, required): invoice_id from list_invoices or get_job.
- `message` (string): Email text. Default: the company's invoice message.
- `subject` (string): Default: the company's invoice subject.

### `housecall_pro_create_job` (~113 tokens)

Create job in Housecall Pro

Create job in the user's own Housecall Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Housecall Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Housecall Pro Cloud Browser. Housecall Pro's official API: Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026).

### `housecall_pro_create_estimate` (~114 tokens)

Create estimate in Housecall Pro

Create estimate in the user's own Housecall Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Housecall Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Housecall Pro Cloud Browser. Housecall Pro's official API: Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026).

### `housecall_pro_create_invoice` (~113 tokens)

Create invoice in Housecall Pro

Create invoice in the user's own Housecall Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Housecall Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Housecall Pro Cloud Browser. Housecall Pro's official API: Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026).

### `housecall_pro_send_invoice` (~113 tokens)

Send invoice in Housecall Pro

Send invoice in the user's own Housecall Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Housecall Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Housecall Pro Cloud Browser. Housecall Pro's official API: Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026).

### `housecall_pro_list_customers` (~114 tokens)

List customers in Housecall Pro

List customers in the user's own Housecall Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Housecall Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Housecall Pro Cloud Browser. Housecall Pro's official API: Housecall Pro has a public REST API, but only on the MAX plan, with a limited-access API key (checked 14 Oct 2026).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 69
- 2026-11-10: 26
- 2026-11-09: 26

## Common questions

### What is the Housecall Pro MCP Server and API by Cotlet server?

Housecall Pro MCP Server and API by Cotlet is listed in the public MCP registry as dev.cotlet/housecall-pro. Housecall Pro home service management MCP server: create job, create estimate, create invoice. This page covers its hosted endpoint (https://cotlet.dev/mcp/v1/housecall-pro).

### Is the Housecall Pro MCP Server and API by Cotlet server safe to use?

Housecall Pro MCP Server and API by Cotlet scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Housecall Pro MCP Server and API by Cotlet server expose?

Housecall Pro MCP Server and API by Cotlet exposes 48 tools: cotlet_whoami, cotlet_apps, cotlet_request_apps, cotlet_get_call, cotlet_upload_file, and 43 more. Their descriptions and schemas cost roughly 7,153 tokens of context every time the server is loaded.

### Does the Housecall Pro MCP Server and API by Cotlet server require authentication?

No. We connected to Housecall Pro MCP Server and API by Cotlet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Housecall Pro MCP Server and API by Cotlet server still maintained?

Housecall Pro MCP Server and API by Cotlet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Housecall Pro MCP Server and API by Cotlet server?

VerifyMCP ran 13 checks on Housecall Pro MCP Server and API by Cotlet, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://cotlet.dev/mcp/v1/housecall-pro
- Authorisation metadata: https://cotlet.dev/.well-known/oauth-protected-resource/mcp/v1/housecall-pro
- Repository: https://github.com/cotlet-connect/housecall-pro-mcp
- Website: https://cotlet.dev/integrations/housecall-pro-api-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro.json
- HTML version of this page: https://verifymcp.io/servers/dev-cotlet-housecall-pro/mcp-v1-housecall-pro
