How to
How to connect Claude to Jobber
Jobber runs quotes, jobs, scheduling, invoicing, and client records for home and commercial service businesses. It ships no official Claude connector, so acting inside Jobber means a custom MCP connector on its GraphQL API.
Connect Claude to Jobber with a custom MCP connector, since Jobber does not ship an official Claude or MCP connector and access runs through its GraphQL API. The connector authenticates with OAuth as your own account, reads clients, quotes, jobs, and invoices, and adds scoped write actions like drafting quotes and creating jobs, with sending gated behind your approval.
Key takeaways
- Jobber has no official Claude or MCP connector today, so read and write access is custom-built on its GraphQL API with OAuth.
- A custom connector lets Claude draft a quote with line items and pricing, create a job and schedule a visit from an approved quote, and prepare an invoice from a completed job.
- Sending a quote or invoice to a client is a separate, gated action that only runs after you confirm it.
- The connector inherits the scopes and permissions of the authorizing account, so Claude never has more access to your Jobber data than your own login.
Does Jobber have an official Claude connector?
No. Jobber does not ship an official Claude or MCP connector, and access to your data runs through its GraphQL API. A custom Jobber connector can read clients, quotes, jobs, and invoices and add scoped write actions like drafting a quote or creating a job, with confirmation on outbound steps.
So the quoting, scheduling, and billing loop that fills a service business's day stays manual unless you build. The GraphQL API is capable; what is missing is the connector layer that turns it into tools Claude can use in conversation.
A custom build closes that gap on your terms: which records Claude reads, which write actions it can stage, and which steps, like anything that reaches a client, always wait for you.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom Jobber connector for Claude?
A custom Jobber connector is a small MCP server that authenticates to Jobber's API with OAuth and the narrowest scopes the work needs. Read tools for clients, quotes, and jobs are kept separate from write tools, and outbound or destructive actions like sending or deleting require your confirmation.
The path from request to working connector:
- 1Describe the Jobber work Claude should handle: quoting, job creation, scheduling, client records, invoicing, and where the approval gates belong.
- 2We build a small MCP server with read tools (clients, quotes, jobs) separated from write tools (draft quote, create job, prepare invoice).
- 3You authenticate through OAuth as your own Jobber account, so Claude inherits that account's scopes and permissions and nothing more.
- 4Claude starts quoting and scheduling in conversation, and outbound or destructive steps like sending or deleting run only after you confirm them.
The server can run behind a firewall with IP allowlisting when needed, and you can scope it to a narrower set of actions if you prefer.
What can Claude do in Jobber with write access?
With full read-write access, Claude can draft a quote for a client with line items and pricing, create a job and schedule a visit from an approved quote, add or update client records including property and contact details, attach notes or follow-up reminders, and prepare an invoice from a completed job for your review.
The tool set maps to the quote-to-invoice loop you currently tab between screens for:
Draft a quote for a client with line items and pricingfrom a client request or an existing record.Create a job and schedule a visit from an approved quoteso won work turns into scheduled work immediately.Add or update a client record, including property and contact detailsto keep the file current.Attach notes or follow-up reminders to a job or clientso nothing slips between visits.Prepare an invoice from a completed job for your reviewbefore anything is sent.Find every open quote matching a filter and propose next stepswhen you want the pipeline worked, not just recorded.
That last one is where a connector earns its keep: Claude can sweep every open quote and come back with proposed follow-ups, which is a job no one gets around to by hand.
Will Claude send a quote or invoice to a client without my approval?
No. Sending and other outbound steps are separate, gated write actions. Claude can prepare the quote or invoice and assemble the line items, but it is only sent to the client after you approve it. You decide which actions run automatically and which require a confirmation step.
Most service businesses settle on the same shape: reads and notes flow freely, drafting and job creation run fast, and every client-facing send waits for a person. Destructive steps like deleting a record sit behind the same confirmation gate.
Claude only has your account's access
The connector authenticates through OAuth and inherits the scopes and permissions tied to the authorizing account. It never grants Claude more access to your Jobber data than that account already has, and you can scope it to a narrower set of actions if you prefer.
What does a Claude and Jobber workflow look like in practice?
A client request comes in, and in one conversation Claude drafts the quote with line items and pricing, stages it for your approval, then, once the quote is approved, creates the job and schedules the visit, attaches follow-up reminders, and later prepares the invoice from the completed job for your review.
The through-line is that Jobber remains the system of record at every step. Claude is not keeping a separate list of quotes and visits; it is reading and writing the same records your team already works from, and every client-facing or destructive step pauses for the person who owns the relationship.
That is the difference between an assistant that talks about your business and one that works inside it.