ShopView API and MCP server Let your AI agent handle the service desk paperwork.

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.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with ShopView

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.

ShopView Cloud Browser

37 tools Read and write

Heavy-duty repair

What can your AI agent do in ShopView? Service desk, parts counter and the reports behind them.

  • Write up a work order with lines and parts

  • Assign techs and change the lead

  • Complete and invoice finished jobs

  • Record payments and take deposits

  • Order and receive parts by vendor

  • Read WIP, efficiency and A/R reports

API without public docs, no MCP

Does ShopView have an MCP server or an API? The official ShopView routes, checked 16 November 2026.

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.

  • ShopView syncs with QuickBooks Online and runs fleet billing through its Interstate Billing Service (IBS) integration.
  • shopview.com/mcp answers 404.
  • Sign-in is at app.shopview.com with email and password.
The ShopView API, working by hand and Cotlet compared
What you need ShopView APIBy handCotlet
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

Set up once

How does the ShopView MCP server work? The ShopView MCP server by Cotlet: your agent works in your own ShopView account.

  1. 1Sign in to ShopView

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the desk work

    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

Any MCP client

How to connect ShopView to your AI agent

  1. 1

    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.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    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.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude
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
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: shopview_read
11 read, 26 write

All 37 ShopView MCP tools

One tool per owner workflow in the ShopView Help Center. The reports, outstanding invoices and audit log only read; every other tool asks first.

Work orders and technicians10

