jobber-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBBER_HUBS | No | JSON array of {label, hubId} for several providers | |
| JOBBER_HUB_ID | No | The UUID from your hub URL (e.g., clienthub.getjobber.com/client_hubs/<UUID>/) | |
| JOBBER_WS_PORT | No | fetchproxy concentrator port (default: 37149) | 37149 |
| JOBBER_DEBUG_LOG | No | Bridge debug logging to stderr (set to any value to enable) | |
| JOBBER_HUB_LABEL | No | Name for the single hub (default: 'default') | default |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jobber_list_appointmentsA | Scheduled visits from a provider's Jobber Client Hub, grouped Today / Upcoming / Past. Each visit carries date, weekday, time, arrival window, location and confirmation state. |
| jobber_list_invoicesA | Invoices a provider has sent through Jobber. Each carries its number, subject, the list section it sits under ( |
| jobber_list_quotesA | Quotes a provider has sent through Jobber, with number, subject, section (approval state) and the raw metadata rows. Read-only — approving a quote is not possible through this server. |
| jobber_list_work_requestsA | Work requests you have raised with a provider through their Jobber Client Hub, with their current section (state) and metadata rows. Read-only. |
| jobber_read_pageA | Fetch a read page of a Jobber Client Hub — |
| jobber_list_hubsA | The provider hubs this server is configured for, by label, and which is the default. Each Jobber-using business shares its own hub; there is no combined view across providers. Never returns hub ids, which are credentials. Read-only. |
| jobber_healthcheckA | Checks the ContextMint Bridge browser connection and, if a hub is configured, fetches its appointments page. Reports which layer failed and what to do about it. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The five list_* tools each target a clearly distinct resource (invoices, appointments, hubs, quotes, work requests), and healthcheck is unique. The only overlap is jobber_read_page, which can also surface invoices/quotes/appointments pages, so an agent must decide between a list tool and the generic page reader, though the description frames it as a detail-page/fallback path.
Every tool uses the same jobber_ prefix with snake_case and a verb_noun shape (list_invoices, list_appointments, list_hubs, list_quotes, list_work_requests, read_page), with healthcheck the sole minor deviation as a single-word diagnostic.
Seven tools is well-scoped for a read-only Jobber Client Hub bridge: five list tools, one raw page reader, and one connectivity check, each earning its place with no redundancy.
The surface covers the read-only hub domain across invoices, quotes, appointments, work requests, hubs, and diagnostics, and read_page backstops anything not directly listed. Gaps are minor: no filtered/search listing and no dedicated single-item getter beyond read_page, and write operations are intentionally absent.