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.
In Elaichi
Connect Jobber once
-
Open Connections, choose Add connection, and pick Jobber.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Jobber to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Jobber to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Jobber to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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?”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch clients
Jobber
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.
Put Jobber in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.