From the first line to completion: parts, technicians, the lead, the authorizer, fees and discounts, and the punch clock.

  • add_work_order_lines Create a work order for a customer and asset, or add labor lines and parts to an open one. writeAsks first

    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

    Parameters

    Parameters: add_work_order_lines
    NameTypeDescription
    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.

    Example input

    {
      "lines": "lines"
    }

    Example response

    {
      "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
    }
  • assign_technicians Assign up to five technicians to a work order line. writeAsks first

    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

    Parameters

    Parameters: assign_technicians
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "work order",
      "line": "line",
      "technicians": "technicians"
    }

    Example response

    {
      "work_order": "WO 1042",
      "line": "Replace front brake pads and rotors",
      "technicians": [
        "Tech A"
      ],
      "saved": true
    }
  • change_lead_technician Make another technician, or nobody, the lead on a work order. writeAsks first

    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

    Parameters

    Parameters: change_lead_technician
    NameTypeDescription
    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`.

    Example input

    {
      "work_order": "work order",
      "technician": "technician"
    }

    Example response

    {
      "work_order": "WO 1042",
      "lead": "Tech B",
      "shifts": "keep",
      "saved": true
    }
  • split_work_order Split a work order in two, as ShopView's split action does. writeAsks first

    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

    Parameters

    Parameters: split_work_order
    NameTypeDescription
    work_order string required string Work order number, as ShopView shows it.
    lines array required array Lines that move to the new work order.

    Example input

    {
      "work_order": "work order",
      "lines": "lines"
    }

    Example response

    {
      "work_order": "WO 1042",
      "new_work_order": "WO 1043",
      "moved_lines": 1,
      "saved": true
    }
  • set_authorizer Set the Authorizer of a work order or part sale from the customer's contacts. writeAsks first

    Optional field in the customer card, under Contact and Phone; it prints on the estimate and the invoice. Only contacts with Approves Work turned on can be picked. By default you confirm each call; you can switch that off for this tool.

    MCP callshopview_write → set_authorizer

    REST endpointPUT https://cotlet.dev/api/v1/shopview/authorizer

    Parameters

    Parameters: set_authorizer
    NameTypeDescription
    work_order string required string Work order number, as ShopView shows it.
    contact string required string Customer contact with Approves Work turned on.

    Example input

    {
      "work_order": "work order",
      "contact": "contact"
    }

    Example response

    {
      "work_order": "WO 1042",
      "authorizer": "Fleet Manager A",
      "saved": true
    }
  • view_audit_log Read the Audit Log of a work order: status changes and line history. read

    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

    Parameters

    Parameters: view_audit_log
    NameTypeDescription
    work_order string required string Work order number, as ShopView shows it.

    Example input

    {
      "work_order": "work order"
    }

    Example response

    {
      "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"
        }
      ]
    }
  • complete_work_order Complete a work order, filling the details your shop requires. writeAsks first

    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

    Parameters

    Parameters: complete_work_order
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "work order"
    }

    Example response

    {
      "work_order": "WO 1042",
      "status": "Completed",
      "next": "Ready to invoice",
      "saved": true
    }
  • add_work_order_fee Add a fee to a work order, a labor line or one part. writeAsks first

    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

    Parameters

    Parameters: add_work_order_fee
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "work order",
      "level": "level",
      "name": "Jane Doe",
      "amount": 1
    }

    Example response

    {
      "work_order": "WO 1042",
      "fee": "Freight",
      "amount": 85,
      "taxable": false,
      "saved": true
    }
  • apply_discount Discount a whole work order or one line item. writeAsks first

    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

    Parameters

    Parameters: apply_discount
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "work order",
      "amount": 1
    }

    Example response

    {
      "work_order": "WO 1042",
      "discount": "10%",
      "applies_to": "whole work order",
      "saved": true
    }
  • clock_in_out Clock the signed-in user in or out of a work order line or a department. writeAsks first

    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

    Parameters

    Parameters: clock_in_out
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "action": "in",
      "work_order": "WO 1042",
      "line": "Replace front brake pads and rotors",
      "at": "2026-11-16 07:02"
    }

Invoices and payments8

Invoicing on the customer's credit terms, payments, deposits, credits and late fees. Portal payments are refunded in the portal.

  • invoice_work_order Invoice a completed work order, with or without taking payment now. writeAsks first

    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

    Parameters

    Parameters: invoice_work_order
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "work order"
    }

    Example response

    {
      "work_order": "WO 1042",
      "invoice": "INV 2210",
      "total": 2480,
      "terms": "Net 30",
      "status": "Invoiced"
    }
  • record_payment Record a full or partial payment on an invoice and get the receipt. writeAsks first

    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

    Parameters

    Parameters: record_payment
    NameTypeDescription
    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.

    Example input

    {
      "customer": "customer",
      "invoice": "invoice",
      "amount": 1,
      "method": "method"
    }

    Example response

    {
      "customer": "Example Freight",
      "invoice": "INV 2210",
      "paid": 1000,
      "balance": 1480,
      "receipt": "Ready to print"
    }
  • void_payment_reverse_invoice Delete a payment, then reverse the invoice back to an open work order. writeAsks first

    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

    Parameters

    Parameters: void_payment_reverse_invoice
    NameTypeDescription
    work_order string required string Work order number, as ShopView shows it.
    step string required string One of `void_payment`, `reverse_invoice`.

    Example input

    {
      "work_order": "work order",
      "step": "step"
    }

    Example response

    {
      "work_order": "WO 1042",
      "payment_voided": true,
      "invoice_reversed": true,
      "status": "Completed"
    }
  • refund_portal_payment Refund or credit a payment made through the Customer Portal (ShopPay, Stripe). writeAsks first

    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

    Parameters

    Parameters: refund_portal_payment
    NameTypeDescription
    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.

    Example input

    {
      "customer": "customer",
      "invoice": "invoice"
    }

    Example response

    {
      "customer": "Example Freight",
      "invoice": "INV 2198",
      "refunded": 240,
      "via": "Customer Portal"
    }
  • take_deposit Record a customer deposit on a work order before it is invoiced. writeAsks first

    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

    Parameters

    Parameters: take_deposit
    NameTypeDescription
    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.

    Example input

    {
      "work_order": "WO 1042",
      "amount": 1500,
      "method": "Card"
    }

    Example response

    {
      "work_order": "WO 1042",
      "deposit": 1500,
      "method": "Card",
      "applies_to": "the invoice when created",
      "saved": true
    }
  • add_customer_credit Add a credit to a customer's account with a note. writeAsks first

    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

    Parameters

    Parameters: add_customer_credit
    NameTypeDescription
    customer string required string Customer name, as on the Customers page.
    amount number required number Credit amount.
    note string string Reason, for your records.

    Example input

    {
      "customer": "customer",
      "amount": 1
    }

    Example response

    {
      "customer": "Example Freight",
      "credit": 150,
      "note": "Goodwill on comeback",
      "saved": true
    }
  • configure_late_fees Turn automatic late fees on overdue invoices on or off and set the rate. writeAsks first

    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

    Parameters

    Parameters: configure_late_fees
    NameTypeDescription
    enabled boolean required boolean On or off.
    rate number number Late fee percentage of the original invoice amount.

    Example input

    {
      "enabled": true
    }

    Example response

    {
      "enabled": true,
      "rate": 2,
      "grace_days": 30,
      "cycle_days": 30,
      "saved": true
    }
  • view_outstanding_invoices List invoiced but unpaid work orders, or a customer's outstanding invoices for a statement. read

    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

    Parameters

    Parameters: view_outstanding_invoices
    NameTypeDescription
    customer string string Only this customer. Leave empty for all.

    Example response

    {
      "invoices": [
        {
          "work_order": "WO 1031",
          "customer": "Example Freight",
          "amount": 4915,
          "status": "Invoiced"
        },
        {
          "work_order": "WO 1036",
          "customer": "Sample Haulage",
          "amount": 2480,
          "status": "Invoiced"
        }
      ]
    }

Parts and vendors7

Counter sales, purchase orders, receiving by vendor, vendor invoices, returns and the price matrix.

  • create_part_sale Create a part sale for a customer, or a Counter Sale for a walk-in. writeAsks first

    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

    Parameters

    Parameters: create_part_sale
    NameTypeDescription
    customer string required string Customer, or `Counter Sale`.
    parts array required array Inventory or special-order parts with quantities.

    Example input

    {
      "customer": "customer",
      "parts": "parts"
    }

    Example response

    {
      "part_sale": "PS 318",
      "customer": "Counter Sale",
      "parts": [
        {
          "part": "Air filter",
          "quantity": 2
        }
      ],
      "total": 96,
      "saved": true
    }
  • create_purchase_order Create a purchase order for a vendor with parts, quantities and costs. writeAsks first

    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

    Parameters

    Parameters: create_purchase_order
    NameTypeDescription
    vendor string required string Vendor, required.
    parts array required array Each part with quantity and cost.

    Example input

    {
      "vendor": "vendor",
      "parts": "parts"
    }

    Example response

    {
      "purchase_order": "PO 774",
      "vendor": "Example Truck Parts",
      "parts": 3,
      "total": 612,
      "saved": true
    }
  • receive_purchase_orders Receive one or many purchase orders, in full or in part. writeAsks first

    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

    Parameters

    Parameters: receive_purchase_orders
    NameTypeDescription
    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.

    Example input

    {
      "purchase_orders": "purchase orders"
    }

    Example response

    {
      "received": [
        "PO 774",
        "PO 775"
      ],
      "vendors": 2,
      "partial": false
    }
  • edit_vendor_invoice Correct a received vendor invoice: its details or existing lines. writeAsks first

    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

    Parameters

    Parameters: edit_vendor_invoice
    NameTypeDescription
    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.

    Example input

    {
      "vendor_invoice": "vendor invoice",
      "changes": "changes"
    }

    Example response

    {
      "vendor_invoice": "EP-55120",
      "changed": [
        "cost on line 2"
      ],
      "synced": true
    }
  • manage_vendors List vendors, add one, or delete one. writeAsks first

    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

    Parameters

    Parameters: manage_vendors
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "vendor": "Example Truck Parts",
      "tax": "Exempt",
      "credit_terms": "Net 30",
      "saved": true
    }
  • return_special_order_part Mark a special-order part as returned, then put it in inventory or send it back to the vendor. writeAsks first

    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

    Parameters

    Parameters: return_special_order_part
    NameTypeDescription
    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`.

    Example input

    {
      "work_order": "work order",
      "part": "part",
      "reason": "reason",
      "outcome": "outcome"
    }

    Example response

    {
      "work_order": "WO 1042",
      "part": "Brake chamber",
      "outcome": "to_vendor",
      "saved": true
    }
  • manage_price_matrix Read or change the cost ranges, markups and margins that price your parts. writeAsks first

    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

    Parameters

    Parameters: manage_price_matrix
    NameTypeDescription
    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.

    Example input

    {
      "matrix": "matrix"
    }

    Example response

    {
      "matrix": "Default",
      "rules": [
        {
          "from": 10.01,
          "to": 100,
          "markup": 40
        }
      ],
      "saved": true
    }

