BackCrew Jobber MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_clientsA | List clients (customers), Relay-paginated. Maps to the GraphQL |
| get_clientA | Get a single client by ID. Maps to the GraphQL |
| list_jobsB | List jobs, Relay-paginated. Maps to the GraphQL |
| get_jobA | Get a single job by ID. Maps to the GraphQL |
| list_invoicesA | List invoices, Relay-paginated. Maps to the GraphQL |
| get_invoiceB | Get a single invoice by ID. Maps to the GraphQL |
| list_quotesA | List quotes/estimates, Relay-paginated. Maps to the GraphQL |
| get_quoteA | Get a single quote by ID. Maps to the GraphQL |
| list_propertiesA | List service properties (addresses), Relay-paginated. Maps to the GraphQL |
| get_propertyA | Get a single property by ID. Maps to the GraphQL |
| list_usersA | List users (team members) on the account, Relay-paginated. Maps to the GraphQL |
| get_accountA | Get the connected Jobber account's basic info. Maps to the GraphQL |
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 12 tools
Each tool targets a distinct resource (clients, account, jobs, invoices, quotes, properties, users) with either list or get operations. There is no ambiguity between tools.
All tools follow a consistent verb_noun pattern (e.g., list_clients, get_job, get_invoice). No deviations or mixed conventions.
With 12 tools, the set is well-scoped for a read-only server focused on core entities of a field service management platform. Not too many, not too few.
The tools cover read operations for all major entities (clients, jobs, invoices, quotes, properties, users). Missing write operations and potentially entities like visits, but the read-only scope is clearly stated and consistently implemented.