jobber_auth_urlLABSCO 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 credentials — npm install @opsconduit/jobber-mcp, then supply credentials
USE CASES
01
Finding the follow-up that is leaking revenue
Query which estimates are still waiting and which invoices have gone past due.
02
Spotting jobs that have gone quiet
Read which jobs are unscheduled, stale or blocked, and which customers have had no recent activity.
03
Connecting the account the first time
Generate the authorization link, exchange the returned code, and confirm which account you ended up on.
04
Checking read access before trusting a report
Pull a capped client sample to prove the token works and the scopes are right.
6 tools
Listed in project docs. Your client may show a different list.
jobber_exchange_codejobber_refresh_tokenjobber_accountjobber_clients_samplejobber_graphql_readBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- JOBBER_CLIENT_ID in your environment
- JOBBER_CLIENT_SECRET in your environment
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"opsconduit-jobber": {
"command": "npx",
"args": [
"-y",
"-p",
"@opsconduit/jobber-mcp",
"opsconduit-jobber-mcp"
],
"env": {
"JOBBER_CLIENT_ID": "<YOUR_JOBBER_CLIENT_ID>",
"JOBBER_CLIENT_SECRET": "<YOUR_JOBBER_CLIENT_SECRET>",
"JOBBER_REDIRECT_URI": "http://localhost:3333/oauth/callback",
"JOBBER_REQUEST_TIMEOUT_MS": "30000",
"JOBBER_TOKEN_STORE": "<YOUR_PATH_TO_OPSCONDUIT_JOBBER>/.opsconduit/jobber-tokens.json"
}
}
}
}npm
TERMINAL
npm install @opsconduit/jobber-mcp