Assets and the shop website3

Decode a VIN onto the customer's asset. Edit the website draft, then publish it.

  • add_asset_vin Add a vehicle to a customer and decode its VIN. writeAsks first

    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

    Parameters

    Parameters: add_asset_vin
    NameTypeDescription
    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.

    Example input

    {
      "customer": "customer",
      "vin": "vin"
    }

    Example response

    {
      "customer": "Example Freight",
      "vin": "1XKAD49X0EJ000000",
      "decoded": {
        "make": "Example make",
        "model": "Example model",
        "year": 2014
      },
      "saved": true
    }
  • edit_shop_website Change text, services, repairs, reviews, photos and design of your ShopView website. writeAsks first

    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

    Parameters

    Parameters: edit_shop_website
    NameTypeDescription
    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.

    Example input

    {
      "page": "page",
      "changes": "changes"
    }

    Example response

    {
      "page": "Home",
      "changed": [
        "hero text",
        "services"
      ],
      "published": false
    }
  • publish_shop_website Publish the website on its free URL or your own domain. writeAsks first

    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

    Parameters

    Parameters: publish_shop_website
    NameTypeDescription
    domain string string Your own domain. Leave empty for the free URL.

    Example response

    {
      "url": "yourshop.netlify.app",
      "domain": null,
      "published": true
    }

