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 any page of a Jobber Client Hub and return its readable text. Use for detail pages (e.g. |
| 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 fetchproxy browser bridge 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
Each list tool targets a distinct resource (appointments, invoices, quotes, work requests), and the generic page reader, hub lister, and healthcheck are clearly separate utilities. No two tools overlap in purpose.
All tools share the jobber_ prefix and mostly follow verb_noun naming (list_, read_), but jobber_healthcheck deviates slightly from the verb_noun pattern. Overall the naming is predictable and consistent.
Seven tools is a tight, appropriate scope for a read-only Jobber Client Hub integration. Each tool covers a distinct need without redundancy, fitting well within the ideal 3-15 tool range.
The surface covers listing all four core resource types plus a generic page reader for details, hub configuration, and diagnostics. Missing structured get-by-id tools are worked around by jobber_read_page, so there are no critical gaps, though dedicated detail endpoints would be marginally more complete.