Invoicing & freelance CRM
Joist
Estimates, invoices, clients and payments in Joist for contractors.
20 endpoints
Jobkore publishes no public API and no MCP server (checked 17 Nov 2026). Cotlet runs a hosted Jobkore MCP server with 20 tools that ChatGPT and Claude use in your own Jobkore account. Estimates, change orders and anything a client sees wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Jobkore. Jobkore is a trademark of its owner. If Jobkore's own integrations cover what you need, use them first.
20 tools Read and write
Jobkore publishes no public API and no developer documentation; its docs and llms.txt list none. No Jobkore MCP server and no official ChatGPT or Claude connector was found. Hank AI, its assistant, works only inside Jobkore.
| What you need | By hand | Hank AI | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | Copy and paste | Inside Jobkore only | Hosted MCP server |
| Draft and review estimates | Line by line | By chat, in the app | From your agent, using Hank |
| Payments, change orders, subs and leads | One screen at a time | Drafts change orders | 20 tools, writes after your OK |
| Run from n8n or a script | Manual only | Manual only | REST, same key |
Checked 17 Nov 2026. Sources: Jobkore · Jobkore llms.txt · Jobkore docs · Docs: Hank AI · Docs: QuickBooks · Docs: Online Payments · Docs: Language Support · Docs: Dashboard · Docs: Reports & Analytics · Docs: Jobs · Docs: Client Management · Docs: Estimates · Docs: Line Items & Sections · Docs: Invoices · Docs: Change Orders · Docs: Email System · Docs: Share Links & Signatures · Docs: PDF Generation · Docs: Subs · Docs: Field Notes · Docs: Catalog · Docs: Leads · Docs: Your Website · Docs: Import & Export
Once, in a browser we host for you.
One address in its settings.
It updates the job, you approve what goes out.
Cotlet never sees or stores your password. Estimates, change orders and anything a client sees wait for your OK. Who can see your session
Sign in to Jobkore in a Cloud Browser. Open app.getjobkore.com in your Cotlet Cloud Browser and log in with your own Jobkore account.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Jobkore sits behind the shared address https://cotlet.dev/mcp/v1 with the other apps you use, so one connector is enough. Enabled Jobkore later? Refresh the connector and its 20 tools load.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: jobkore_read One tool per owner workflow in the Jobkore docs. Reads run at once; every write asks first.
The Dashboard, Reports, each job's money in one view, and online payment status.
Outstanding is what clients still owe on your invoices, with the count of unpaid invoices and the past-due amount. Recent invoices and estimates come with it. Read only.
MCP calljobkore_read → get_dashboard
REST endpointGET https://cotlet.dev/api/v1/jobkore/dashboard
No parameters.
{
"outstanding": 18450,
"unpaid_invoices": 5,
"past_due": 3200,
"this_month": 12600,
"out_for_approval": 24900,
"year_to_date": 186300
} Returns the four key metrics: Collected (with the change on the same time last year), Avg Days to Pay, Estimates Sent with the total quoted, and Won with its share. Outstanding and Overdue are on get_dashboard. Read only.
MCP calljobkore_read → get_reports
REST endpointGET https://cotlet.dev/api/v1/jobkore/reports
| Name | Type | Description |
|---|---|---|
| period string required | string | `month`, `quarter`, `year` or `custom`. |
| from string | string | For `custom`: ISO start date. |
| to string | string | For `custom`: ISO end date. |
{
"period": "period"
} {
"period": "October 2026",
"collected": 21400,
"invoices_paid": 9,
"avg_days_to_pay": 11,
"estimates_sent": 14,
"quoted": 96500,
"won": 6,
"won_share": "43%"
} A job holds everything for one piece of work, with invoiced, collected and outstanding in one view. Most one-visit work has no job, and a document is never on two jobs. Read only.
MCP calljobkore_read → get_jobs
REST endpointGET https://cotlet.dev/api/v1/jobkore/jobs
| Name | Type | Description |
|---|---|---|
| job string | string | Job name, for example Henderson kitchen. Leave empty to list jobs. |
{
"job": "Henderson kitchen",
"client": "Example Homeowner",
"estimates": [
"EST-0031"
],
"invoices": [
"INV-0047"
],
"invoiced": 28600,
"collected": 20000,
"outstanding": 8600,
"owed_to_subs": 400
} Online payments run through Stripe Connect in your Jobkore account; ACH takes about four business days. This reads the status Jobkore shows. Read only.
MCP calljobkore_read → get_payment_status
REST endpointGET https://cotlet.dev/api/v1/jobkore/payment-status
| Name | Type | Description |
|---|---|---|
| invoice string | string | One invoice. Leave empty for recent online payments. |
{
"payments": [
{
"invoice": "INV-0050",
"method": "ACH",
"amount": 2400,
"status": "Pending"
},
{
"invoice": "INV-0049",
"method": "Card",
"amount": 1250,
"status": "Paid"
}
]
} Line items, sections and private markup; invoices from accepted estimates; branded email or a share link; PDFs.
Numbers run EST-0001, EST-0002 and on. Markup is rolled into the rate the client sees. Line item notes appear on the estimate, PDF and share page, so the agent never puts cost reminders there. Saving sends nothing. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_estimates
REST endpointPOST https://cotlet.dev/api/v1/jobkore/estimates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| estimate string | string | For `get` and `update`: the EST number. |
| client string | string | For `create`: the client. |
| job string | string | Optional job to file it under; defaults to No Job. |
| title string | string | For example Kitchen Renovation. |
| valid_until string | string | `7`, `14`, `30`, `60` or `90` days, or `never`. |
| lines array | array | Line items: description (required), quantity, unit price, unit (sq ft, hours, each), taxable, markup percent, notes and section. Notes are shown to the client; markup never is. |
{
"action": "action"
} {
"estimate": "EST-0031",
"client": "Example Homeowner",
"title": "Kitchen Renovation",
"sections": 3,
"total": 24900,
"valid_until": "30 days",
"status": "Draft"
} Numbers run INV-0001 and on, separately from estimates. One job can hold several invoices. Creating an invoice sends nothing; send_document does. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_invoices
REST endpointPOST https://cotlet.dev/api/v1/jobkore/invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `from_estimate`. `list` and `get` only read. |
| invoice string | string | For `get`: the INV number. |
| estimate string | string | For `from_estimate`: the accepted estimate. |
| client string | string | For `create`. |
| due string | string | `on_receipt`, or Net `7`, `14`, `30`, `45`, `60` or `90`. |
| lines array | array | Line items: description (required), quantity, unit price, unit (sq ft, hours, each), taxable, markup percent, notes and section. Notes are shown to the client; markup never is. |
{
"action": "action"
} {
"invoice": "INV-0052",
"from_estimate": "EST-0031",
"total": 24900,
"due": "Net 14",
"status": "Draft"
} The email carries your logo, the total and a View & Respond or View & Pay button, with the PDF attached. Share links expire after 90 days unless the client keeps opening them. Jobkore then shows when the document is opened. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → send_document
REST endpointPOST https://cotlet.dev/api/v1/jobkore/documents
| Name | Type | Description |
|---|---|---|
| document string required | string | Estimate or invoice number, for example EST-0012 or INV-0045. |
| method string required | string | `email` sends Jobkore's branded email; `link` returns the share link only. |
| to string | string | Recipient. Defaults to the client's primary contact. |
| message string | string | Custom message, or your saved default. |
{
"document": "document",
"method": "method"
} {
"document": "EST-0031",
"method": "email",
"to": "homeowner@example.com",
"pdf_attached": true,
"sent": true
} The PDF carries your logo, line items with markup rolled into the rate, sections with subtotals, totals, notes, terms and any collected signatures. Columns follow the document's display settings. Downloading sends nothing.
MCP calljobkore_read → download_pdf
REST endpointGET https://cotlet.dev/api/v1/jobkore/pdfs/download
| Name | Type | Description |
|---|---|---|
| document string required | string | Estimate or invoice number, for example EST-0012 or INV-0045. |
{
"document": "document"
} {
"document": "EST-0031",
"pdf": "https://files.example.com/EST-0031.pdf"
} Signed scope changes on sent invoices, payments you took in person, and what you owe each sub per job.
A change order has no number or PDF of its own: the client signs it on the invoice, and the total moves only after signing. On an accepted estimate, create the invoice first. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → add_change_order
REST endpointPOST https://cotlet.dev/api/v1/jobkore/change-orders
| Name | Type | Description |
|---|---|---|
| invoice string required | string | A sent invoice. Jobkore refuses drafts and estimates. |
| title string required | string | For example Tile upgrade. |
| lines array | array | Line items: description (required), quantity, unit price, unit (sq ft, hours, each), taxable, markup percent, notes and section. Notes are shown to the client; markup never is. |
{
"invoice": "INV-0047",
"title": "Tile upgrade",
"lines": [
{
"description": "Porcelain tile upgrade, kitchen floor",
"quantity": 200,
"unit": "sq ft",
"unit_price": 9
}
]
} {
"invoice": "INV-0047",
"change_order": "Tile upgrade",
"amount": 1800,
"status": "Sent for signature"
} Jobkore recalculates the balance and the Dashboard. Online card and ACH payments record themselves; this is for money you took in person. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → record_payment
REST endpointPOST https://cotlet.dev/api/v1/jobkore/payments
| Name | Type | Description |
|---|---|---|
| invoice string required | string | A sent invoice. |
| amount number required | number | Amount received. |
| method string | string | For example check or cash. |
| date string | string | ISO date. Defaults to today. |
{
"invoice": "invoice",
"amount": 1
} {
"invoice": "INV-0047",
"amount": 3000,
"method": "check",
"balance_due": 5600,
"saved": true
} Each sub has one running balance per job, kept off every client document. What you charge the client and what you agree with the sub never move each other. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_subs
REST endpointPOST https://cotlet.dev/api/v1/jobkore/subs/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `pay`. `list` and `get` only read. |
| job string required | string | The job the sub works on. |
| sub string | string | Subcontractor name; a name is all a new one needs. |
| work string | string | For `add`: what they do. |
| amount number | number | For `add`: amount agreed. For `pay`: amount paid. |
{
"action": "action",
"job": "job"
} {
"job": "Henderson kitchen",
"sub": "Example Electric",
"agreed": 900,
"paid": 500,
"owed": 400
} Your job site notebook, Hank's drafts from it, and Hank's review before you send.
Notes save as you go and have no title field. They are your record of the job until you turn them into a draft with draft_from_field_notes. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → add_field_note
REST endpointPOST https://cotlet.dev/api/v1/jobkore/field-notes
| Name | Type | Description |
|---|---|---|
| text string required | string | The note. Its first line becomes its name. |
| attachments array | array | Links to photos or PDFs the Cloud Browser can download. |
{
"text": "text"
} {
"note": "Henderson kitchen walkthrough",
"attachments": 3,
"saved": true
} Hank writes the draft in your app language. It stays a draft: nothing reaches the client until send_document. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → draft_from_field_notes
REST endpointPOST https://cotlet.dev/api/v1/jobkore/field-notes/draft
| Name | Type | Description |
|---|---|---|
| notes array required | array | Field notes by their first line. |
| kind string required | string | `estimate` or `invoice`. |
| client string | string | Client for the draft. |
{
"notes": "notes",
"kind": "kind"
} {
"notes": [
"Henderson kitchen walkthrough"
],
"draft": "EST-0033",
"lines": 12,
"status": "Draft"
} Returns what Hank would fix. Applying a change is a separate write, made with manage_estimates or manage_invoices after your OK.
MCP calljobkore_read → hank_review
REST endpointGET https://cotlet.dev/api/v1/jobkore/reviews/hank
| Name | Type | Description |
|---|---|---|
| document string required | string | Estimate or invoice number, for example EST-0012 or INV-0045. |
{
"document": "document"
} {
"document": "EST-0031",
"suggestions": [
"Tile allowance has no budget amount",
"Valid Until is set to Never"
]
} Clients with up to 20 contacts and a language, your price catalog, and CSV import and export.
The primary contact's email is where documents go by default. A client's language decides the language of their share pages, PDFs and emails. `get` also returns revenue and every estimate and invoice for that client. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/jobkore/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| client string | string | Client name, for `get` and `update`. Name is the only required field on `create`. |
| fields object | object | Address, default rate and language (`English` or `Spanish`). |
| contacts array | array | Up to 20 contacts: name, role, email, phone, and one primary. |
{
"action": "action"
} {
"client": "Example Homeowner",
"language": "Spanish",
"primary_contact": "homeowner@example.com",
"contacts": 2,
"saved": true
} Documents get a copy of a catalog item, so a new price applies to new estimates and invoices only; sent ones keep their prices. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_catalog
REST endpointPOST https://cotlet.dev/api/v1/jobkore/catalog/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| item string | string | Item name. |
| type string | string | `Service`, `Material` or `Other`. |
| rate number | number | Base unit price, before markup. |
| markup number | number | Markup percent. |
| unit string | string | For example each, sq ft, hour, lin ft. Blank is allowed. |
{
"action": "action"
} {
"item": "Tile install",
"type": "Service",
"rate": 9,
"markup": 20,
"unit": "sq ft",
"saved": true
} Jobkore shows how every column maps before anything is created, and the agent shows you that mapping. Rows with the same client name become contacts of one client. Estimates and invoices do not import. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → import_csv
REST endpointPOST https://cotlet.dev/api/v1/jobkore/csvs
| Name | Type | Description |
|---|---|---|
| file_url string required | string | A link the Cloud Browser can download the CSV from. |
| list string | string | `clients`, `catalog` or `subs`. Jobkore detects it from the header row when empty. |
{
"file_url": "https://example.com"
} {
"list": "clients",
"rows": 42,
"clients_created": 38,
"contacts_added": 4,
"imported": true
} Returns the CSV Jobkore produces for that list. Read only.
MCP calljobkore_read → export_data
REST endpointGET https://cotlet.dev/api/v1/jobkore/datas/export
| Name | Type | Description |
|---|---|---|
| list string required | string | `clients`, `catalog` or `subs`. |
{
"list": "list"
} {
"list": "catalog",
"rows": 84,
"csv": "https://files.example.com/catalog.csv"
} Leads from every channel and your hosted website. Adding leads, follow-ups and the site need the Marketing add-on.
Every account can read leads. Adding leads, follow-up dates and won or lost need the Marketing add-on. Leads from your website contact form arrive here by themselves. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_leads
REST endpointPOST https://cotlet.dev/api/v1/jobkore/leads/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `follow_up`, `won`, `lost`. `list` and `get` only read. |
| lead string | string | Lead name, for every action but `list` and `add`. |
| fields object | object | For `add`: name, phone or email (at least one), what they want, how they reached you. |
| date string | string | For `follow_up`: ISO date. |
{
"action": "action"
} {
"lead": "Example Prospect",
"want": "Bathroom remodel",
"source": "Referral",
"follow_up": "2026-11-20",
"status": "New"
} The website is the Marketing add-on ($19 a month or $190 a year on top of Jobkore). Publishing puts your changes in front of the public, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calljobkore_write → manage_website
REST endpointPOST https://cotlet.dev/api/v1/jobkore/website/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `approve_testimonial`, `publish`. `list` and `get` only read. |
| testimonial string | string | For `approve_testimonial`: the testimonial, by client name. |
{
"action": "action"
} {
"site": "example-builders.example.com",
"published": true,
"to_do": [
"2 testimonials waiting for approval"
],
"visits_this_week": 37
} Your signed-in Jobkore browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 20 Jobkore tools. The session cookie stays in the Cloud Browser.
Your Jobkore account: clients, jobs, documents, payments, subs and leads.
Your subscription, the Stripe and QuickBooks Online connections, notification settings and your profile.
You log in again yourself, in the same Cloud Browser.
Disable Jobkore for agents, reset the browser, or change your Jobkore password.
Cotlet never sees or stores your password. You log in to Jobkore yourself, and the agent uses only the session that leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Client, catalog item, draft estimate or invoice | Call the same tool again with the earlier values |
| Payment or sub payment logged by mistake | Correct it on the invoice or the job in Jobkore |
| Change order sent | It counts only once signed: tell the client not to sign it |
| Estimate or invoice emailed | Already with your client: talk to them before you send a new one |
All 13 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 7 read tools, Dashboard, Reports, jobs, payment status, PDFs, CSV export and Hank's review, run at once.
{
"name": "add_change_order",
"arguments": {
"invoice": "INV-0047",
"title": "Tile upgrade",
"lines": [
{
"description": "Porcelain tile upgrade, kitchen floor",
"quantity": 200,
"unit": "sq ft",
"unit_price": 9
}
]
}
} curl -X POST https://cotlet.dev/api/v1/jobkore/change-orders \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"invoice":"INV-0047","title":"Tile upgrade","lines":[{"description":"Porcelain tile upgrade, kitchen floor","quantity":200,"unit":"sq ft","unit_price":9}]}' {
"invoice": "INV-0047",
"change_order": "Tile upgrade",
"amount": 1800,
"status": "Sent for signature"
} The example adds a 200 sq ft tile upgrade at $9: an $1,800 change order that joins the invoice total once the client signs. A cron job or n8n flow can make the same call over REST at /api/v1/jobkore with the same key and price, in JSON. Failed calls are free.
About $15 a monthfor a remodeling contractor with about four open jobs, 2,550 credits. Your Jobkore plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Monday dashboard and jobs check | 2 × 4 | 80 |
| Field note, Hank draft and review | 3 × 10 | 300 |
| Sending estimates and invoices | 1 × 22 | 220 |
| Invoices from accepted estimates | 1 × 8 | 80 |
| Change orders | 1 × 4 | 40 |
| Payments taken and paid to subs | 1 × 20 | 200 |
| Lead follow-ups | 1 × 12 | 120 |
| Monthly report | 1 × 1 | 10 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 105 calls | 2,550 |
The smallest pack, 5,000 credits for $29, covers this month.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| 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.
| Option | What it does | Where it stops |
|---|---|---|
| Hank AI | Edits documents by chat, drafts from field notes, reviews before sending. | Inside Jobkore only; not a route for ChatGPT, Claude or a script. |
| QuickBooks Online sync | Sends clients, invoices and payments one way to QuickBooks. | Accounting only; nothing comes back into Jobkore. |
| CSV import and export | Clients, catalog and subs in and out. | No estimates or invoices; files you handle yourself. |
| Automatic follow-ups | Jobkore chases unanswered estimates, unsigned change orders and late invoices by email. | Reminders only; the work behind them is still yours. |
If Hank and the automatic follow-ups already cover your week, keep them. Cotlet fits when you want ChatGPT, Claude or a script to work across your whole Jobkore account, from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Jobkore tools.
Sign up free at https://cotlet.dev/signup?app=jobkore, turn on Jobkore under Integrations in the console and log in at https://app.getjobkore.com/login in your Cloud Browser. Then connect your AI agent and ask it what clients owe you. The trial needs no card.
Jobkore publishes no public API and no developer documentation; its docs and llms.txt list none (checked 17 Nov 2026). No Jobkore MCP server and no official ChatGPT or Claude connector was found. Hank AI is Jobkore's own assistant inside the app. Cotlet does not need one: it works in your own signed-in Jobkore account.
Hank AI is Jobkore's assistant inside the app: it edits documents by chat, turns field notes into drafts and reviews a document before you send it. Cotlet lets ChatGPT, Claude or a script you choose work across your whole Jobkore account, and two of its tools call on Hank for drafts and reviews.
No. Jobkore rolls markup into the rate and never shows it, and subs are kept on the job, never on a document. Line item notes are the exception: clients see them, so the tools never put cost notes there.
Yes. Set a client's language to Spanish with manage_clients, and Jobkore sends their share pages, PDFs and emails in Spanish, even if you run the app in English.
Only in how it is called. Both carry the same 20 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Jobkore.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy