[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Jobber API and MCP server

> Yes, Jobber has a GraphQL API in its Developer Center (checked 14 Oct 2026), but you cannot use it without registering an app. Each Jobber account authorizes your app with OAuth 2.0 and tokens must be refreshed. Jobber reviews an app before it reaches the App Store, and an app in Draft state loses API access if it connects to more than 5 paying Jobber accounts. Jobber has no official MCP server.

Field service management software for home service businesses: clients, requests, quotes, jobs, scheduling, invoices and payments in one account.

## What is the Jobber API?

Cotlet's Jobber API exposes 14 endpoints for your own Jobber account: list clients, get client, list quotes, get quote, list jobs, list invoices, get invoice, create client, create quote, send quote, convert quote to job, create invoice, send invoice and record payment. The list_clients endpoint returns clients in your Jobber account with name, contact details and open balance, newest first. Each endpoint takes simple JSON inputs like client_id, limit or cursor and works both as an operation of the jobber_read or jobber_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-23

Yes, Jobber has a GraphQL API in its Developer Center (checked 14 Oct 2026), but you cannot use it without registering an app. Cotlet is a hosted MCP server and REST API for Jobber with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Jobber have an official API?

Yes, Jobber has a GraphQL API in its Developer Center (checked 14 Oct 2026), but you cannot use it without registering an app. Each Jobber account authorizes your app with OAuth 2.0 and tokens must be refreshed. Jobber reviews an app before it reaches the App Store, and an app in Draft state loses API access if it connects to more than 5 paying Jobber accounts. Jobber has no official MCP server.

| Task | Jobber official | Cotlet |
|---|---|---|
| List and read clients | Yes: GraphQL clients query, paginated with first or last | Yes |
| Create a client | Yes: clientCreate mutation; Zapier also has Create Client | Yes |
| List and read quotes | Partly: Zapier has quote triggers; query fields not confirmed in docs we could open | Yes |
| Create a quote | Partly: Zapier has Create Quote; no action to send it | Yes |
| Convert a quote to a job | Partly: Zapier has Create Job but no convert action | Yes |
| List unpaid invoices | Partly: Zapier has invoice triggers only; query fields not confirmed in docs we could open | Yes |
| Create and send an invoice | Partly: Zapier cannot create or send invoices; mutations not confirmed in docs we could open | Yes |
| Record a payment | Partly: Not confirmed in docs we could open | Yes |

Sources: [Jobber Developer Center: App review process](https://developer.getjobber.com/docs/publishing_your_app/app_review_process), [Jobber Developer Center: API queries and mutations](https://developer.getjobber.com/docs/using_jobbers_api/api_queries_and_mutations/), [Jobber Help: Developer Center](https://help.getjobber.com/en/articles/developer-center/), [Zapier Help: Get started with Jobber on Zapier](https://help.zapier.com/hc/en-us/articles/40859679162381-How-to-get-started-with-Jobber-on-Zapier)

## For AI agents

```text
Yes, Jobber has a GraphQL API in its Developer Center (checked 14 Oct 2026), but you cannot use it without registering an app. Each Jobber account authorizes your app with OAuth 2.0 and tokens must be refreshed. Jobber reviews an app before it reaches the App Store, and an app in Draft state loses API access if it connects to more than 5 paying Jobber accounts. Jobber has no official MCP server.
Cotlet provides a hosted MCP server and REST API for Jobber: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=jobber, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    jobber_read, jobber_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/jobber, each operation at its own route, e.g. POST /api/v1/jobber/invoices/{invoice_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_clients, get_client, list_quotes, get_quote, list_jobs, list_invoices, get_invoice, create_client, create_quote, send_quote, convert_quote_to_job, create_invoice, send_invoice, record_payment
Confirm      send_quote, convert_quote_to_job, send_invoice, record_payment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/jobber-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=jobber, requests Jobber in the Cotlet console and creates an API key there.
2. The user signs in to Jobber once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Jobber for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Jobber server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Jobber MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Jobber in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Jobber only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Jobber login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Jobber's terms; Cotlet is not affiliated with Jobber.
```

## What can an AI agent do in Jobber?

Cotlet is best for Jobber owners and office managers who want an AI agent to chase invoices, follow up on quotes and turn approved quotes into jobs without running or fixing a server.

- **[Chase unpaid invoices](https://cotlet.dev/integrations/jobber-api-mcp-server/chase-unpaid-invoices.md)** (runs: weekly): "List my past due Jobber invoices over 14 days late. For each one, check the client's last payment, then send the invoice again by email with a short, friendly note. Skip anyone I flagged and tell me the total still owed." → `list_invoices`, `get_invoice`, `send_invoice`
- **[Convert approved quotes to jobs](https://cotlet.dev/integrations/jobber-api-mcp-server/convert-approved-quotes-to-jobs.md)** (runs: daily): "Find Jobber quotes that clients approved and have no job yet. Convert each to a job starting next Monday, assigned to Dan, and list anything with a deposit or a changes request for me." → `list_quotes`, `get_quote`, `convert_quote_to_job`
- **[Follow up on unanswered quotes](https://cotlet.dev/integrations/jobber-api-mcp-server/follow-up-on-unanswered-quotes.md)** (runs: weekly): "List my Jobber quotes still awaiting response for 5 days or more. For each one, check the client's last quote and send the quote again with a short note offering to answer questions." → `list_quotes`, `get_quote`, `send_quote`
- **Add new leads as clients with a draft quote** (runs: daily): "For each new lead in my inbox sheet, create a Jobber client if one does not exist, then draft a quote for the service they asked about. Do not send anything." → `list_clients`, `create_client`, `create_quote`
- **Invoice finished jobs** (runs: weekly): "List my Jobber jobs completed last week that have no invoice yet. Create a draft invoice for each and show me the totals before anything is sent." → `list_jobs`, `create_invoice`, `send_invoice`

## Can Jobber automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Jobber connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to chase unpaid invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/jobber/invoices. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/jobber/invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Jobber.

### list_clients

Clients in your Jobber account with name, contact details and open balance, newest first. Access: read. REST: `GET /api/v1/jobber/clients`. MCP: `jobber_read → list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Match on name, email or phone. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists clients newest first. Search by name, email or phone to find one client before creating a duplicate. Pages hold up to 50 clients; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_7731",
      "name": "Maria Santos",
      "email": "maria@example.com",
      "phone": "+1 555 0100",
      "balance": 480,
      "currency": "USD"
    }
  ],
  "next_cursor": null
}
```

### get_client

One client with properties, recent quotes, jobs and invoices. Access: read. REST: `GET /api/v1/jobber/clients/{client_id}`. MCP: `jobber_read → get_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |

Returns one client with the service properties on file and the latest quotes, jobs and invoices, each with its status. Use it to see a client's history before writing to them.

Example response:

```json
{
  "client_id": "cl_7731",
  "name": "Maria Santos",
  "properties": [
    "12 Oak Lane"
  ],
  "quotes": [
    {
      "quote_id": "q_5521",
      "number": "Q-5521",
      "status": "approved",
      "total": 480
    }
  ],
  "jobs": [
    {
      "job_id": "job_3290",
      "title": "Gutter cleaning",
      "status": "completed"
    }
  ],
  "invoices": [
    {
      "invoice_id": "inv_20418",
      "number": 1042,
      "status": "past_due",
      "balance": 480
    }
  ]
}
```

### list_quotes

Quotes with client, status, total and sent date, newest first. Access: read. REST: `GET /api/v1/jobber/quotes`. MCP: `jobber_read → list_quotes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, awaiting_response, changes_requested, approved or converted. Default: all. |
| `client_id` | string | no | Only quotes for this client. |
| `sent_before` | date | no | Only quotes sent before this date. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists quotes newest first. Status is one of draft, awaiting_response, changes_requested, approved or converted, the same statuses Jobber shows. Filter by client or by sent date to find quotes that went cold. Pages hold up to 50 quotes.

Example response:

```json
{
  "quotes": [
    {
      "quote_id": "q_5498",
      "number": "Q-5498",
      "client": "Anna Kim",
      "title": "Deck staining",
      "status": "awaiting_response",
      "total": 1200,
      "currency": "USD",
      "sent_at": "2026-10-07T09:12:00-04:00"
    }
  ],
  "next_cursor": null
}
```

### get_quote

One quote with line items, deposit, client message and status. Access: read. REST: `GET /api/v1/jobber/quotes/{quote_id}`. MCP: `jobber_read → get_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | string | yes | Quote ID from list_quotes. |

Returns the line items, the total, any required deposit and the message sent with the quote. Use it before converting or resending so the agent knows what the client was offered.

Example response:

```json
{
  "quote_id": "q_5521",
  "number": "Q-5521",
  "client": "Maria Santos",
  "status": "approved",
  "line_items": [
    {
      "name": "Gutter cleaning",
      "quantity": 1,
      "unit_price": 480
    }
  ],
  "deposit": null,
  "total": 480,
  "currency": "USD",
  "message": "Thanks for the visit, Maria."
}
```

### list_jobs

Jobs with client, title, status, dates and whether an invoice exists. Access: read. REST: `GET /api/v1/jobber/jobs`. MCP: `jobber_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Job status as shown in the Jobs list in Jobber. |
| `client_id` | string | no | Only jobs for this client. |
| `completed_since` | date | no | Only jobs completed on or after this date. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists jobs newest first with the dates Jobber shows and a flag for jobs that already have an invoice. Filter by client or by completion date to find work that is done and not yet billed.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "job_3290",
      "title": "Gutter cleaning",
      "client": "Maria Santos",
      "status": "completed",
      "completed_at": "2026-10-09",
      "invoiced": false
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Invoices with client, status, total, balance and due date. Access: read. REST: `GET /api/v1/jobber/invoices`. MCP: `jobber_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, awaiting_payment, past_due, paid, bad_debt or void. Default: all. |
| `client_id` | string | no | Only invoices for this client. |
| `due_before` | date | no | Only invoices due before this date. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists invoices newest first. Status is one of draft, awaiting_payment, past_due, paid, bad_debt or void, the statuses Jobber shows. Use past_due with due_before to build a list to chase. Pages hold up to 50 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_20418",
      "number": 1042,
      "client": "Maria Santos",
      "status": "past_due",
      "total": 480,
      "balance": 480,
      "currency": "USD",
      "due_date": "2026-09-28"
    }
  ],
  "next_cursor": null
}
```

### get_invoice

One invoice with line items, payments recorded and balance. Access: read. REST: `GET /api/v1/jobber/invoices/{invoice_id}`. MCP: `jobber_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |

Returns line items, total, every payment already recorded and the remaining balance. A partly paid invoice shows each payment, so a reminder asks for the balance and not the total.

Example response:

```json
{
  "invoice_id": "inv_20418",
  "number": 1042,
  "client": "Maria Santos",
  "status": "past_due",
  "line_items": [
    {
      "name": "Gutter cleaning",
      "quantity": 1,
      "unit_price": 480
    }
  ],
  "payments": [],
  "total": 480,
  "balance": 480,
  "currency": "USD",
  "due_date": "2026-09-28"
}
```

### create_client

Add a client with name, email, phone and a service address. Access: write. REST: `POST /api/v1/jobber/clients`. MCP: `jobber_write → create_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Client full name or company. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |
| `address` | string | no | Service address. |

Creates a client record in your Jobber account. It sends nothing to the client and reaches no one, so it runs without asking first. Search with list_clients before creating, because Jobber does not stop duplicates for you. A wrong record is removed in Jobber.

Example response:

```json
{
  "client_id": "cl_7802",
  "name": "Anna Kim",
  "created_at": "2026-10-14T09:00:00-04:00"
}
```

### create_quote

Create a draft quote for a client with line items. Access: write. REST: `POST /api/v1/jobber/clients/{client_id}/quotes`. MCP: `jobber_write → create_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |
| `title` | string | yes | Quote title. |
| `line_items` | array | yes | Items with name, quantity and unit_price. |
| `message` | string | no | Message shown to the client with the quote. |

Creates a quote in Draft status with the line items you give. Nothing is sent: Jobber keeps a draft until a quote is sent or marked Awaiting Response, so create_quote reaches no one and runs without asking first. Send it with send_quote.

Example response:

```json
{
  "quote_id": "q_5540",
  "number": "Q-5540",
  "status": "draft",
  "total": 1200,
  "currency": "USD"
}
```

### send_quote

Send a quote to the client by email or text, or send it again. Access: write, asks the user first. REST: `POST /api/v1/jobber/quotes/{quote_id}`. MCP: `jobber_write → send_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | string | yes | Quote ID from list_quotes. |
| `channel` | enum | yes | email or text. |
| `message` | string | no | Message sent with the quote. |

Sends the quote to the client by email or text message with your message, and sets a Draft quote to Awaiting Response. The client can approve it in client hub. Sending again repeats the message. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": "q_5498",
  "status": "awaiting_response",
  "sent_via": "email",
  "sent_at": "2026-10-14T09:05:00-04:00"
}
```

### convert_quote_to_job

Create a job from an approved quote with a start date and team. Access: write, asks the user first. REST: `POST /api/v1/jobber/quotes/{quote_id}/to-job/convert`. MCP: `jobber_write → convert_quote_to_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | string | yes | Quote ID from list_quotes. |
| `start_date` | date | no | First visit date. |
| `user_ids` | array | no | Team member IDs to assign. |

Creates a job from the quote's line items, as Convert to Job does in Jobber, and sets the quote to Converted. Optional start date and team members are set on the job. Quote edits made later do not reach the job. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "job_3377",
  "quote_id": "q_5521",
  "quote_status": "converted",
  "title": "Gutter cleaning",
  "start_date": "2026-10-19",
  "assigned_to": [
    "Dan"
  ]
}
```

### create_invoice

Create a draft invoice for a client or a completed job. Access: write. REST: `POST /api/v1/jobber/clients/{client_id}/invoices`. MCP: `jobber_write → create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients. |
| `job_id` | string | no | Invoice this job. Without it, pass line_items. |
| `line_items` | array | no | Items with name, quantity and unit_price. |

Creates an invoice in Draft status from a job or from line items. A draft is not sent and not due, so create_invoice reaches no one and runs without asking first. Check the total, then send it with send_invoice.

Example response:

```json
{
  "invoice_id": "inv_20431",
  "number": 1051,
  "status": "draft",
  "total": 480,
  "balance": 480,
  "currency": "USD"
}
```

### send_invoice

Send an invoice to the client by email or text, or send it again. Access: write, asks the user first. REST: `POST /api/v1/jobber/invoices/{invoice_id}`. MCP: `jobber_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |
| `channel` | enum | yes | email or text. |
| `message` | string | no | Message sent with the invoice. |

Sends the invoice by email or text message. The email links to the invoice in client hub, and text delivery is available in the US, Canada and the UK. A Draft invoice becomes Awaiting Payment. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_20418",
  "status": "past_due",
  "sent_via": "email",
  "sent_at": "2026-10-14T09:10:00-04:00"
}
```

### record_payment

Record a cash, check or other offline payment against an invoice. Access: write, asks the user first. REST: `POST /api/v1/jobber/invoices/{invoice_id}/payments`. MCP: `jobber_write → record_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |
| `amount` | number | yes | Amount received, in the invoice currency. |
| `method` | string | yes | How it was paid, e.g. cash or check. |
| `paid_on` | date | no | Date received. Default: today. |

Records an offline payment as Collect Payment does in Jobber. A payment that covers the full balance changes the invoice to Paid. It does not charge a card. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_20418",
  "payment_id": "pay_9912",
  "amount": 480,
  "status": "paid",
  "balance": 0
}
```

## How do I connect Jobber to Claude Code, Codex or Cursor?

Connecting Jobber takes three steps: sign up, sign in to Jobber once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Jobber to your agent.

1. **Create an account** Sign up and add Jobber in the console. Your API key is there too.

2. **Sign in to Jobber in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Jobber there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Jobber tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List my past due Jobber invoices over 14 days late. For each one, check the client's last payment, then send the invoice again by email with a short, friendly note. Skip anyone I flagged and tell me the total still owed.
```

### Call Jobber from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/jobber with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/jobber/invoices/inv_20418 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channel":"email","message":"Hi Maria, a quick reminder that invoice #1042 for $480.00 is past due. You can pay it online from the link below."}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "invoice_id": "inv_20418",
  "status": "past_due",
  "sent_via": "email",
  "sent_at": "2026-10-14T09:10:00-04:00"
}
```

## Why use Cotlet for Jobber?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Jobber yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Jobber changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Jobber to Cotlet?

Yes. You sign in to Jobber yourself, in your own Cloud Browser, and we never save your password. Your agents only get Jobber once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Jobber integration?**

No, Cotlet is independent of Jobber. Jobber's own API is open only to approved partners. Cotlet works through your own Jobber account, the way you use Jobber in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Jobber in your console: your agents lose access at once and you stay signed in. Signing out of Jobber in the browser works too, and Reset browser deletes the whole profile.

## Is there a Jobber MCP server on GitHub?

Yes. Community Jobber MCP servers exist on GitHub and npm, usually maintained by one person. They call the official GraphQL API, so you still register a Developer Center app, run the OAuth flow, host the server and fix it yourself when something changes. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Register a Jobber Developer Center app, run OAuth, install the server, add it to each MCP client | Sign up, sign in to Jobber once, add one MCP server or API key |
| When Jobber changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Jobber session | OAuth tokens in a file or env var on your computer | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You refresh or re-authorize the token yourself | Your Cloud Browser keeps you signed in; if Jobber logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n, Make, Zapier and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Jobber changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Jobber API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Jobber API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Jobber account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Jobber yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Jobber only after you enable it. When Jobber signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Jobber, sign out of Jobber in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Jobber's terms:** You use your own Jobber account and stay responsible for following Jobber's terms. Cotlet is independent and not affiliated with Jobber. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Jobber in the console and press Request access. Then you create your API key and connect Jobber there.

**Do I need to be technical?**

No. You sign in to Jobber once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Jobber to Cotlet?**

Yes. You sign in to Jobber yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Jobber once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Jobber sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Jobber cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Jobber's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Jobber sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Jobber login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Jobber offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a Jobber plan with API access or Zapier?**

No. Cotlet works in your own Jobber account and does not use the Zapier integration, which Jobber and Zapier list on the Connect and Grow plans (Zapier also lists Plus). Jobber's automatic quote and invoice follow-ups need the Connect plan, so the follow-up jobs here also help on lower plans.

**Why not register my own Jobber API app?**

You can. A custom integration for one client gets full API access without an App Store listing, but you build the OAuth flow and the GraphQL code yourself. Public apps go through Jobber review, and Draft apps are blocked above 5 paying accounts.

**Can my agent post or send messages in Jobber without asking me?**

No. Every call to send_quote, convert_quote_to_job, send_invoice or record_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_client, create_quote, create_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Jobber API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/jobber from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.