Reports9

Read only. Sales, efficiency, timesheets, advisors, A/R, sales tax, work in progress and inventory value.

  • view_wip_report List every open job with the money earned and still to do. read

    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

    Parameters

    Parameters: view_wip_report
    NameTypeDescription
    group string string One of `partially_completed`, `not_started`, `completed`.

    Example response

    {
      "group": "partially_completed",
      "jobs": [
        {
          "work_order": "WO 1029",
          "days_open": 12,
          "earned": 1840,
          "remaining": 960
        }
      ]
    }
  • view_sales_report Read the Sales Report for a date range, invoice by invoice with totals. read

    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

    Parameters

    Parameters: view_sales_report
    NameTypeDescription
    from string string ISO start date of the report range.
    to string string ISO end date. Defaults to today.

    Example response

    {
      "from": "2026-11-01",
      "to": "2026-11-15",
      "invoices": 38,
      "total_sales": 61240,
      "billing_efficiency": "104%"
    }
  • view_technician_efficiency Compare each technician's given hours with the hours they clocked. read

    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

    Parameters

    Parameters: view_technician_efficiency
    NameTypeDescription
    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`.

    Example response

    {
      "tab": "invoiced",
      "technicians": [
        {
          "name": "Tech A",
          "tech_hours": 62,
          "clocked": 58
        },
        {
          "name": "Tech B",
          "tech_hours": 47,
          "clocked": 51
        }
      ]
    }
  • view_shop_efficiency Read the shop-wide billing efficiency for a date range. read

    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

    Parameters

    Parameters: view_shop_efficiency
    NameTypeDescription
    from string string ISO start date of the report range.
    to string string ISO end date. Defaults to today.

    Example response

    {
      "from": "2026-11-01",
      "to": "2026-11-15",
      "clocked_billable": 210,
      "billed": 219
    }
  • view_timesheet_activities List every punch in and out for a date range. read

    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

    Parameters

    Parameters: view_timesheet_activities
    NameTypeDescription
    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.

    Example response

    {
      "punches": [
        {
          "date": "2026-11-14",
          "technician": "Tech A",
          "work_order": "WO 1042",
          "in": "07:02",
          "out": "10:31",
          "hours": 3.48
        }
      ]
    }
  • view_advisor_analysis Read each service advisor's invoices, hours and sales for a date range. read

    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

    Parameters

    Parameters: view_advisor_analysis
    NameTypeDescription
    from string string ISO start date of the report range.
    to string string ISO end date. Defaults to today.

    Example response

    {
      "advisors": [
        {
          "name": "Advisor A",
          "invoices": 21,
          "hours_invoiced": 96
        }
      ]
    }
  • view_ar_reports Read the A/R Aging Summary, Aging Detail or Collection report. read

    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

    Parameters

    Parameters: view_ar_reports
    NameTypeDescription
    report string required string One of `aging_summary`, `aging_detail`, `collection`.

    Example input

    {
      "report": "report"
    }

    Example response

    {
      "report": "aging_summary",
      "current": 18400,
      "days_31_60": 6200,
      "days_61_90": 2480,
      "over_90": 0
    }
  • view_sales_tax_collected Read the tax collected on paid and partly paid invoices for a period. read

    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

    Parameters

    Parameters: view_sales_tax_collected
    NameTypeDescription
    from string string ISO start date of the report range.
    to string string ISO end date. Defaults to today.

    Example response

    {
      "from": "2026-10-01",
      "to": "2026-10-31",
      "taxes": [
        {
          "tax": "State sales tax",
          "collected": 3120
        }
      ]
    }
  • view_inventory_value Read inventory value at cost and sell price, by category or vendor. read

    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

    Parameters

    Parameters: view_inventory_value
    NameTypeDescription
    by string string One of `category`, `vendor`.
    date string string Earlier ISO date, back to 2026-08-24 when snapshots began.

    Example response

    {
      "by": "category",
      "rows": [
        {
          "category": "Brakes",
          "cost": 8420,
          "sell": 12630
        }
      ]
    }
Encrypted, revocable

Who can see my ShopView session, and how do I revoke it?

  • What we store

    Your signed-in ShopView browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 37 ShopView tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The shops and records your ShopView role opens. A service desk login sees its own shop.

  • What no tool touches

    Staff roles and permissions, ShopView settings, the QuickBooks Online and IBS connections, and ShopPay Terminal readers.

  • If ShopView signs you out

    You sign in again yourself, in the same Cloud Browser.

  • How to cut access

    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).

26 tools ask first

Approvals, undo and mistakes No customer is invoiced, charged or refunded until you say so.

  1. 01 Read the work order Status must allow a deposit.
  2. 02 Show you the deposit Work order, amount and method.
  3. 03 Record after your OK take_deposit saves it on the Finance tab.
  4. 04 Applied at invoicing ShopView applies it to the invoice by itself.
Fixing a ShopView write that went wrong
ActionHow to put it right
Line, technician or lead changeCall the same tool again with the earlier values
InvoiceVoid its payments, then reverse it with void_payment_reverse_invoice
Portal paymentRefund it in the portal with refund_portal_payment
Published websiteEdit 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.

MCP call
{
  "name": "take_deposit",
  "arguments": {
    "work_order": "WO 1042",
    "amount": 1500,
    "method": "Card"
  }
}
REST
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"}'
Response
{
  "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.

Pay per call

How much does the ShopView MCP server cost?

About $27 a monthfor a shop writing about 40 work orders a month, 4,580 credits. Your ShopView plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Morning WIP and unpaid invoices2 × 22440
New work orders with lines and techs2 × 40800
Complete and invoice finished jobs2 × 40800
Purchase orders and receiving1 × 40400
Payments and deposits1 × 50500
Friday efficiency and sales reports3 × 4120
Month-end A/R and sales tax2 × 120
Cloud Browser, 30 days1,500
Total308 calls4,580

The smallest pack, 5,000 credits for $29, covers this month. A multi-site operation with more work orders uses more calls.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your ShopView plan, role and shop settings apply as they are

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

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.

Other options

ShopView MCP server: other ways to connect What each route does for a repair shop, and where it stops.

Other ways to work with ShopView, checked 16 Nov 2026
OptionWhat it doesWhere it stops
ShopView open APINamed on the Enterprise page for connecting other systems.No public docs; you talk to the team, then write and host the client.
QuickBooks Online syncDeposits and edited vendor invoices sync to your books.Accounting only, not a route for an AI agent.
IBS integrationFleet billing through Interstate Billing Service.Billing only.
By handOpen 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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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.

ShopView MCP server: questions

How do I get access?

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.

Does ShopView have an API?

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.

Can the agent take a card payment on a ShopPay Terminal?

No. ShopPay Terminals need a physical Stripe reader at the counter. The agent can record payments, take deposits and refund portal payments.

Does Cotlet change my QuickBooks Online sync?

No. ShopView runs its own QuickBooks Online integration. Deposits and edited vendor invoices sync through it as ShopView describes; customer credits stay in ShopView.

Which ShopView user should I sign in with?

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.

Is the MCP server different from the REST API?

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.

Is Cotlet affiliated with ShopView?

No. Cotlet is independent and not affiliated with ShopView.

Hand the next ShopView write-up to your agent.

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