Local services & SaaS
Tekmetric
Job board, repair orders, customers, appointments and texts in your shop.
10 endpoints
ShopView names an open API on its Enterprise page but publishes no documentation for it, and runs no MCP server (checked 16 Nov 2026). Cotlet runs a hosted ShopView MCP server with 37 tools that ChatGPT and Claude use in your own shop account. Invoices, payments and anything your customers see wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by ShopView. ShopView is a trademark of its owner. If ShopView's own integrations cover what you need, use them first.
37 tools Read and write
ShopView's Enterprise page says that for everything beyond its own integrations, "there's an open API to connect it". No public API documentation, self-serve key or plan was found, and the page leads to a talk with its team. No ShopView MCP server and no official ChatGPT or Claude connector was found.
| What you need | ShopView API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Start today with your own login | Talk to the team first | Your login | Your login, once |
| Work orders, payments, parts and reports | No public docs | One screen at a time | 37 tools, writes after your OK |
| Run from n8n or a script | After access, your own code | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: ShopView Enterprise · ShopView Help Center · Help: ShopView Integration with QuickBooks Online · Help: Adding Lines and Parts, New and Existing WO · Help: Assigning Technicians to Lines · Help: Clocking In & Out in ShopView · Help: Splitting Work Orders · Help: Changing a Work Order's Lead Technician · Help: Authorizer: Record Who Approved the Work · Help: Work Order History, Audit Log · Help: Completing a Work Order: The Streamlined Flow · Help: Invoicing work orders and payment scenarios · Help: Void payments, reverse invoices, partial payments · Help: Refund a payment made through the Customer Portal · Help: Customer Deposits: Taking Pre-Payment on a Work Order · Help: How to Add Credit for a Customer · Help: Manage payments and receipts · Help: Fees like Freight or Miscellaneous Charges · Help: How to apply a discount in ShopView · Help: Part Sales: Sell parts without creating a work order · Help: Purchase Orders (POs) in ShopView · Help: Bulk Receiving: Receive Multiple Purchase Orders at Once · Help: Edit Vendor Invoices After Receiving · Help: How to Add a New Vendor or Delete a Vendor · Help: Special order part returns · Help: Outstanding invoices and customer statements · Help: Vehicle Management & VIN Decoder · Help: Automatic Late Fees on Overdue Invoices · Help: Price Matrices & Pricing Rules · Help: Websites: Editing Your Website · Help: Websites: Publishing & Domains · Help: Sales Report · Help: Technician Efficiency Report · Help: Shop Efficiency Report · Help: Timesheet Activities Report · Help: Advisor Analysis Report · Help: Accounts Receivable Reports · Help: Sales Tax Collected Report · Help: Work In Progress (WIP) Report · Help: Inventory Value Report · Help: Take in-person card payments with ShopPay Terminals
Once, in a browser we host for you.
One address in its settings.
Write-ups, invoices and reports, money after your OK.
Your agent works in your own signed-in Cloud Browser. Invoices, payments and anything a customer sees wait for your OK. Who can see your session
Sign in to ShopView in a Cloud Browser. Open app.shopview.com in your Cotlet Cloud Browser and sign in with your own ShopView email and password.
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.
ShopView is reached at the shared address https://cotlet.dev/mcp/v1, like every other app you turn on, so a single connector covers them all. Turned ShopView on later? Refresh the connector to load its 37 tools.
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: shopview_read One tool per owner workflow in the ShopView Help Center. The reports, outstanding invoices and audit log only read; every other tool asks first.
From the first line to completion: parts, technicians, the lead, the authorizer, fees and discounts, and the punch clock.
Every work order starts with a line, the description of the work, where labor and parts come together. A new work order is linked to the customer and asset you name. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → add_work_order_lines
REST endpointPOST https://cotlet.dev/api/v1/shopview/work-order-lines
| Name | Type | Description |
|---|---|---|
| work_order string | string | Existing work order. Leave empty to create one. |
| customer string | string | Customer, for a new work order. |
| asset string | string | The customer's truck, trailer or equipment, for a new work order. |
| lines array required | array | Each line: what you are doing and why, labor hours and parts. |
{
"lines": "lines"
} {
"work_order": "WO 1042",
"customer": "Example Freight",
"asset": "Tractor, unit T12",
"lines": [
{
"description": "Replace front brake pads and rotors",
"hours": 3.5,
"parts": 4
}
],
"saved": true
} An assigned line shows in the Assigned view on the Schedule. ShopView still lets any technician punch into a job, assigned or not. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → assign_technicians
REST endpointPOST https://cotlet.dev/api/v1/shopview/technicians/assign
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| line string required | string | Line, by its description. |
| technicians array required | array | Up to 5 technicians. |
{
"work_order": "work order",
"line": "line",
"technicians": "technicians"
} {
"work_order": "WO 1042",
"line": "Replace front brake pads and rotors",
"technicians": [
"Tech A"
],
"saved": true
} The lead gets the unassigned lines and new lines default to them; lines assigned to a specific technician stay put and recorded time is never touched. The lead of an Invoiced or Paid work order cannot be changed. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → change_lead_technician
REST endpointPATCH https://cotlet.dev/api/v1/shopview/lead-technician
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| technician string required | string | New lead, or `Unassigned`. |
| shifts string | string | If the outgoing tech has shifts: `keep` or `clear`. |
{
"work_order": "work order",
"technician": "technician"
} {
"work_order": "WO 1042",
"lead": "Tech B",
"shifts": "keep",
"saved": true
} Use it when part of the job is billed or finished separately. The agent names the lines that move before it splits. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → split_work_order
REST endpointPOST https://cotlet.dev/api/v1/shopview/work-order/split
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| lines array required | array | Lines that move to the new work order. |
{
"work_order": "work order",
"lines": "lines"
} {
"work_order": "WO 1042",
"new_work_order": "WO 1043",
"moved_lines": 1,
"saved": true
} Opens the work order's options menu, then Audit Log, and returns work order level and line level changes in order. It changes nothing and runs without asking.
MCP callshopview_read → view_audit_log
REST endpointGET https://cotlet.dev/api/v1/shopview/audit-logs/view
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
{
"work_order": "work order"
} {
"work_order": "WO 1042",
"entries": [
{
"at": "2026-11-14 08:12",
"user": "Advisor A",
"change": "Status Estimate to Approved"
},
{
"at": "2026-11-14 09:30",
"user": "Tech A",
"change": "Line clocked in"
}
]
} The Complete Work Order flow asks only for the fields your shop requires, then leads to the invoice. Your shop's approval, vendor invoice and review rules apply as set. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → complete_work_order
REST endpointPOST https://cotlet.dev/api/v1/shopview/work-order/complete
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| mileage number | number | If your shop requires it. |
| vin string | string | If your shop requires it. |
| engine_hours number | number | If your shop requires it. |
{
"work_order": "work order"
} {
"work_order": "WO 1042",
"status": "Completed",
"next": "Ready to invoice",
"saved": true
} Uses ShopView's Fees & Discounts feature, on work orders and part sales. The fee lands on the customer's invoice. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → add_work_order_fee
REST endpointPOST https://cotlet.dev/api/v1/shopview/work-order-fees
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| level string required | string | One of `work_order`, `line`, `part`. |
| name string required | string | For example Freight or Disposal. |
| amount number required | number | Flat amount, or the percentage with `percent`. |
| percent boolean | boolean | True for a percentage. |
| taxable boolean | boolean | Whether tax applies. |
{
"work_order": "work order",
"level": "level",
"name": "Jane Doe",
"amount": 1
} {
"work_order": "WO 1042",
"fee": "Freight",
"amount": 85,
"taxable": false,
"saved": true
} Built-in Fees & Discounts, from the work order's menu (Add Work Order Fee / Discount) or the line. It lowers what the customer pays. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → apply_discount
REST endpointPOST https://cotlet.dev/api/v1/shopview/discount/apply
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| line string | string | Line to discount. Leave empty for the whole work order. |
| amount number required | number | Flat amount, or the percentage with `percent`. |
| percent boolean | boolean | True for a percentage. |
{
"work_order": "work order",
"amount": 1
} {
"work_order": "WO 1042",
"discount": "10%",
"applies_to": "whole work order",
"saved": true
} Work order lines are billable and land in the asset's history; departments are payroll-only time. The punch belongs to the user signed in to the Cloud Browser. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → clock_in_out
REST endpointPOST https://cotlet.dev/api/v1/shopview/out/clock
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `in`, `out`. |
| work_order string | string | Work order, for billable line time. |
| line string | string | Line on that work order. |
| department string | string | Department, for non-billable time such as shop cleanup or training. |
{
"action": "action"
} {
"action": "in",
"work_order": "WO 1042",
"line": "Replace front brake pads and rotors",
"at": "2026-11-16 07:02"
} Invoicing on the customer's credit terms, payments, deposits, credits and late fees. Portal payments are refunded in the portal.
Credit terms decide what happens: COD needs payment at invoicing, Net terms and Due on Receipt allow invoicing now, Credit Hold blocks it. The invoice reaches your customer's balance, so the agent shows it first. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → invoice_work_order
REST endpointPOST https://cotlet.dev/api/v1/shopview/work-order/invoice
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| take_payment boolean | boolean | False to invoice on the customer's credit terms. |
{
"work_order": "work order"
} {
"work_order": "WO 1042",
"invoice": "INV 2210",
"total": 2480,
"terms": "Net 30",
"status": "Invoiced"
} From the customer's Unpaid Invoices tab, New Payment. A partial payment leaves the remaining balance open on the invoice. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → record_payment
REST endpointPOST https://cotlet.dev/api/v1/shopview/payments
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as on the Customers page. |
| invoice string required | string | Invoice number from Unpaid Invoices. |
| amount number required | number | Amount paid; less than the balance leaves the rest open. |
| method string required | string | Payment method as ShopView lists it. |
| date string | string | ISO date. |
{
"customer": "customer",
"invoice": "invoice",
"amount": 1,
"method": "method"
} {
"customer": "Example Freight",
"invoice": "INV 2210",
"paid": 1000,
"balance": 1480,
"receipt": "Ready to print"
} All payments on an invoice must be deleted before it can be reversed; an unpaid invoice reverses directly from the Finance tab. Payments made in the Customer Portal go through refund_portal_payment instead. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → void_payment_reverse_invoice
REST endpointPOST https://cotlet.dev/api/v1/shopview/payment-reverse-invoice/void
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| step string required | string | One of `void_payment`, `reverse_invoice`. |
{
"work_order": "work order",
"step": "step"
} {
"work_order": "WO 1042",
"payment_voided": true,
"invoice_reversed": true,
"status": "Completed"
} Portal payments are refunded in the portal, not with Issue Credit or Reverse on the work order. Money goes back to your customer's card. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → refund_portal_payment
REST endpointPOST https://cotlet.dev/api/v1/shopview/portal-payment/refund
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as on the Customers page. |
| invoice string required | string | Invoice paid in the portal. |
| amount number | number | Amount to refund. Defaults to the full payment. |
{
"customer": "customer",
"invoice": "invoice"
} {
"customer": "Example Freight",
"invoice": "INV 2198",
"refunded": 240,
"via": "Customer Portal"
} Add Deposit sits on the work order's Finance tab while it is Estimate, Approved, In Progress or Review. ShopView applies the deposit to the invoice by itself, and it syncs to QuickBooks Online. Owners, administrators, service and parts managers and service advisors have the permission by default. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → take_deposit
REST endpointPOST https://cotlet.dev/api/v1/shopview/deposit/take
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| amount number required | number | Deposit amount. |
| method string | string | How it was paid, or `portal` to collect it in the Customer Portal. |
{
"work_order": "WO 1042",
"amount": 1500,
"method": "Card"
} {
"work_order": "WO 1042",
"deposit": 1500,
"method": "Card",
"applies_to": "the invoice when created",
"saved": true
} Customers, the customer, Unpaid Invoices, New Credit. These credits stay in ShopView and do not sync to QuickBooks Online or other systems. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → add_customer_credit
REST endpointPOST https://cotlet.dev/api/v1/shopview/customer-credits
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as on the Customers page. |
| amount number required | number | Credit amount. |
| note string | string | Reason, for your records. |
{
"customer": "customer",
"amount": 1
} {
"customer": "Example Freight",
"credit": 150,
"note": "Goodwill on comeback",
"saved": true
} Set in the Customer Portal payment settings and works only with Shop Pay. After a 30 day grace period past the due date, a fee is charged every 30 days on the original amount, for every customer with an overdue invoice. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → configure_late_fees
REST endpointPOST https://cotlet.dev/api/v1/shopview/late-fees/configure
| Name | Type | Description |
|---|---|---|
| enabled boolean required | boolean | On or off. |
| rate number | number | Late fee percentage of the original invoice amount. |
{
"enabled": true
} {
"enabled": true,
"rate": 2,
"grace_days": 30,
"cycle_days": 30,
"saved": true
} Reads the Work Orders page filtered By Status to Invoiced; paid ones are labeled Paid. It changes nothing and runs without asking.
MCP callshopview_read → view_outstanding_invoices
REST endpointGET https://cotlet.dev/api/v1/shopview/outstanding-invoices/view
| Name | Type | Description |
|---|---|---|
| customer string | string | Only this customer. Leave empty for all. |
{
"invoices": [
{
"work_order": "WO 1031",
"customer": "Example Freight",
"amount": 4915,
"status": "Invoiced"
},
{
"work_order": "WO 1036",
"customer": "Sample Haulage",
"amount": 2480,
"status": "Invoiced"
}
]
} Counter sales, purchase orders, receiving by vendor, vendor invoices, returns and the price matrix.
Parts, Part Sales. A part sale makes a parts-only invoice and handles returns of parts sold without service work. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → create_part_sale
REST endpointPOST https://cotlet.dev/api/v1/shopview/part-sales
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer, or `Counter Sale`. |
| parts array required | array | Inventory or special-order parts with quantities. |
{
"customer": "customer",
"parts": "parts"
} {
"part_sale": "PS 318",
"customer": "Counter Sale",
"parts": [
{
"part": "Air filter",
"quantity": 2
}
],
"total": 96,
"saved": true
} Parts, Purchase Orders, New PO. ShopView numbers it. Parts requested from a work order get their own linked purchase order automatically. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → create_purchase_order
REST endpointPOST https://cotlet.dev/api/v1/shopview/purchase-orders
| Name | Type | Description |
|---|---|---|
| vendor string required | string | Vendor, required. |
| parts array required | array | Each part with quantity and cost. |
{
"vendor": "vendor",
"parts": "parts"
} {
"purchase_order": "PO 774",
"vendor": "Example Truck Parts",
"parts": 3,
"total": 612,
"saved": true
} Bulk Receive groups purchase orders by vendor, each with its own invoice number, and fixes a missing vendor or part number on the same page. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → receive_purchase_orders
REST endpointPOST https://cotlet.dev/api/v1/shopview/purchase-orders/receive
| Name | Type | Description |
|---|---|---|
| purchase_orders array required | array | Purchase orders to receive. |
| vendor_invoice string | string | Vendor invoice number, per vendor. |
| partial object | object | Quantities received, when not everything arrived. |
{
"purchase_orders": "purchase orders"
} {
"received": [
"PO 774",
"PO 775"
],
"vendors": 2,
"partial": false
} Changes sync to QuickBooks automatically. New lines cannot be added to a received vendor invoice. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → edit_vendor_invoice
REST endpointPATCH https://cotlet.dev/api/v1/shopview/vendor-invoice
| Name | Type | Description |
|---|---|---|
| vendor_invoice string required | string | Vendor invoice number. |
| changes object required | object | Invoice number, date, vendor, description, tax, or a line's part number, description, cost, quantity, core charge. |
{
"vendor_invoice": "vendor invoice",
"changes": "changes"
} {
"vendor_invoice": "EP-55120",
"changed": [
"cost on line 2"
],
"synced": true
} Parts, Vendors. Run `list` first: an existing name cannot be added twice. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → manage_vendors
REST endpointPOST https://cotlet.dev/api/v1/shopview/vendors/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `delete`. `list` only reads. |
| name string | string | Vendor name; it must be unique. |
| tax string | string | Default tax on this vendor's bills. |
| details object | object | Optional address, phone, email, website, notes, credit terms (COD if empty) and credit limit. |
{
"action": "action"
} {
"vendor": "Example Truck Parts",
"tax": "Exempt",
"credit_terms": "Net 30",
"saved": true
} The part then appears in Parts, Returns. Invoiced work orders are read-only, so the payment is voided and the work order reopened first. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → return_special_order_part
REST endpointPOST https://cotlet.dev/api/v1/shopview/special-order-part/return
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as ShopView shows it. |
| part string required | string | The part on that work order. |
| reason string required | string | Return reason. |
| outcome string required | string | One of `to_inventory`, `to_vendor`. |
{
"work_order": "work order",
"part": "part",
"reason": "reason",
"outcome": "outcome"
} {
"work_order": "WO 1042",
"part": "Brake chamber",
"outcome": "to_vendor",
"saved": true
} Every account has a default matrix; more can be assigned to part categories. A change reprices parts on future work, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → manage_price_matrix
REST endpointPOST https://cotlet.dev/api/v1/shopview/price-matrix/manage
| Name | Type | Description |
|---|---|---|
| matrix string required | string | Matrix name. The default matrix prices uncategorized parts. |
| rules array | array | Rows of cost range with markup or margin. Leave empty to read. |
{
"matrix": "matrix"
} {
"matrix": "Default",
"rules": [
{
"from": 10.01,
"to": 100,
"markup": 40
}
],
"saved": true
} Decode a VIN onto the customer's asset. Edit the website draft, then publish it.
Customers, the customer, Assets, New Asset, Decode VIN. Returns make, model, year and engine for you to check before saving. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → add_asset_vin
REST endpointPOST https://cotlet.dev/api/v1/shopview/asset-vins
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, as on the Customers page. |
| vin string required | string | VIN, exactly as printed. |
| details object | object | Make, model, year and engine, if decoding fails. |
{
"customer": "customer",
"vin": "vin"
} {
"customer": "Example Freight",
"vin": "1XKAD49X0EJ000000",
"decoded": {
"make": "Example make",
"model": "Example model",
"year": 2014
},
"saved": true
} Edits the draft in the website editor. Visitors see nothing until publish_shop_website. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → edit_shop_website
REST endpointPATCH https://cotlet.dev/api/v1/shopview/shop-website
| Name | Type | Description |
|---|---|---|
| page string required | string | Website page, as the editor sidebar lists it. |
| changes object required | object | Fields to change, in the editor's own labels. |
{
"page": "page",
"changes": "changes"
} {
"page": "Home",
"changed": [
"hero text",
"services"
],
"published": false
} Publishing takes about 30 seconds. With your own domain ShopView shows the DNS records to add at your registrar; the agent returns them and changes nothing at the registrar. By default you confirm each call; you can switch that off for this tool.
MCP callshopview_write → publish_shop_website
REST endpointPOST https://cotlet.dev/api/v1/shopview/shop-website/publish
| Name | Type | Description |
|---|---|---|
| domain string | string | Your own domain. Leave empty for the free URL. |
{
"url": "yourshop.netlify.app",
"domain": null,
"published": true
} Read only. Sales, efficiency, timesheets, advisors, A/R, sales tax, work in progress and inventory value.
Under Reports, Performance. The longest open jobs come first, so aging work shows at the top. It changes nothing and runs without asking.
MCP callshopview_read → view_wip_report
REST endpointGET https://cotlet.dev/api/v1/shopview/wip-reports/view
| Name | Type | Description |
|---|---|---|
| group string | string | One of `partially_completed`, `not_started`, `completed`. |
{
"group": "partially_completed",
"jobs": [
{
"work_order": "WO 1029",
"days_open": 12,
"earned": 1840,
"remaining": 960
}
]
} Each row is an invoice closed in the range: customer, invoice, billing efficiency, effective labor rate and labor, parts and profit figures, with shop totals at the bottom. It changes nothing and runs without asking.
MCP callshopview_read → view_sales_report
REST endpointGET https://cotlet.dev/api/v1/shopview/sales-reports/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
{
"from": "2026-11-01",
"to": "2026-11-15",
"invoices": 38,
"total_sales": 61240,
"billing_efficiency": "104%"
} Tech Hours against Actual Clocked Hours, per technician. The Completed tab counts only work orders completed as a whole. It changes nothing and runs without asking.
MCP callshopview_read → view_technician_efficiency
REST endpointGET https://cotlet.dev/api/v1/shopview/technician-efficiencies/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
| tab string | string | One of `invoiced`, `completed`. |
{
"tab": "invoiced",
"technicians": [
{
"name": "Tech A",
"tech_hours": 62,
"clocked": 58
},
{
"name": "Tech B",
"tech_hours": 47,
"clocked": 51
}
]
} Total billable clocked hours set against billed hours, for the whole shop. It changes nothing and runs without asking.
MCP callshopview_read → view_shop_efficiency
REST endpointGET https://cotlet.dev/api/v1/shopview/shop-efficiencies/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
{
"from": "2026-11-01",
"to": "2026-11-15",
"clocked_billable": 210,
"billed": 219
} Date, technician, work order and line or department, punch times, hours and comment. Entries post after the technician clocks out. It changes nothing and runs without asking.
MCP callshopview_read → view_timesheet_activities
REST endpointGET https://cotlet.dev/api/v1/shopview/timesheet-activities/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
| technician string | string | Only this technician. |
{
"punches": [
{
"date": "2026-11-14",
"technician": "Tech A",
"work_order": "WO 1042",
"in": "07:02",
"out": "10:31",
"hours": 3.48
}
]
} One row per invoice closed by an advisor: days open, hours worked and invoiced, and sales. It changes nothing and runs without asking.
MCP callshopview_read → view_advisor_analysis
REST endpointGET https://cotlet.dev/api/v1/shopview/advisor-analysis/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
{
"advisors": [
{
"name": "Advisor A",
"invoices": 21,
"hours_invoiced": 96
}
]
} Under Reports, Finance. The Collection report groups open invoices and credits past their due date by customer. It changes nothing and runs without asking.
MCP callshopview_read → view_ar_reports
REST endpointGET https://cotlet.dev/api/v1/shopview/ar-reports/view
| Name | Type | Description |
|---|---|---|
| report string required | string | One of `aging_summary`, `aging_detail`, `collection`. |
{
"report": "report"
} {
"report": "aging_summary",
"current": 18400,
"days_31_60": 6200,
"days_61_90": 2480,
"over_90": 0
} Under Reports, Finance: each tax applied, with a total for the period. ShopView can export it to CSV. It changes nothing and runs without asking.
MCP callshopview_read → view_sales_tax_collected
REST endpointGET https://cotlet.dev/api/v1/shopview/sales-tax-collecteds/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO start date of the report range. |
| to string | string | ISO end date. Defaults to today. |
{
"from": "2026-10-01",
"to": "2026-10-31",
"taxes": [
{
"tax": "State sales tax",
"collected": 3120
}
]
} Under Reports, Parts. ShopView snapshots the value nightly at each location. It changes nothing and runs without asking.
MCP callshopview_read → view_inventory_value
REST endpointGET https://cotlet.dev/api/v1/shopview/inventory-values/view
| Name | Type | Description |
|---|---|---|
| by string | string | One of `category`, `vendor`. |
| date string | string | Earlier ISO date, back to 2026-08-24 when snapshots began. |
{
"by": "category",
"rows": [
{
"category": "Brakes",
"cost": 8420,
"sell": 12630
}
]
} Your signed-in ShopView browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 37 ShopView tools. The session cookie stays in the Cloud Browser.
The shops and records your ShopView role opens. A service desk login sees its own shop.
Staff roles and permissions, ShopView settings, the QuickBooks Online and IBS connections, and ShopPay Terminal readers.
You sign in again yourself, in the same Cloud Browser.
Turn ShopView off for agents, reset the browser, or change your ShopView password.
Cotlet never sees or stores your password: you type it into ShopView yourself, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Line, technician or lead change | Call the same tool again with the earlier values |
| Invoice | Void its payments, then reverse it with void_payment_reverse_invoice |
| Portal payment | Refund it in the portal with refund_portal_payment |
| Published website | Edit the draft and publish again |
All 26 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 11 read tools, reports, outstanding invoices and the audit log, run at once.
{
"name": "take_deposit",
"arguments": {
"work_order": "WO 1042",
"amount": 1500,
"method": "Card"
}
} curl -X POST https://cotlet.dev/api/v1/shopview/deposit/take \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"work_order":"WO 1042","amount":1500,"method":"Card"}' {
"work_order": "WO 1042",
"deposit": 1500,
"method": "Card",
"applies_to": "the invoice when created",
"saved": true
} The example records a $1,500 card deposit before parts are ordered. Automatic late fees work the same way once set: ShopView's own example charges $20 every 30 days on a $1,000 invoice at 2%, always on the original amount. A script or n8n flow can call /api/v1/shopview over REST with the same key and price, in JSON. Failed calls are free.
About $27 a monthfor a shop writing about 40 work orders a month, 4,580 credits. Your ShopView plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning WIP and unpaid invoices | 2 × 22 | 440 |
| New work orders with lines and techs | 2 × 40 | 800 |
| Complete and invoice finished jobs | 2 × 40 | 800 |
| Purchase orders and receiving | 1 × 40 | 400 |
| Payments and deposits | 1 × 50 | 500 |
| Friday efficiency and sales reports | 3 × 4 | 120 |
| Month-end A/R and sales tax | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 308 calls | 4,580 |
The smallest pack, 5,000 credits for $29, covers this month. A multi-site operation with more work orders uses more calls.
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 |
|---|---|---|
| ShopView open API | Named on the Enterprise page for connecting other systems. | No public docs; you talk to the team, then write and host the client. |
| QuickBooks Online sync | Deposits and edited vendor invoices sync to your books. | Accounting only, not a route for an AI agent. |
| IBS integration | Fleet billing through Interstate Billing Service. | Billing only. |
| By hand | Open each work order in ShopView and click through. | One screen at a time, only while someone is at the desk. |
If you get access to the ShopView API and it covers your job, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script working in ShopView today, from your own login, with nothing to host.
Behind Cotlet is Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273) and building software since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the ShopView tools: contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=shopview, turn on ShopView under Integrations in the console and sign in at https://app.shopview.com/login in your Cloud Browser. Then connect your AI agent and ask it about your open work orders. The trial needs no card.
ShopView's Enterprise page says it offers an open API for connecting other systems, but no public API documentation or self-serve key was found, and that page leads to its team (checked 16 Nov 2026). No ShopView MCP server or official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in ShopView account.
No. ShopPay Terminals need a physical Stripe reader at the counter. The agent can record payments, take deposits and refund portal payments.
No. ShopView runs its own QuickBooks Online integration. Deposits and edited vendor invoices sync through it as ShopView describes; customer credits stay in ShopView.
The user whose work the agent should do. ShopView sets access by role and by shop, and some actions have their own permission: deposits, for example, are on by default for owners, administrators, service and parts managers and service advisors.
Only in how it is called. Both carry the same 37 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 ShopView.
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