Skip to content

CRM

Jobber MCP connector

The Jobber connector brings your Jobber clients, work requests and jobs into Claude, ChatGPT, Cursor and any MCP client, so your office team can look up, create and update records in plain language while every action stays within their own Jobber access.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Jobber to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Jobber once

  1. Open Connections, choose Add connection, and pick Jobber.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Jobber app, then approve. Jobber needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

jobber
Jobber
Affinity
Attio
Clazar
Clio Manage
Close
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Jobber MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Jobber MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Jobber MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Jobber to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Jobber through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Office

    Catch a client record up after a call

    A customer rings to change their phone number or add a gate code, and the office manager asks the agent to update the Jobber client on the spot instead of switching windows mid-conversation.

  • Dispatch

    See what jobs are on today

    Ask which Jobber jobs are scheduled, who they are for and where, and get a plain answer before the first truck leaves the yard.

  • Sales

    Log a new work request from a phone call

    When a homeowner calls asking for a quote on a fence repair, the salesperson describes the job and the agent creates the Jobber request and the new client in one go.

  • Sales

    Follow up on open requests

    Pull every Jobber request that has been sitting untouched for a week, then update each one with notes from the follow-up call.

  • Operations

    Check a job before heading out

    A crew lead asks for the details of one Jobber job, the client attached to it and any notes on the request that started it, all in one answer.

  • Owner

    Tidy up the client list

    Count how many Jobber clients are on the books, find the ones who have not had a job in years, and archive them so the list reflects the customers you actually serve.

Try asking

  • “Which Jobber requests came in this week and from whom?”
  • “Create a Jobber client for the Harlow Street property.”
  • “How many open Jobber jobs sit with each team?”

See all 15 Jobber tools below

Compare

Elaichi vs Zapier MCP vs Composio for Jobber

All three can connect Jobber to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Jobber, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Jobber tools Allow or restrict single Jobber tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Jobber call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Jobber tools for your AI agents

15 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jobber, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Jobber gets you

6 screens from the product, each doing one job for your Jobber account.

The agent

Ask about Jobber jobs in plain language.

Answers come from live Jobber clients, requests and jobs, not stale exports.

  • clients
  • requests
  • jobs
  • accounts

Ask Elaichi to work across your apps.

Which Jobber requests came in this week and from whom?

Create a Jobber client for the Harlow Street property.

How many open Jobber jobs sit with each team?

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Jobber here.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

15 Jobber tools ready without custom code.

Clients, requests, jobs and account calls are listed with methods and resources.

  • List all Jobber account
  • List all Jobber clients
  • Get single Jobber client by ID
  • Jobber clients count
ElaichiTools
Tool Action Description
List all Jobber account List Get information about the authorized Jobber account. Returns: id, name, countryCode, phone. No required parameters — the account is determined by the access token.
List all Jobber clients List List Jobber clients. Returns: id, name, isLead, leadSource, email, phone, balance, tags, billingAddress, and totalCount rollups for jobs, requests, quotes and invoices. Filter with the filter param, e.g. {"isLead": true} for leads only. A client whose jobs.totalCount is 0 has never had work booked.
Get single Jobber client by ID Get Get a single Jobber client by id. Returns: id, name, isLead, leadSource, email, phone, balance, tags, billingAddress, and jobs/requests/quotes/invoices totalCount. Required: id.
Jobber clients count Action Count Jobber clients matching a filter, without fetching the records. Returns: totalCount. Use filter {"isLead": true} to count how many leads have come through, optionally narrowed by createdAt.
Create a Jobber client Create Create a Jobber client, e.g. to lodge a qualifying lead. Returns the created client; new clients start with isLead true. Accepts scalar fields only — to set emails, phones, addresses or custom fields, use the graphql tool with the clientCreate mutation.

Toolboxes

Every team gets its own Jobber toolbox.

Scope a toolbox to dispatch, sales or finance and hand it over.

  • Sales
  • Dispatch
  • Field crews
  • Customer support
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Jobber · requests and quotes

