Local services & SaaS
Jobber
Quotes, jobs, invoices and clients in your Jobber account.
14 endpoints
Skimmer gives API keys to Enterprise accounts only and runs no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Skimmer MCP server with 30 tools that ChatGPT and Claude use in your own Skimmer web account, on any tier. Quotes, broadcasts and anything that reaches a customer or a tech wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Skimmer. Skimmer is a trademark of its owner. If Skimmer's own integrations cover what you need, use them first.
30 tools Read and write
Skimmer has a public API and webhooks. Enterprise accounts create their own API keys in the Integrations Center; software vendors get access after Skimmer approves them as partners. No Skimmer MCP server and no official ChatGPT or Claude connector was verified.
| What you need | Skimmer API | Skimmer Zapier app | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server | Zaps, not chat | Hosted MCP server |
| Available on your tier | Enterprise only | Scaling Up and above | Any tier, your login |
| Quotes, routes, service notes, broadcasts | Endpoints not verified | Customers, products, work orders | 30 tools, writes after your OK |
| Run from n8n or a script | Your own code | Inside Zapier | REST, same key |
Checked 16 Nov 2026. Sources: Help: Integrations Center (API keys, webhooks) · Software Vendor Partners · Help: Zapier Integration · Skimmer pricing · Help: Add, Edit, or Delete a Customer · Help: Import Customers From a File · Help: Manage Service Rates in Bulk · Help: Customize Tags · Help: Add a Service Location · Help: Body of Water · Help: Service Types to Bodies of Water · Help: Manage Pool Equipment · Help: Build a Pool Service Route · Help: Manage Route Assignments · Help: Route Dashboard · Help: The Schedule, Calendar · Help: Quotes, Create and Send · Help: Quotes, Related Invoices · Help: Quotes, Related Work Orders · Help: Jobs, Create and View · Help: Jobs, Manage Work · Help: Jobs, Manage Invoices · Help: Work Orders · Help: Recurring Work Orders · Help: Work Order Reminders · Help: Work Order Types · Help: Pool Service History · Help: Service Notes and Issues · Help: Service Checklist · Help: Readings and Dosages · Help: Shopping List · Help: Products · Help: Auto Invoicing by Customer Date · Help: Suspend Service When Payment Is Overdue · Help: Service Emails · Help: Skipped Stops · Help: Broadcast Emails · Help: Marketing Suite · Help: Send Alerts to Your Techs · Help: Directory of Skimmer Reports
Once, in a browser we host for you.
One address in its settings.
Draft a repair quote, then approve it.
Your agent works in your own signed-in Cloud Browser. Writes, and anything that reaches a customer or a tech, wait for your OK. Who can see your session
Sign in to Skimmer in a Cloud Browser. Open app.getskimmer.com in your Cotlet Cloud Browser and sign in with your own Skimmer web user.
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.
Skimmer shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Skimmer on after connecting? Refresh the connector and the 30 Skimmer tools appear.
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: skimmer_read One tool per web workflow in the Skimmer Help Center. Most take an `action`: `list` and `get` only read, the other actions write and ask first.
Read the Route Dashboard or the calendar, make permanent route changes, or move stops for one day.
Returns each tech's stops in route order with their state: done, not recorded yet, or skipped (Skimmer highlights skipped stops in orange). The calendar view returns one route summary per person and day with its estimated duration. Nothing is changed.
MCP callskimmer_read → view_schedule
REST endpointGET https://cotlet.dev/api/v1/skimmer/schedules/view
| Name | Type | Description |
|---|---|---|
| view string | string | `route_dashboard` (default) or `calendar`. The calendar needs Scaling Up or above. |
| date string | string | ISO date. With `week: true`, the week that holds it. |
| week boolean | boolean | Read the whole week instead of one day. |
| tech string | string | One tech by name. Leave empty for all routes. |
{
"date": "2026-11-17",
"routes": [
{
"tech": "Tech A",
"stops": 14,
"done": 9,
"skipped": 1
},
{
"tech": "Tech B",
"stops": 12,
"done": 12,
"skipped": 0
}
]
} These are permanent changes, made where Skimmer makes them (Route Builder and Route Assignments). One-time moves go through move_scheduled_work. `optimize` reorders up to 25 stops and needs Scaling Up or Enterprise. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_route_assignments
REST endpointPOST https://cotlet.dev/api/v1/skimmer/route-assignments/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `move`, `change_frequency`, `end`, `optimize`. `list` and `get` only read. |
| tech string | string | Tech name. |
| day string | string | Day of the week. |
| customer string | string | For `add`: customer and location. |
| frequency string | string | How often the stop is serviced, as Skimmer offers it. |
| starting_on string | string | ISO date the change takes effect. |
| stop_after string | string | ISO end date, or empty for no end. |
{
"action": "action"
} {
"tech": "Tech A",
"day": "Tuesday",
"customer": "Example Homeowner",
"frequency": "Weekly",
"starting_on": "2026-11-18",
"saved": true
} Techs see moved stops on their phones, so the agent names the stops, the techs and the dates before it saves. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → move_scheduled_work
REST endpointPOST https://cotlet.dev/api/v1/skimmer/scheduled-work/move
| Name | Type | Description |
|---|---|---|
| from_tech string required | string | Tech whose stops move. |
| date string required | string | ISO date of the stops. |
| customers array | array | Stops to move. Leave empty to move the whole day. |
| to_tech string required | string | Tech who takes them. |
| to_date string required | string | ISO date. |
| permanent boolean | boolean | False (default) for a one-time move. |
{
"from_tech": "from tech",
"date": "date",
"to_tech": "to tech",
"to_date": "to date"
} {
"moved": 6,
"from_tech": "Tech A",
"to_tech": "Tech B",
"to_date": "2026-11-19",
"permanent": false
} Tech alerts need Scaling Up or Enterprise and the send permission. They arrive at once, stay in the app for 7 days and cannot be replied to or recalled. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → send_tech_alert
REST endpointPOST https://cotlet.dev/api/v1/skimmer/tech-alerts
| Name | Type | Description |
|---|---|---|
| to array required | array | Users by name, or a role to reach every active user with it. |
| title string | string | Up to 50 characters. |
| message string required | string | Up to 500 characters. |
{
"to": "to",
"message": "message"
} {
"to": [
"Tech A",
"Tech B"
],
"title": "Schedule change",
"delivered": 2
} Customer profiles, service locations, bodies of water and the equipment on them.
A quick customer needs a name, a billing address and a location address; the rest can follow. Every new customer starts as a Lead and turns Active when you assign a route or convert their quote to a job. Skimmer does not delete a customer with service or billing history, and this tool deletes none. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_customers
REST endpointPOST https://cotlet.dev/api/v1/skimmer/customers/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `set_as_lead`. `list` and `get` only read. |
| customer string | string | Customer name or code, for `get`, `update` and `set_as_lead`. |
| fields object | object | For `create` and `update`: first_name, last_name, company, display_as_company, customer_code, billing address, phone, email, lead_source, tags. |
| filter object | object | For `list`: status (`lead`, `active`), tags with `has_any`, `has_all` or `has_none`. |
{
"action": "action"
} {
"customer": "Example Homeowner",
"status": "Lead",
"billing_address": "12 Palm Lane, Springfield, AZ 85001",
"saved": true
} Skimmer reads only the first worksheet, needs a row of column names and the same number of columns in every row; a file that breaks its formatting rules does not import. The agent checks those rules and shows you the row count before it uploads. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → import_customers
REST endpointPOST https://cotlet.dev/api/v1/skimmer/customers
| Name | Type | Description |
|---|---|---|
| file_url string required | string | A link the Cloud Browser can download the file from. |
{
"file_url": "https://example.com"
} {
"file": "customers-export.csv",
"rows": 48,
"imported": true
} A service location needs at least one body of water, and a customer profile always keeps one, so the last body of water cannot be deleted. Route assignment can wait; manage_route_assignments adds it later. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_service_locations
REST endpointPOST https://cotlet.dev/api/v1/skimmer/service-locations/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `add_location`, `add_body_of_water`, `update_body_of_water`, `delete_body_of_water`. `list` and `get` only read. |
| customer string required | string | Customer name or customer code, as manage_customers `list` returns it. |
| service_location string | string | Service location, when the customer has more than one. |
| fields object | object | Location: address and access notes. Body of water: name, gallons, baseline_filter_pressure_psi, notes. |
{
"action": "action",
"customer": "customer"
} {
"customer": "Example Homeowner",
"service_location": "12 Palm Lane",
"body_of_water": "Pool",
"gallons": 18000,
"saved": true
} Techs see a new service type at their next stop after it is assigned, and Skimmer suggests assigning at the end of a route day. Techs need Skimmer Pro 12.16 or later. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → set_service_types
REST endpointPUT https://cotlet.dev/api/v1/skimmer/service-types
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `set_default`, `assign`. `list` and `get` only read. |
| body_of_water_type string | string | For `set_default`, for example Pool, Salt Pool or Cold Plunge. |
| service_type string required | string | Service type name, created in Settings > Service Types. |
| customer string | string | For `assign`: the customer whose body of water changes. |
{
"action": "action",
"service_type": "service type"
} {
"body_of_water_type": "Salt Pool",
"service_type": "Weekly salt service",
"saved": true
} Equipment records show techs what is installed and its condition. `list` is the quick way to find every pump marked Poor or Critical before a repair quote. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_equipment
REST endpointPOST https://cotlet.dev/api/v1/skimmer/equipment/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| customer string required | string | Customer name or customer code, as manage_customers `list` returns it. |
| body_of_water string | string | Defaults to the first one. |
| fields object | object | type (Pump, Filter, Heater, Salt System and the other Skimmer types), manufacturer, model, serial_number, condition (`Good`, `Fair`, `Poor`, `Critical`), notes. |
{
"action": "action",
"customer": "customer"
} {
"customer": "Example Homeowner",
"type": "Pump",
"manufacturer": "Hayward",
"condition": "Poor",
"saved": true
} Rates change what customers pay, so the agent lists the customers and the new rate before saving, page by page. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → update_service_rates
REST endpointPATCH https://cotlet.dev/api/v1/skimmer/service-rates
| Name | Type | Description |
|---|---|---|
| customers array | array | Customer names. Leave empty for every customer on the page. |
| rates object required | object | Service rate category and the new option, in Skimmer's labels. |
| page number | number | Page of the list. Skimmer shows up to 100 customers per page and bulk updates one page at a time. |
{
"rates": "rates"
} {
"page": 1,
"customers": 100,
"category": "Weekly service",
"saved": true
} From a repair quote to a job with its work orders and invoices. Quotes need Scaling Up, jobs Scaling Up or Enterprise.
Quotes need Scaling Up or above, and each action follows your user's quote permissions. `send` emails the quote to the customer for approval, so it is a separate call after `create`. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_quotes
REST endpointPOST https://cotlet.dev/api/v1/skimmer/quotes/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`, `mark_approved`, `mark_rejected`. `list` and `get` only read. |
| quote string | string | Quote number, for every action but `list` and `create`. |
| customer string | string | For `create`. |
| lines array | array | For `create`: description, quantity and price per line. |
| expires string | string | ISO expiration date. |
| filter object | object | For `list`: status, customer, start and end date, tags. |
{
"action": "create",
"customer": "Example Homeowner",
"lines": [
{
"description": "Variable speed pump",
"quantity": 1,
"price": 1680
},
{
"description": "Pump install labor",
"quantity": 1,
"price": 650
},
{
"description": "Plumbing fittings",
"quantity": 1,
"price": 150
}
],
"expires": "2026-12-01"
} {
"quote": "Q-1042",
"customer": "Example Homeowner",
"total": 2480,
"status": "Draft",
"expires": "2026-12-01"
} Jobs need Scaling Up or Enterprise. Converting keeps the quote and moves its customer, location, tax rate, line items, work orders and deposit to the job. Status runs Not Started, Active, Work Complete as work orders are scheduled and finished. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_jobs
REST endpointPOST https://cotlet.dev/api/v1/skimmer/jobs/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `convert_quote`, `add_work_order`, `hold`, `close`. `list` and `get` only read. |
| job string | string | Job number, for `get` and the job actions. |
| quote string | string | For `convert_quote`. |
| line_item string | string | For `add_work_order`: the work line item to schedule. |
{
"action": "action"
} {
"job": "J-318",
"quote": "Q-1042",
"status": "Not Started",
"work_orders": 1,
"deposit": "Collected"
} The first tech is the lead who completes the job record. A work order type that emails customers when work is scheduled sends that email on save, so the agent says so first. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_work_orders
REST endpointPOST https://cotlet.dev/api/v1/skimmer/work-orders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `delete`. `list` and `get` only read. |
| work_order string | string | For `get`, `update` and `delete`. |
| type string | string | Work order type, which fills in the defaults. |
| customer string | string | Customer and service location. |
| date string | string | ISO service date. Without a date and tech it saves as Unscheduled. |
| techs array | array | Lead tech first, then up to nine crew techs. |
| price number | number | What the customer pays. |
| labor_cost number | number | Total paid to all assigned techs. |
{
"action": "action"
} {
"work_order": "WO-2207",
"type": "Filter clean",
"customer": "Example Homeowner",
"date": "2026-11-20",
"techs": [
"Tech A"
],
"price": 95,
"status": "Scheduled"
} Recurring work orders need Scaling Up or Enterprise. Skimmer fills ninety days of them ahead, so a type that emails customers on scheduling would email for each one. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_recurring_work_orders
REST endpointPOST https://cotlet.dev/api/v1/skimmer/recurring-work-orders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `end`. `list` and `get` only read. |
| type string | string | Work order type. |
| customer string | string | Customer and service location. |
| tech string | string | Leave empty to keep it in Unscheduled. |
| frequency string | string | How often it recurs. |
| start_date string | string | ISO date. |
| end string | string | ISO end date, or empty for no end. |
{
"action": "action"
} {
"type": "Salt cell clean",
"customer": "Palm Court HOA",
"tech": "Tech B",
"frequency": "Every 3 months",
"start_date": "2026-12-01",
"saved": true
} Reminders let you place the next job yourself instead of on a fixed schedule. `create_work_order` turns a due reminder into a work order with its fields filled in. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_work_order_reminders
REST endpointPOST https://cotlet.dev/api/v1/skimmer/work-order-reminders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `delete`, `create_work_order`. `list` and `get` only read. |
| customer string required | string | Customer name or customer code, as manage_customers `list` returns it. |
| type string | string | A work order type with a recurrence period. |
| last_done string | string | ISO date the work was last done; Skimmer counts forward from it. |
| weeks_ahead number | number | For `list`: 1 to 12 weeks. |
{
"action": "action",
"customer": "customer"
} {
"reminders": [
{
"customer": "Example Homeowner",
"type": "Filter clean",
"due": "2026-12-08"
}
]
} Edits apply to future work orders only. Customer emails on scheduling are off unless you ask for them. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_work_order_types
REST endpointPOST https://cotlet.dev/api/v1/skimmer/work-order-types/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `delete`. `list` and `get` only read. |
| name string required | string | Type name. |
| fields object | object | color, invoice_when_completed, allow_autopay, office_alerts, require_photo, email_customer_when_scheduled, email_when_completed, default price and labor cost. |
{
"action": "action",
"name": "Jane Doe"
} {
"name": "Green pool clean-up",
"invoice_when_completed": true,
"require_photo": true,
"saved": true
} What techs recorded at each stop, the notes they flagged, and the checklist, readings and dosages they work from.
Returns visits by date with readings, dosages, checklist items and tech service notes. Skimmer marks those notes as office notes that customer emails leave out, so read them before you share a history with a customer.
MCP callskimmer_read → view_service_history
REST endpointGET https://cotlet.dev/api/v1/skimmer/service-histories/view
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name or customer code, as manage_customers `list` returns it. |
| service_location string | string | Service location, when the customer has more than one. |
| body_of_water string | string | Pool, spa or other body of water by name. Defaults to the first one. |
| from string | string | ISO date to start from. |
{
"customer": "customer"
} {
"customer": "Example Homeowner",
"body_of_water": "Pool",
"visits": [
{
"date": "2026-11-10",
"readings": {
"Free Chlorine": "3 ppm",
"pH": "7.6"
},
"dosages": {
"Liquid Chlorine": "1 gal"
},
"tech": "Tech A"
}
]
} Notes come from your techs in the field. Marking one resolved changes only its status in Skimmer. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_service_notes
REST endpointPOST https://cotlet.dev/api/v1/skimmer/service-notes/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `resolve`, `reopen`, `set_alert`. `list` and `get` only read. |
| filter object | object | For `list`: tab (`notes`, `issues`), date range, status (`open`, `resolved`), service type, tech, customer. |
| note string | string | Note ID from `list`. |
{
"action": "action"
} {
"notes": [
{
"id": "SN-881",
"customer": "Example Homeowner",
"tech": "Tech A",
"text": "Pump making noise",
"alert": true,
"status": "open"
}
]
} The universal checklist applies to every route stop for every tech; work orders keep their own checklists. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → configure_service_checklist
REST endpointPOST https://cotlet.dev/api/v1/skimmer/service-checklist/configure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `delete`. `list` and `get` only read. |
| description string required | string | What techs see before they swipe it done. |
| description_when_complete string | string | What it reads after, also in service emails. |
| frequency string | string | `every_stop`, or a number of days, weeks, months or years. |
| required boolean | boolean | Must be done before the stop is finished (Scaling Up and Enterprise). |
| photo boolean | boolean | Require a photo. |
{
"action": "action",
"description": "description"
} {
"description": "Empty skimmer baskets",
"description_when_complete": "Emptied skimmer baskets",
"frequency": "every_stop",
"saved": true
} Dosage prices feed what you bill for chemicals, so price changes wait for your OK like every write here. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → configure_readings_dosages
REST endpointPOST https://cotlet.dev/api/v1/skimmer/readings-dosages/configure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add_reading`, `add_dosage`, `update`, `delete`. `list` and `get` only read. |
| description string required | string | For example Free Chlorine or Liquid Chlorine. |
| uom string | string | Unit of measure. |
| values array | array | Values techs pick from, and which one is the default. |
| cost_per_uom number | number | Dosages only. |
| price_per_uom number | number | Dosages only. |
{
"action": "action",
"description": "description"
} {
"dosage": "Liquid Chlorine",
"uom": "gal",
"price_per_uom": 9.5,
"saved": true
} The shopping list of parts and chemicals to buy, and your product catalog with cost and price.
Each item shows its customer, related work order and date added. Parts for a customer come from Skimmer's equipment database. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_shopping_list
REST endpointPOST https://cotlet.dev/api/v1/skimmer/shopping-list/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `update`, `mark_purchased`, `delete`. `list` and `get` only read. |
| customer string | string | For a part tied to a customer's equipment. Leave empty for stock. |
| description string | string | The part, product or chemical. |
| item string | string | Item ID from `list`. |
{
"action": "action"
} {
"items": [
{
"item": "SL-412",
"description": "Pump seal kit",
"customer": "Example Homeowner",
"work_order": "WO-2207",
"added": "2026-11-12"
}
]
} Skimmer gives each product its own ID. A discontinued product stays in the catalog but leaves the selection screens. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_products
REST endpointPOST https://cotlet.dev/api/v1/skimmer/products/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `discontinue`. `list` and `get` only read. |
| name string required | string | Product name. |
| fields object | object | mfg_number, default_description, product_category, invoice_category, cost, markup_type (`None`, `Fixed Amount`, `Percentage`), default_price, taxable. |
{
"action": "action",
"name": "Jane Doe"
} {
"name": "Salt cell, 40k",
"cost": 420,
"markup_type": "Percentage",
"default_price": 546,
"taxable": true,
"saved": true
} Reports, invoice dates, reminders, service emails and broadcasts. Anything that emails customers waits for your OK.
Skimmer's Directory of Reports groups them into invoice, customer, operations, payment and sales tax reports. The tool returns the rows and totals the report shows to your user. Nothing is changed.
MCP callskimmer_read → view_reports
REST endpointGET https://cotlet.dev/api/v1/skimmer/reports/view
| Name | Type | Description |
|---|---|---|
| report string required | string | Report name as Skimmer lists it, for example `AR Aging Summary`, `Invoice Details`, `Sales by Category`, `Labor`, `Tech Performance`, `Customer Statement`. |
| from string | string | ISO start date, for reports with a range. |
| to string | string | ISO end date. |
| customer string | string | For a Customer Statement. |
{
"report": "report"
} {
"report": "AR Aging Summary",
"rows": [
{
"customer": "Palm Court HOA",
"current": 640,
"over_30": 320
},
{
"customer": "Example Homeowner",
"current": 185,
"over_30": 0
}
]
} Auto invoicing must be on. Each day Skimmer invoices the customers due that day for everything billable since their last invoice, with your Auto Invoicing settings; a customer with nothing billable gets no invoice. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → set_customer_invoice_dates
REST endpointPUT https://cotlet.dev/api/v1/skimmer/customer-invoice-dates
| Name | Type | Description |
|---|---|---|
| customers array required | array | Customer names. |
| day string required | string | Day of the month, or `last`. Empty returns them to the company default day. |
{
"customers": "customers",
"day": "day"
} {
"customers": [
"Palm Court HOA"
],
"day": "1",
"saved": true
} Suspension needs Scaling Up or above. A suspended customer's stops are skipped until the account is current, then service resumes by itself; suspended customers still get invoice emails. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → configure_invoice_reminders
REST endpointPOST https://cotlet.dev/api/v1/skimmer/invoice-reminders/configure
| Name | Type | Description |
|---|---|---|
| reminder_days number | number | Send reminder emails this many days after an invoice is due. |
| suspend_after_days number | number | Suspend service after this many days overdue. Empty turns suspension off. |
| suspension_email object | object | subject, header and message of the past-due email, or empty for none. |
{
"reminder_days": 7,
"suspend_after_days": 30,
"suspension_email": true,
"saved": true
} Turning customer emails on reaches every customer in your account, so the agent shows the message first. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → configure_service_emails
REST endpointPOST https://cotlet.dev/api/v1/skimmer/service-emails/configure
| Name | Type | Description |
|---|---|---|
| service_emails object | object | enabled, where_to_send, bcc, subject, header, default_message, footer, included checklist items. |
| skipped_stops object | object | require_reason, reasons, email_office, email_customer, message. |
{
"service_emails": {
"enabled": true
},
"skipped_stops": {
"require_reason": true,
"email_customer": false
},
"saved": true
} Skimmer leaves out customers who unsubscribed. The agent shows you the recipient count and the text; a sent broadcast cannot be recalled. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → send_broadcast_email
REST endpointPOST https://cotlet.dev/api/v1/skimmer/broadcast-emails
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `send`. `list` and `get` only read. |
| recipients string | string | `all_active` or a narrower group Skimmer offers. |
| subject string | string | Email subject. |
| message string | string | Email body. |
{
"action": "action"
} {
"recipients": 212,
"subject": "Winter service hours",
"sent": false
} Marketing Suite is a Skimmer add-on with its own permission. Campaigns go to active customers only by default, and texts only to customers who opted in. By default you confirm each call; you can switch that off for this tool.
MCP callskimmer_write → manage_marketing_campaigns
REST endpointPOST https://cotlet.dev/api/v1/skimmer/marketing-campaigns/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create_segment`, `create_broadcast`, `create_automation`. `list` and `get` only read. |
| request string | string | What the campaign does, in plain words. |
{
"action": "action"
} {
"segments": [
{
"name": "Customers without a filter clean in a year",
"type": "Custom"
}
]
} Your signed-in Skimmer browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 30 Skimmer tools. The session cookie stays in the Cloud Browser.
The customers, routes and billing your Skimmer user's permissions open, on your tier, and nothing more.
Skimmer users and permissions, payment settings, Stripe payouts, refunds and the QuickBooks Online connection.
You sign in again yourself, in the same Cloud Browser.
Disable Skimmer for agents, reset the browser, or change your Skimmer password.
Cotlet never sees or stores your password: you type it 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).
create after your OK. send is its own call, so nothing emails early. | Action | How to put it right |
|---|---|
| Customer fields, tags, route assignments | Call the same tool again with the earlier values |
| A one-time move of stops | move_scheduled_work back to the first tech and date |
| Draft quote, work order | Edit it, or delete the work order with manage_work_orders |
| Sent quote, broadcast or tech alert | Already delivered: follow up with the customer or tech directly |
All 27 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 read tools, the schedule, service history and reports, run at once.
{
"name": "manage_quotes",
"arguments": {
"action": "create",
"customer": "Example Homeowner",
"lines": [
{
"description": "Variable speed pump",
"quantity": 1,
"price": 1680
},
{
"description": "Pump install labor",
"quantity": 1,
"price": 650
},
{
"description": "Plumbing fittings",
"quantity": 1,
"price": 150
}
],
"expires": "2026-12-01"
}
} curl -X POST https://cotlet.dev/api/v1/skimmer/quotes/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","customer":"Example Homeowner","lines":[{"description":"Variable speed pump","quantity":1,"price":1680},{"description":"Pump install labor","quantity":1,"price":650},{"description":"Plumbing fittings","quantity":1,"price":150}],"expires":"2026-12-01"}' {
"quote": "Q-1042",
"customer": "Example Homeowner",
"total": 2480,
"status": "Draft",
"expires": "2026-12-01"
} The example quotes a $1,680 pump, $650 of install labor and $150 of fittings: $2,480, saved as a draft. A cron job or n8n flow can make the same call over REST at /api/v1/skimmer with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a pool company with three techs, 3,560 credits. Your Skimmer plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Evening check of skipped stops and alert notes | 2 × 22 | 440 |
| Work orders and due reminders | 1 × 40 | 400 |
| Repair quote, job and related invoice | 4 × 12 | 480 |
| New customer with pool, equipment and route | 4 × 8 | 320 |
| Covering a tech: move stops, send alert | 3 × 6 | 180 |
| Shopping list and product updates | 1 × 20 | 200 |
| Monday AR Aging review | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 206 calls | 3,560 |
The smallest pack, 5,000 credits for $29, covers this month. More techs and more repair work use 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 |
|---|---|---|
| Skimmer API and webhooks | Keys from the Integrations Center; webhooks for finished stops, work orders, invoices and payments. | Enterprise tier only; you write, host and fix the code. |
| Skimmer Zapier app | Zaps on new customers and products; creates customers, products and work orders. | Scaling Up and above; no quotes, routes or service notes, and no chat. |
| AI Insights in Skimmer Reports | Skimmer's own assistant answers questions about your report data. | Inside Skimmer, read only; no ChatGPT or Claude connector was verified. |
| By hand | Open each customer, route and quote in Skimmer. | One screen at a time, only while someone is at the desk. |
If you are on Enterprise and the API covers your job, use it: it is Skimmer's own route. Cotlet fits when you want ChatGPT, Claude or a script working in Skimmer on any tier, from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Skimmer tools.
Sign up free at https://cotlet.dev/signup?app=skimmer, turn on Skimmer under Integrations in the console and sign in at https://app.getskimmer.com/ in your Cloud Browser. Then connect your AI agent and ask it about today's routes. The trial needs no card.
Skimmer has a public API with webhooks, but only Enterprise accounts can create API keys; software vendors get API access after partner approval (checked 16 Nov 2026). Its Zapier app, included from the Scaling Up tier, covers customers, products and work orders. No Skimmer MCP server and no official ChatGPT or Claude connector was verified. Cotlet does not use that API: it works in your own signed-in Skimmer account.
The tools use the features your tier has. Skimmer documents quotes, the Schedule calendar and overdue suspension from Scaling Up, jobs, recurring work orders, route optimization and tech alerts on Scaling Up and Enterprise, and Marketing Suite as an add-on.
No. Skimmer documents those steps in its mobile app, where your techs record the visit. The tools work in the Skimmer web app your office uses.
An office user whose work the agent should do, such as an admin or route manager. The agent sees only what that user's permissions open, so a user who cannot view quotes gives the agent no quotes either.
Only in how it is called. Both carry the same 30 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 Skimmer.
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