Local services & SaaS
Faire
Orders, inventory, reorders and messages for wholesale brands.
12 endpoints
Your AI agent logs jobs from customer emails, allocates engineers, drafts quotes and chases overdue invoices. Sign in to Joblogic once in your own Cloud Browser. No API module, no developer.
6 tools Read and write
Joblogic has no MCP server live and no ChatGPT or Claude app. Its REST API is a paid "API Access" Marketplace module for developers, and its API terms mention an MCP server that we could not find (checked 9 Nov 2026). Cotlet runs 6 Joblogic tools hosted, over MCP for agents and REST for scripts, in your own Joblogic login.
| What you need | Joblogic API | Zapier app | Cotlet |
|---|---|---|---|
| Log jobs | Paid module | Limited | Yes |
| Allocate engineers | Paid module | No | Yes, after your OK |
| Quotes and invoices | Paid module | Lists only | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Developer needed | Yes | Zap setup | No |
Checked 8 Nov 2026. Sources: Joblogic Marketplace: API Access · Joblogic API terms · Joblogic pricing
Once, in a browser we host for you.
One address in its settings.
It drafts the work, you OK what customers get.
We never keep your Joblogic password, and no engineer is allocated until you approve it. Who can see your session
Sign in to Joblogic in a Cloud Browser. Create a Cotlet account, open Joblogic in its Cloud Browser, sign in with your Joblogic login and press Enable for agents.
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.
Joblogic shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Joblogic on after connecting? Refresh the connector and the 6 tools appear.
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" Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth // ~/.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: joblogic_read Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: joblogic_write Search customers by name and postcode. New jobs are logged unallocated and reach no one, so they run at once.
Returns customers with ID, sites, open jobs and contract status.
MCP calljoblogic_read → list_customers
REST endpointGET https://cotlet.dev/api/v1/joblogic/customers
| Name | Type | Description |
|---|---|---|
| query string | string | Name or postcode. |
| page integer | integer | Page number. Default: 1. |
{
"customers": [
{
"customer_id": "C-10421",
"name": "Harrow Lettings Ltd",
"sites": 14,
"open_jobs": 3,
"contract": "Planned maintenance"
}
],
"page": 1
} Returns jobs with customer, site, job type, engineer, visit date and status.
MCP calljoblogic_read → list_jobs
REST endpointGET https://cotlet.dev/api/v1/joblogic/jobs
| Name | Type | Description |
|---|---|---|
| status string | string | Logged, Allocated, Completed, Invoiced. |
| date_from string | string | ISO date. |
| date_to string | string | ISO date. |
| engineer string | string | Engineer name. |
| page integer | integer | Page number. Default: 1. |
{
"jobs": [
{
"job_id": "J-88120",
"customer": "Harrow Lettings Ltd",
"site": "12 Park Row, Leeds",
"type": "Boiler breakdown",
"engineer": "Dan",
"visit": "2026-11-10T09:00",
"status": "Allocated"
}
],
"page": 1
} Creates the job with type, priority and description, unallocated. Reaches no one, so it runs at once.
MCP calljoblogic_write → log_job
REST endpointPOST https://cotlet.dev/api/v1/joblogic/customers/{customer_id}/jobs
| Name | Type | Description |
|---|---|---|
| customer_id string required | string | Customer ID from list_customers. |
| site string required | string | Site address or name. |
| type string required | string | Job type. |
| description string required | string | What is wrong. |
| priority string | string | Low, Normal, High. |
{
"customer_id": "C-10421",
"site": "4 Mill Lane, Leeds",
"type": "Leak",
"description": "Leak under kitchen sink",
"priority": "High"
} {
"job_id": "J-88177",
"customer": "Harrow Lettings Ltd",
"site": "4 Mill Lane, Leeds",
"type": "Leak",
"priority": "High",
"status": "Logged"
} Allocating an engineer waits for your OK.
Puts the visit on the planner; the engineer gets it on the Joblogic app and your settings decide whether the customer is notified. By default you confirm each call; you can switch that off for this tool.
MCP calljoblogic_write → schedule_engineer
REST endpointPOST https://cotlet.dev/api/v1/joblogic/jobs/{job_id}/engineer/schedule
| Name | Type | Description |
|---|---|---|
| job_id string required | string | Job ID from list_jobs. |
| engineer string required | string | Engineer name. |
| visit string required | string | ISO date and time. |
{
"job_id": "job_8c41d2",
"engineer": "engineer",
"visit": "visit"
} {
"job_id": "J-88177",
"engineer": "Dan",
"visit": "2026-11-11T08:00",
"status": "Allocated"
} Draft quotes run at once; sending stays in Joblogic. Unpaid invoices by days overdue.
Creates the quote with lines and VAT, ready to send from Joblogic. Reaches no one, so it runs at once.
MCP calljoblogic_write → create_quote
REST endpointPOST https://cotlet.dev/api/v1/joblogic/customers/{customer_id}/quotes
| Name | Type | Description |
|---|---|---|
| customer_id string required | string | Customer ID from list_customers. |
| site string required | string | Site. |
| items array required | array | Description, quantity, price, VAT rate. |
{
"customer_id": "customer_8c41d2",
"site": "site",
"items": "items"
} {
"quote_id": "Q-5521",
"customer": "Harrow Lettings Ltd",
"net": "1,240.00",
"vat": "248.00",
"total": "1,488.00",
"status": "Draft"
} Returns unpaid invoices with customer, total and days overdue.
MCP calljoblogic_read → list_unpaid_invoices
REST endpointGET https://cotlet.dev/api/v1/joblogic/unpaid-invoices
| Name | Type | Description |
|---|---|---|
| min_days_overdue integer | integer | Only invoices overdue at least this many days. |
{
"invoices": [
{
"invoice_id": "INV-40210",
"customer": "Northside Housing",
"total": "2,310.00",
"days_overdue": 24
}
]
} Your signed-in Joblogic profile, AES-256-GCM encrypted, in Finland. No password.
The 6 Joblogic tools, never the session cookie.
What your login sees: customers, sites, jobs, planner, quotes, invoices.
Payments, contracts, stock, purchase orders, settings, deletes.
You sign in again yourself, in the same Cloud Browser.
Disable for agents, reset the browser, or change your Joblogic password.
Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
When Joblogic moves a button on a job or renames a planner view, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.
| Action | Undo |
|---|---|
| Log a job or draft a quote | Yes, edit or cancel it in Joblogic |
| Allocate an engineer | Yes, reallocate or unallocate it |
1 of 6 tools ask first: schedule_engineer. New jobs and draft quotes reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.
{
"name": "log_job",
"arguments": {
"customer_id": "C-10421",
"site": "4 Mill Lane, Leeds",
"type": "Leak",
"description": "Leak under kitchen sink",
"priority": "High"
}
} curl -X POST https://cotlet.dev/api/v1/joblogic/customers/C-10421/jobs \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"4 Mill Lane, Leeds","type":"Leak","description":"Leak under kitchen sink","priority":"High"}' {
"job_id": "J-88177",
"customer": "Harrow Lettings Ltd",
"site": "4 Mill Lane, Leeds",
"type": "Leak",
"priority": "High",
"status": "Logged"
} A cron job or n8n flow can call the same tools over REST at /api/v1/joblogic with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.
About $39 a monthfor a contractor with 8 engineers, 6,760 credits. Your Joblogic plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Job logged from an email | 2 × 150 | 3,000 |
| Engineer allocated | 1 × 150 | 1,500 |
| Unallocated jobs, daily | 1 × 22 | 220 |
| Quote drafted | 2 × 25 | 500 |
| Overdue invoices, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 6,760 |
Joblogic publishes no job counts, so the month is our example. Dollars at the $29 pack rate.
| 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 |
|---|---|---|
| Joblogic API | Customers, jobs, quotes and invoices for your own developer. | Paid API Access module; you build and host the code. |
| Zapier app | Lists of jobs, sites and purchase orders to other apps. | Polling triggers; nothing you can ask in plain words. |
| By hand | Every screen of Joblogic, one job at a time. | Your office's time. |
If you already have the API module and a developer, building on the API is cheaper for syncing data. To log, allocate and quote from ChatGPT or Claude this week, Cotlet works in the Joblogic account you already have.
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Joblogic tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev, open Joblogic under Integrations in the console and sign in to Joblogic in its Cloud Browser. The trial starts with your first app and asks for no card.
Sign up at cotlet.dev, log in to Joblogic once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Joblogic account through Cotlet, in their phone apps too.
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Joblogic: log jobs from emails; allocate the day; see what is unallocated. You ask in plain words, and anything that reaches other people waits for your OK first.
No. Joblogic has no ChatGPT or Claude connector of its own and Joblogic has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.
Yes, with Cotlet. ChatGPT logs jobs from customer emails with site, type and priority, ready to allocate.
Yes, with Cotlet. ChatGPT allocates the job to the engineer and time you name, after your OK, and lists jobs still without an engineer.
Yes, with Cotlet. ChatGPT drafts the quote for the customer site with VAT, ready to send from Joblogic.
No. Cotlet works through your own Joblogic login, so you do not need the paid API module or a developer. It can do what your login can do.
Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
No. Cotlet is independent and not affiliated with Joblogic.
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