Jobber starter 18 Mar 4, 2026

Dispatch toolbox

Jobber · jobs and scheduling

— 9 Mar 2, 2026

Field crews toolbox

Jobber · assigned jobs

— 24 Feb 27, 2026

Customer support toolbox

Jobber · clients and requests

Jobber starter 6 Feb 19, 2026

Finance toolbox

Jobber · jobs and account

— 31 Jan 30, 2026

Operations toolbox

Jobber · job volume and client records

— 12 Jan 22, 2026

Shared connections

Teammates use Jobber without seeing credentials.

Each connection shows who connected it and how many teams and members share it.

  • Sales North
  • Dispatch
  • Field crews
  • Support
ElaichiConnections
Connection Scope Status Access
JO

Jobber (Sales North)

Connected by Emily Carter

Personal • Active 1 team · 6 members
JO

Jobber (Dispatch)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
JO

Jobber (Field crews)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
JO

Jobber (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
JO

Jobber (Finance)

Connected by Ryan Hayes

Personal • Active Not shared
JO

Jobber (Operations)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Jobber call is written down.

When, who, what happened, type and resource for each request against Jobber.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Jobber Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Jobber Clients Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Jobber Clients List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Jobber jobs into action.

Six steps fetch jobs, group them, draft a digest, get approval, post back.

Jobber digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch clients

    Jobber

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Jobber

    Queued

Collections and dashboards

Jobber health computed, not asked for.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

Jobber health

Refreshed 4 minutes ago · every 15 minutes · from the clients collection

Live

Clients

1,284 ↓ 12%

Requests

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Clients created

Last 14 days

By team

Share of activity

Sales North 34%

Dispatch 27%

Field crews 21%

Support 18%

FAQ

Frequently asked questions

How do I connect Jobber to Claude?

Connect Jobber in Elaichi first. Jobber requires an OAuth application registered inside your own Jobber account, so one person creates that once and enters its client ID and secret into Elaichi; after that, everyone signs in to Jobber through the normal Jobber login screen and nobody handles those values again. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in, and Jobber is ready.

Does Jobber work with ChatGPT and Cursor as well as Claude?

Yes. Once Jobber is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi agent. You connect Jobber once and use it from whichever client you happen to be working in.

What can an AI agent actually do with my Jobber data?

With Jobber connected, an agent can look up a client, create a new one, update their details or archive them when they are no longer a customer. It can list and count work requests, create a new request from a phone call and update an existing one, and it can list your jobs and pull up the details of any single job. It can also answer questions about your Jobber account itself.

Does connecting Jobber give the AI access to every client and job in my account?

No. Every request to Jobber runs as the person who signed in, so the agent sees exactly the clients, requests and jobs that person can already see in Jobber, and nothing more. Elaichi can narrow that further, for example to read-only, but it can never grant access that Jobber itself has not given the user.

Can my team share one Jobber connection?

Yes. One person connects Jobber in Elaichi and shares the connection with a team, and nobody else on the team ever handles a client ID, secret or password. Each teammate still signs in as themselves, so when someone updates a Jobber client or creates a request, the audit log records their name, not the name of whoever set up the connection.

Can I stop an agent from deleting or changing things in Jobber?

Yes. Restrictions in Elaichi work per action, so you can allow reading Jobber clients, requests and jobs while blocking creating, updating or archiving them. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

What happens to a Jobber connection when someone leaves?

Offboarding a person in Elaichi ends their access to Jobber through every client at once, including Claude, ChatGPT and Cursor. If they were using a shared Jobber connection, it keeps working for everyone else on the team. If you want to remove Jobber entirely, disconnecting it once in Elaichi takes it out of every client at the same time.

Does the Jobber MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Jobber is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Jobber?

Yes. Both let Claude, ChatGPT or Cursor use Jobber. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Jobber call.

How is Elaichi different from Composio for Jobber?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Jobber: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Jobber in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.