
Jobber Mcp Server
io.github.friendlygeorgePublished by GitHub account friendlygeorgev1.0.0Updated Oct 24, 2026
MCP server for Jobber (home services SaaS) — exposes tools for clients, jobs, invoices, and quote...
Overview
An MCP server that connects an AI assistant to Jobber field-service data, letting it list clients, jobs and invoices and create quotes.
- What you can do
- List and look up clients, including contact details and recent jobs, with search and lead filters and a result limit. Retrieve full job details such as status, assignees, schedule and line items. List and read invoices filtered by client or status, with line items and payment status. Create a new quote for a client with line items.
- When to use it
- Useful for home-services teams already on Jobber who want to ask about clients, jobs and overdue invoices, or draft quotes in natural language instead of opening the Jobber dashboard. Mock mode lets you try it without a Jobber account.
- Requirements
- Runs locally via npx, so Node.js 18+ and npm are needed. Real use requires a Jobber account with API access and OAuth2 credentials supplied through the JOBBER_ACCESS_TOKEN, JOBBER_CLIENT_ID and JOBBER_CLIENT_SECRET environment variables. Setting JOBBER_MOCK_MODE=true uses fake data with no Jobber account.
Installation
In SourceWeft
- Open Jobber Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Jobber MCP Server
An MCP server for Jobber — connect any MCP-compatible client to your Jobber field-service data.
[npm version] [npm downloads] [License: MIT] [MCP Compatible] [TypeScript] [Claude Desktop] [Cursor]
What is this?
An MCP (Model Context Protocol) server that gives AI assistants and agents access to your Jobber data — clients, jobs, invoices, and quotes — through a clean, typed API.
Use it with Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible client to ask questions about your business data, create quotes, and manage field-service operations through natural language.
Why use this?
- 6 built-in tools — clients, jobs, invoices, and quotes in one server
- Mock mode — try it instantly with fake data, no Jobber account needed
- Natural language queries — "show me overdue invoices" just works
- Quote creation — create and send quotes without opening Jobber
- Client lookup — find client details, contact info, and job history
- Works with every MCP client — Claude Desktop, Cursor, Windsurf, Cline, and more
Quick Start
Add to your MCP client config (e.g. claude_desktop_config.json):
Or try with mock data first (no Jobber account needed):
Get API credentials at Jobber Developer Portal.
Use it
Ask your AI assistant things like:
- "List all my clients"
- "Show me the details for client-101"
- "What jobs are assigned to Alex Reyes?"
- "Create a quote for Northwind Roofing: 2 hours of emergency repair at $150/hr"
- "Which invoices are overdue?"
Tools
Use Cases
Daily Operations Check
"Show me today's jobs and any overdue invoices" — start your morning with a full picture of what needs attention. No more logging into Jobber's dashboard first thing.
Client Research
"What's the history with Northwind Roofing?" — pull up client details, recent jobs, and outstanding invoices before a site visit or sales call.
Quote Generation
"Create a quote for Mrs. Chen: gutter cleaning, 1 hour, $120" — draft and send quotes from the field without switching apps.
Invoicing Audit
"Show me all unpaid invoices over $500" — find overdue payments and follow up without manually filtering through Jobber's invoice list.
Field Service Reporting
"Summarize Alex Reyes' jobs this week" — generate performance summaries for team meetings or payroll without pulling reports manually.
Security
- OAuth credentials required — Jobber API uses OAuth2. Credentials are passed via environment variables, never logged.
- No local file access — does not read or write any files on your machine (unless you enable mock mode).
- No shell access — does not execute commands or spawn processes.
- Mock mode safe —
JOBBER_MOCK_MODE=trueuses fake data with no API calls to Jobber. - Open source — MIT licensed. Inspect the code at GitHub.
Troubleshooting
"Authentication failed" errors
Verify your JOBBER_CLIENT_ID, JOBBER_CLIENT_SECRET, and JOBBER_ACCESS_TOKEN are correct. Tokens expire — check the Jobber Developer Portal for fresh credentials.
"No data found" in mock mode
Make sure JOBBER_MOCK_MODE=true is set in your environment or MCP config. Mock mode creates sample clients, jobs, and invoices automatically.
Server won't start
Make sure Node.js 18+ is installed: node --version. If using npx, ensure npm is up to date: npm install -g npm@latest.
MCP client can't connect
Verify the config path is correct. Claude Desktop uses ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Restart the client after config changes.
Slow responses
Jobber's GraphQL API has ~200-500ms latency. Complex queries (e.g., listing clients with full job history) may take longer. Use list_clients with a limit parameter to speed up initial queries.
Jobber API Setup
To use with your real Jobber account:
- Go to Jobber Developer Portal
- Create an app and get your
client_idandclient_secret - Complete OAuth flow to get an
access_token - Add credentials to
.envor MCP client config
Requirements
- Node.js 18+
- A Jobber account with API access, or use
JOBBER_MOCK_MODE=truefor testing
Development
License
MIT
Source: README.md at commit 87996dc
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts