Jobber MCP server

Jobber Client Hub MCP

A Model Context Protocol server that connects Claude to the Jobber Client Hub — the customer portal that home-service businesses (pest control, lawn care, HVAC, cleaning) use to send you appointments, quotes and invoices.

[!WARNING]

AI-developed project. This codebase was built and is actively maintained

by Claude Code. No human has audited the

implementation. Review all code and tool permissions before use.

This is the customer side, not the business side

Jobber has two surfaces, and they share nothing:

If you run a business on Jobber, you want the Developer API instead — jobber-mcp by justinvogel covers that surface. This server is for being someone's customer, and the reasoning is written up in skills/jobber-fpx/references/why-not-the-api.md.

What you can do

• "When is the exterminator coming next?"
• "Do I owe Queen Bee's anything?"
• "Show me every invoice they've sent this year."
• "What did I ask them to do in my last work request?"

Read-only, and not by omission — see Why there are no writes.

Requirements

allowing getjobber.com, and a signed-in Client Hub tab

• Claude Desktop or Claude Code
• Node.js 22 or later
• Chrome with the Transporter (fetchproxy) extension, its Site access

emails

• A Client Hub link from a provider — the "View Details" button in any of their

Setup

{
  "mcpServers": {
    "jobber": {
      "command": "npx",
      "args": ["-y", "@chrischall/jobber-mcp"],
      "env": { "JOBBER_HUB_ID": "<the UUID from your hub URL>" }
    }
  }
}

Your hub URL looks like clienthub.getjobber.com/client_hubs//. The UUID is the whole credential — anyone holding it can read the hub — so treat it like a password.

Several providers, several hubs (there is no combined view):

"env": {
  "JOBBER_HUBS": "[{\"label\":\"queenbee\",\"hubId\":\"…\"},{\"label\":\"greenworx\",\"hubId\":\"…\"}]"
}

Then pass hub: "greenworx" to any tool. With one hub configured you never need the argument.

Tools

Shortened. The full README is on GitHub.