Claude + Jobber: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Jobber connector and no Jobber-built MCP server. Jobber isn’t in Anthropic’s connectors directory, and Jobber’s developer docs publish a GraphQL API and webhooks but no MCP endpoint. What exists on the Claude side are a handful of tiny community MCP servers (the biggest has 3 GitHub stars) and middleware like Zapier MCP or Pipedream MCP. And even once you wire one up, every Claude MCP setup shares the same limit: it only works inside a conversation you start. Nothing watches your Jobber account, nothing fires when a quote gets approved, nothing runs while you’re on a job site.
Here’s exactly what’s available today, how to connect it, where the limits bite, and what to use if you want Jobber work that runs on its own.
What Jobber ships — and what it doesn’t
Jobber’s Developer Center gives you a real, capable API — it’s the best API of the field-service tools. But it’s built for app developers, not for a one-click Claude hookup:
- GraphQL API (no REST) — a free, self-serve developer account, an app you create in the Developer Center, and OAuth 2.0 auth. You test queries in GraphiQL.
- Webhooks — real-time events configured at the application level, covering the objects that matter: clients, requests, quotes, jobs, visits, invoices, timesheets, expenses.
- Broad CRUD coverage — create and update clients, quotes, jobs, and invoices through mutations.
What you won’t find is anything Claude-native. Jobber’s AI story is entirely its own in-product tooling — Jobber Copilot (the business-coach chat launched in late 2024) and the AI Receptionist (launched Aug 2025, answers calls and texts and books jobs). Those are useful, but they’re internal Jobber features. Neither is an MCP server, and neither connects to Claude.
How you’d actually connect Claude to Jobber today
There’s no supported first-party path, so you’re choosing among unofficial ones:
- Middleware MCP — Zapier MCP or Pipedream MCP expose Jobber actions to Claude as a custom MCP server. This is the most practical “connect Claude to Jobber today” route because you don’t maintain any code.
- A community MCP server — a few exist on GitHub, all very small (the largest is around 3 stars, and one prolific author auto-generates near-identical “[app]-mcp-2026-complete” repos, so vet anything before handing it credentials).
- Your own app — register an app in Jobber’s Developer Center, get OAuth 2.0 credentials, and point a local MCP server at the GraphQL API.
Any of these adds Jobber as a custom MCP connector. Remote custom connectors on claude.ai require a paid Claude plan; local servers run through Claude Desktop or Claude Code.
The limits that actually matter
Wire it up however you like — the shape stays “an assistant you operate,” not “an agent that runs.” Three limits define it:
- No triggers, no monitoring. Jobber’s webhooks can fire on “quote approved” or “invoice paid,” but Claude’s MCP tools only run inside a conversation you start. There’s nothing to catch that webhook and act — no “when a quote is approved, schedule the visit and text the client.” You have to be in the chat, prompting.
- Conversation-only. Claude looks up a client or drafts a quote when you ask; it doesn’t sit on your account watching for new requests and following up. Close the chat and nothing continues.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on, event-driven dispatch agent.
So Claude is good for “pull up this client’s job history and draft a follow-up” and not built for “chase every approved quote the moment it lands.”
If you want Jobber work that runs on its own: Carly
The moment you want something to happen around Jobber without you in the chat — text a client the instant their quote is approved, follow up on an overdue invoice, confirm tomorrow’s visits every evening — you’ve crossed past what Claude’s MCP setup is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on Jobber events, 24/7, in the cloud — when a quote is approved, a job is booked, or an invoice goes overdue, Carly acts; your laptop doesn’t need to be awake.
- Runs the whole follow-up — read the job, draft the message, send it, and update the record, all in one flow off a single event.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, updates your CRM, and records meetings.
- Builds the workflow for you — tell it “I’d like to set up a system that texts a client when their quote is approved and books the visit” in plain English; it interviews you, then builds it with you. No prompt engineering.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations. Carly natively integrates with Jobber.
Claude vs Carly
| Claude (community/middleware MCP) | Carly | |
|---|---|---|
| Look up clients & jobs | Yes | Yes |
| Draft quotes & messages | Yes | Yes |
| Acts on Jobber triggers / events | No | Yes |
| Chases approved quotes on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Official Jobber support | No (community/middleware) | Yes (native) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with a community MCP is a Jobber lookup inside a chat. Carly is a teammate that acts on Jobber events as they happen.
Frequently Asked Questions
Does Claude work with Jobber?
Not officially. There’s no Claude Jobber connector in Anthropic’s directory and no Jobber-built MCP server. You can connect the two through middleware (Zapier MCP or Pipedream MCP) or a small community MCP server against Jobber’s GraphQL API — but these are unofficial, and like all MCP setups they only work inside a conversation you start.
Isn’t Jobber Copilot a Claude integration?
No. Jobber Copilot and the AI Receptionist are Jobber’s own in-product AI features. They’re not MCP servers and they don’t connect to your Claude account — they run inside Jobber.
How do I connect Claude to Jobber?
The practical route is middleware MCP: connect Zapier MCP or Pipedream MCP and add it to Claude as a custom MCP connector (paid plan for remote connectors). Developers can instead register an app in Jobber’s Developer Center, get OAuth 2.0 credentials, and run a local MCP server against the GraphQL API.
What if I want Jobber to act on its own — text clients, chase invoices?
That’s outside what Claude’s MCP setup does; it responds inside a chat and doesn’t act on Jobber’s webhooks. Carly fires on Jobber events 24/7 in the cloud and can message clients, chase invoices, update records, and send email. AI agents start at $35/month.
More: Claude connectors · Claude + ServiceTitan · Claude + Housecall Pro · Can Claude send emails · Claude vs Carly · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
