jobber-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBBER_ACCESS_TOKEN | Yes | OAuth2 access token for Jobber API. Get one via the Jobber OAuth flow. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsA | List clients (homeowners/businesses you service) with their contact info. |
| list_jobsB | List jobs (work orders). Optional status filter — common values: |
| list_quotesB | List quotes with optional status filter. Common statuses: |
| list_invoicesB | List invoices with optional status filter. |
| health_checkA | Verify the access token is valid by listing 1 client. |
| create_clientB | Create a new client (homeowner / business). App-created clients are automatically tagged with your app's name in Jobber's Lead source field — this is the only way leads enter the system via your integration. |
| add_client_noteB | Add a note to a client's record. Useful after a phone call or site visit. |
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 tool targets a distinct resource or action: client creation, note addition, health check, and lists for clients, invoices, jobs, and quotes. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_clients, create_client, add_client_note), with health_check being the only slight deviation but still clear.
7 tools is a reasonable size for a focused CRM server, covering basic operations without being overwhelming. It could grow slightly but is well-scoped.
The server lacks update, delete, and creation tools for jobs, invoices, and quotes, limiting full lifecycle management. Only client creation and listing are covered.