Jobber logo getjobber.com

Live

Jobber API and MCP server

Jobber's API is open only to apps you register and Jobber reviews, and its docs do not show sending quotes or invoices. Sign in to Jobber once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Jobber.

Jobber has no API for this. So we run one for you.

Jobber's own API, a GitHub MCP server and Cotlet compared
What you need Jobber's APIGitHub MCP serverCotlet
Sending quotes and invoices, converting quotes to jobs No Partly Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Jobber changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 14, 2026. Sources: Jobber Developer Center: App review process · Jobber Developer Center: API queries and mutations · Jobber Help: Developer Center · Zapier Help: Get started with Jobber on Zapier

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Jobber in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Jobber to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Jobber and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/jobber with its own method and path, such as POST /api/v1/jobber/invoices/{invoice_id}, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Jobber API and MCP server do?

14 tools on your own Jobber account. Agents call them as operations of the MCP tools jobber_read and jobber_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Jobber tools in Cotlet's MCP server and REST API
Tool What it does Access
list_clients Clients in your Jobber account with name, contact details and open balance, newest first. read
get_client One client with properties, recent quotes, jobs and invoices. read
list_quotes Quotes with client, status, total and sent date, newest first. read
get_quote One quote with line items, deposit, client message and status. read
list_jobs Jobs with client, title, status, dates and whether an invoice exists. read
list_invoices Invoices with client, status, total, balance and due date. read
get_invoice One invoice with line items, payments recorded and balance. read
create_client Add a client with name, email, phone and a service address. write
create_quote Create a draft quote for a client with line items. write
send_quote Send a quote to the client by email or text, or send it again. writeasks first
convert_quote_to_job Create a job from an approved quote with a start date and team. writeasks first
create_invoice Create a draft invoice for a client or a completed job. write
send_invoice Send an invoice to the client by email or text, or send it again. writeasks first
record_payment Record a cash, check or other offline payment against an invoice. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

All Jobber use cases

Is it safe to connect Jobber?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Jobber API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while Jobber is enabled for agents, so 20 calls a day come to 250 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 10 credits each
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.

Questions

Does Jobber have an 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.

How do I get access?

Sign up free, open Jobber under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Jobber yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Jobber sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: send_quote, convert_quote_to_job, send_invoice, record_payment wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Jobber MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Jobber changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Jobber?

No. Cotlet is independent and not affiliated with Jobber.

Give your agent access to Jobber.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free