Labsco
MCP SERVER

OpsConduit Jobber MCP

by opsconduit

Ask a Jobber account which estimates need chasing and which invoices are overdue — read-only.

ERP & Vertical Business Systems
Summary
Mutations are blocked before the request leaves, not refused by Jobber.

The GraphQL tool checks the operation locally, so a write cannot reach your account even by accident. Credentials never leave your machine either: you register your own Jobber app and the tokens land in a local file.

What it is

A connector for Jobber field-service accounts, hosted by you. It runs the OAuth setup locally, stores the tokens on your machine, and exposes read-only GraphQL against your own Jobber data.

What you get
  • jobber_auth_url — the one-time authorization link for a self-hosted install
  • jobber_exchange_code — swap the redirected code for tokens without them appearing in the conversation
  • jobber_refresh_token — refresh the stored access token
  • jobber_account — confirm which account is connected before running anything
  • jobber_clients_sample — a capped client sample to verify read access works
  • jobber_graphql_read — read-only Jobber GraphQL, with mutations blocked before the request is sent
Requirements

Node.js 20 or newer. Install @opsconduit/jobber-mcp, set JOBBER_CLIENT_ID and JOBBER_CLIENT_SECRET from your own Jobber developer app, then run the bundled auth helper — it prints the authorization URL, catches the callback at http://localhost:3333/oauth/callback, and writes the tokens to a local file. Runs over stdio.

Setup effort

One command plus a key — npm install @opsconduit/jobber-mcp, then supply credentials