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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/jobber-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server