OpsConduit Jobber MCP
This is a read-only connector for Jobber's field service platform, built for customer-hosted deployments. It handles OAuth setup locally, stores tokens on your machine, and exposes six GraphQL tools to surface operational gaps: overdue invoices, unscheduled jobs, stale estimates, and customer follow-up opportunities. All mutations are blocked before sending. You'd reach for this if you run a trade or service business on Jobber and want to ask Claude which work is slipping through the cracks without giving a third party custody of your credentials or letting an agent write back into your system.
- tools
- 6
- auth
- Secret needed
- transport
- STDIO
- env vars
- 3
- last updated
- May 18, 2026
Tools
6 toolsPublic tool metadata for what this MCP can expose to an agent.
jobber_auth_urlcreate the one-time Jobber OAuth authorization link for a customer-hosted install.
create the one-time Jobber OAuth authorization link for a customer-hosted install.
No parameter schema in public metadata yet.
jobber_exchange_codeexchange the redirected OAuth code and store tokens locally without exposing them in chat.
exchange the redirected OAuth code and store tokens locally without exposing them in chat.
No parameter schema in public metadata yet.
jobber_refresh_tokenrefresh the stored access token for continued read-only reporting.
refresh the stored access token for continued read-only reporting.
No parameter schema in public metadata yet.
jobber_accountvalidate the connected account before running operational queries.
validate the connected account before running operational queries.
No parameter schema in public metadata yet.
jobber_clients_samplevalidate read access with a capped client sample.
validate read access with a capped client sample.
No parameter schema in public metadata yet.
jobber_graphql_readrun read-only Jobber GraphQL for owner reports; mutations are blocked before sending.
run read-only Jobber GraphQL for owner reports; mutations are blocked before sending.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageConfiguration
JOBBER_CLIENT_ID*Jobber developer app client id for customer-owned OAuth setup.
JOBBER_CLIENT_SECRET*secretJobber developer app client secret. Keep local; do not email or publish.
JOBBER_REDIRECT_URIOAuth redirect URI, usually http://localhost:3333/oauth/callback for local setup.
Readme
OpsConduit Jobber MCP
Read-only MCP connector for Jobber field-service operations.
OpsConduit helps owners and operators ask practical questions about the tools that run their business. This first connector is for Jobber and is designed to stay read-only by default.
Plain buyer-facing overview: docs/index.md. Common buyer questions are answered in docs/faq.md. Example owner/operator prompts are in docs/operator-prompts.md. First paid-install deliverable shape: docs/first-report.md.
What It Should Answer
- Which estimates need follow-up?
- Which invoices are overdue?
- Which jobs are unscheduled, stale, or blocked?
- Which customers have not had activity recently?
- What work needs attention this week?
- Where is operational follow-up leaking revenue?
More buyer-facing examples are in docs/use-cases.md.
A fictional sample output is available in docs/demo-output.md, or run:
npm run demo
The paid pilot handoff format is documented in docs/pilot-deliverable-template.md.
Product Posture
Details
- Repository
- github.com/opsconduit/jobber-mcp
- Package
@opsconduit/jobber-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active