Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
HCP_API_KEY, HCP_READ_ONLY, HCP_TOOLSETS, HCP_TOOLS标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
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运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
HCP_READ_ONLY envHCP_TOOLSETS envHCP_TOOLS env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 hcpapi 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:HCP_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.19.0)于23天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读