Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Jobber to Claude Code

Make Claude draft quotes, create jobs, and prepare invoices in Jobber. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Jobber to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Jobber, you add a Jobber MCP server: a small hosted service that exposes Jobber's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Jobber account. No API keys pasted into config files.

claude mcp add --transport http jobber https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Jobber once connected?

Full read-write Jobber access lets Claude draft a quote from a client request, create a job and schedule a visit, add line items, attach notes to a client record, and prepare an invoice for your approval. The quoting and scheduling that used to mean tabbing between screens happen where the work already lives.

  • 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 a client record, including property and contact details
  • Attach notes or follow-up reminders to a job or client
  • Prepare an invoice from a completed job for your review
  • Find every open quote matching a filter and propose next steps

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Jobber access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Jobber API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Jobber changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Jobber connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Jobber connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Jobber account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Jobber's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Jobber?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Jobber account it signs in with. Revoking access is one click in Jobber.

More on the Jobber connector

Jobber connector for claude.aiServiceTitan + Claude CodeQuickBooks Online + Claude CodeCustom CRM + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us