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:

	Developer API	Client Hub (this repo)
Serves	the business running on Jobber	that business's customers
Auth	OAuth2 app you register	the hub link your provider emailed you
Reachable from a server	yes	no — Cloudflare

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

• Claude Desktop or Claude Code
• Node.js 22 or later
• Chrome with the Transporter (fetchproxy) extension, its Site access allowing getjobber.com, and a signed-in Client Hub tab
• A Client Hub link from a provider — the "View Details" button in any of their emails

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/<UUID>/. 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.

Variable	Meaning
JOBBER_HUB_ID	Single hub UUID
JOBBER_HUB_LABEL	Name for that hub (default default)
JOBBER_HUBS	JSON array of {label, hubId} for several providers
JOBBER_WS_PORT	fetchproxy concentrator port (default 37149 — don't change it)
JOBBER_DEBUG_LOG	Bridge debug logging to stderr

Tools

Tool	Returns
jobber_list_appointments	Visits, grouped Today / Upcoming / Past
jobber_list_invoices	Invoices with number, subject and section (Paid, Overdue, …)
jobber_list_quotes	Quotes with their approval section
jobber_list_work_requests	Requests you raised
jobber_read_page	Readable text of any hub page, including detail pages
jobber_list_hubs	Configured hubs (labels only — never the ids)
jobber_healthcheck	Which layer is broken: bridge, config, or hub

jobber_list_* keeps each record's metadata rows raw in details rather than forcing a schema. Which rows a card shows depends on its state — an unpaid invoice carries a balance row a paid one does not — so a fixed schema would invent fields for some records and drop rows from others.

Why the browser bridge is not optional

Verified live 2026-08-09: clienthub.getjobber.com sits behind a Cloudflare managed challenge that fingerprints the TLS client, not the User-Agent. curl and Node both get 403 with the Just a moment interstitial, and keep getting it when handed a current Chrome UA and the full browser Accept* header set. The identical request from inside a real tab returns 200.

There is also no JSON API to fall back on: the hub is a server-rendered Rails app that makes zero API calls to its own origin. clienthub.getjobber.com/api/graphql exists and answers introspection, but it serves the same staff schema as the Developer API — it is not a client-facing endpoint.

Why this is not hosted on mcp-host

Every other reason to run an MCP server rather than a shell script is about reach — using it from claude.ai, on a phone, anywhere the CLI is not. This server cannot deliver that, and the reason is structural rather than a missing afternoon of work.

mcp-host runs children on a Fly machine. There is no browser there and no Transporter extension, and a lifted cookie does not help: cf_clearance is bound to IP, User-Agent and TLS fingerprint together, so a session captured on a laptop is dead the moment a datacenter replays it. mcp-host's own docs/BROWSER-BRIDGE.md designs a path for exactly this class of server and states plainly that no hosting path is implemented yet.

So this repo is built to be ready rather than hosted: the concentrator port comes from JOBBER_WS_PORT via readPortEnv, matching the twelve of thirteen browser-bridge MCPs that already do this, so a future host can attribute a socket to this child without a code change. It deliberately does not use the @fetchproxy/bootstrap "lift the session once" pattern, which is the one shape that cannot name a port at all.

Why there are no writes

The hub can submit work requests, approve quotes and pay invoices. None of them are here:

• Those flows are form POSTs carrying CSRF tokens and, on some paths, a Turnstile token read from the DOM. The bridge does fetch(), not DOM reads, so it cannot complete them — a write tool would fail unpredictably rather than work.
• Paying an invoice means handling card or bank details. That belongs in your hands, in your browser, not in an agent's tool call.

Without the MCP

skills/jobber-fpx/ does the same reads from a shell with the fpx CLI — no server process. Same bridge, same pages, one command.

Development

npm install
npm run build
npm test

The suite mocks the network entirely; tests/server-boot.test.ts additionally boots the real built artifacts — including the bundle in a directory with no node_modules, as the .mcpb runs — and drives a full initialize + tools/list handshake.

Acknowledgement of terms

1. This server accesses your own Client Hub. Every request is dispatched through your own signed-in browser session via the fetchproxy extension, reusing the session you already have. It does not — and cannot — reach anyone else's hub.

2. Jobber's Terms of Service govern your use of this server, exactly as they govern your direct use of the hub in a browser. Review them, and stop using this server if your use of it would not comply.

License

MIT