Connect Housecall Pro to Cursor

Cursor speaks MCP over stdio, so the MCP works the same way it does in Claude Desktop. The entry goes in Cursor's own MCP configuration.

Setup

Generate a Housecall Pro API key

In Housecall Pro: My Apps, then Go to App store, then API Key Management. Choose Read-only unless you specifically want the MCP to be able to make changes. API access is a MAX-plan feature and you need an admin login.

The full walkthrough, with a direct link to the page
Open Cursor's MCP settings

Settings → MCP → add a new server. Cursor lets you configure servers globally or per project; global is usually right for this, since your Housecall Pro account is not project-specific.

Add the server

Command npx, arguments -y and housecall-pro-mcp, with HCP_API_KEY in the environment.

{
  "mcpServers": {
    "housecall-pro": {
      "command": "npx",
      "args": ["-y", "housecall-pro-mcp"],
      "env": { "HCP_API_KEY": "your-api-key-here" }
    }
  }
}

Your first ask

Ask something you already know the answer to. If it agrees with you, everything is wired correctly. If it does not, you have found something worth knowing about your book.

list our open estimates over $2,000

Worth knowing

Any client that speaks MCP over stdio works with the same three values: command npx, args -y housecall-pro-mcp, env HCP_API_KEY.
Keep the key out of a project-level file that is committed to git.

If it does not work

The two commonest causes are the plan and the header. API access is a MAX-plan feature, so on a lower plan there is no key to generate. And if you are hand-rolling requests rather than using the MCP, the auth header is Token, not Bearer. That one accounts for most "my key does not work" reports. The API guide covers the rest.

Still stuck: hello@hcpapi.com, or read the source, which is open.

← About the MCP