Project Delivery integration · Beta
Evaluate the Jobber MCP server for your MSP stack.
The Stackyapper Jobber connection is available for evaluation. Beta apps may change and should begin with a small set of read-only tools.
What is the Stackyapper Jobber MCP integration?
The Stackyapper Jobber integration lets compatible AI clients use approved Jobber tools without receiving the provider credential.
What can the Jobber integration do?
Home-service operations — clients, jobs, requests, quotes, and invoices. An admin configures the OAuth app, then authorizes one Jobber account for this workspace.
Available tools depend on the provider account, workspace settings, and the signed-in user’s permissions.
Who is the Jobber MCP integration for?
It is for MSP and customer teams that need approved Jobber context available to an AI assistant while keeping provider authorization inside the selected Stackyapper workspace.
What is the current support status?
| Status | Beta |
|---|---|
| App review | In review |
| What that means | Available for evaluation, may change, and should begin with read-only tools. |
| Catalog category | Project Delivery |
| Catalog audience | msp and customer |
| Credential handling | Each authorized user completes the Jobber OAuth flow; an administrator may need to configure the provider application for the workspace first. |
| Customer access | Customer access available when an administrator enables it |
Start in a test workspace with one read-only tool and a request for no more than five records.
What can an MSP use it for?
- Review approved Jobber context during a project delivery workflow.
- Ask an authorized AI client to summarize permitted Jobber results before a human decision.
- Use the Jobber connection alongside another permitted business system when the workflow needs that information.
Exact tools depend on provider authorization, credential ownership, workspace settings, and the signed-in user’s permissions.
What should I expect?
| Provider scope | Home-service operations — clients, jobs, requests, quotes, and invoices. An admin configures the OAuth app, then authorizes one Jobber account for this workspace. |
|---|---|
| Available tools | Compatible clients see only the tools available to the signed-in user in the selected workspace. |
| Write actions | If a write tool is available, Stackyapper applies its permissions and confirmation requirements before it runs. |
| API coverage | This page lists the capabilities Stackyapper currently supports, not every endpoint in the provider API. |
How is Jobber access controlled?
- An administrator configures Jobber for the intended Stackyapper workspace, and each authorized user connects their own provider identity or credential.
- The administrator grants available tools to specific workspaces, groups, or people.
- Stackyapper resolves the connection within the current credential and tenant scope.
- Stackyapper checks permissions and safety controls again before every request.
- Actions that require confirmation do not execute until the exact request is confirmed.
Does Jobber send its API credential to Claude or ChatGPT?
No. Stackyapper keeps the encrypted provider credential secure and does not send it to the AI client.
How do I evaluate the Jobber beta?
- Create or select a non-production Stackyapper workspace.
- Find Jobber in the app catalog and request beta access if it is not enabled.
- Use the provider authorization described above with the narrowest practical permissions.
- Grant only the read-only tool needed for the evaluation.
- Request no more than five records, confirm the result in Audit, and expand access only when the test succeeds.
Support boundaries
- Stackyapper does not claim that every endpoint in the Jobber API is exposed.
- Provider plan, account configuration, API scopes, and upstream availability can limit results.
- Administrators are responsible for correct provider permissions and user grants.
- Support status and available tools can change as provider capabilities evolve.
Jobber MCP questions
Is there a Jobber MCP server?
Stackyapper has a beta Jobber MCP connection available for evaluation. Beta apps may change and should begin with a small set of read-only tools.
Can I connect Jobber to Claude or ChatGPT?
Stackyapper has a beta Jobber connection for compatible MCP clients. It is available for evaluation and may change. Exact access depends on provider authorization and Stackyapper workspace permissions.
Does Stackyapper expose every Jobber API endpoint?
No. This page lists the Jobber capabilities Stackyapper currently supports.
Does Jobber send its credential to the AI client?
No. Stackyapper keeps the encrypted Jobber credential secure and does not send it to the AI client.
Related Stackyapper resources
- How the Stackyapper MCP server works for MSPs
- MCP security, credential, and access-control model
- Connect ChatGPT, Claude, Claude Code, or Codex to Stackyapper
- Complete Stackyapper app catalog
- Forge MCP access (available)
- GitHub MCP access (beta)
- Jira Cloud MCP access (beta)
Stackyapper is an independent product. Provider availability and API capabilities can change.