[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# ServiceTrade API and MCP server

> ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). The API covers jobs, appointments, deficiencies and quotes, so the missing piece is the agent layer: you build and host the wrapper yourself.

Job management software for commercial service contractors: scheduling and dispatch, technician mobile app, inspections and deficiencies, online quotes, invoicing and a customer portal.

## What is the ServiceTrade API?

Cotlet's ServiceTrade API exposes 14 endpoints for your own ServiceTrade account: list jobs, get a job, list appointments, list service requests, list deficiencies, list quotes, get a quote, list locations, list technicians, create an appointment, update an appointment, create a quote, submit a quote and add a comment. The list_jobs endpoint returns list jobs filtered by status, location, customer, technician or due date. Each endpoint takes simple JSON inputs like status, cursor or location_id and works both as an operation of the servicetrade_read or servicetrade_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 14 (9 read, 5 write)
- **Updated:** 2026-10-17

ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for ServiceTrade with 14 endpoints (9 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does ServiceTrade have an official API?

ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). The API covers jobs, appointments, deficiencies and quotes, so the missing piece is the agent layer: you build and host the wrapper yourself.

| Task | ServiceTrade official | Cotlet |
|---|---|---|
| List jobs by status, technician or due date | Yes: REST API, GET /job with filters; you write the client | Yes |
| Read appointments and technician schedules | Yes: REST API, GET /appointment | Yes |
| Create and update appointments, assign technicians, release to techs | Yes: REST API and a Zapier action for create and update | Yes |
| List deficiencies by severity and resolution | Yes: REST API, GET /deficiency; Zapier only finds one by number | Yes |
| Create a quote from service requests | Yes: REST API, POST /quote; Zapier has Create Quote | Yes |
| Submit a quote to the customer | Yes: REST API, POST /quote/{id}/submit | Yes |
| Comment on a job, location or quote | Yes: REST API and Zapier for jobs and locations | Yes |
| Use all of this from an AI agent without writing code | No: No official MCP server | Yes |

Sources: [ServiceTrade API documentation](https://api.servicetrade.com/api/docs), [ServiceTrade triggers and actions on Zapier](https://zapier.com/apps/servicetrade/integrations), [ServiceTrade: Field service scheduling software](https://servicetrade.com/products/servicetrade-platform/features/scheduling/), [ServiceTrade: Job quoting software](https://servicetrade.com/products/servicetrade-platform/features/quoting/)

## Quick reference

```text
ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). The API covers jobs, appointments, deficiencies and quotes, so the missing piece is the agent layer: you build and host the wrapper yourself.
Cotlet provides a hosted MCP server and REST API for ServiceTrade: 14 tools (9 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=servicetrade, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    servicetrade_read, servicetrade_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/servicetrade, each operation at its own route, e.g. POST /api/v1/servicetrade/jobs/{job_id}/appointments
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_jobs, get_job, list_appointments, list_service_requests, list_deficiencies, list_quotes, get_quote, list_locations, list_technicians, create_appointment, update_appointment, create_quote, submit_quote, add_comment
Confirm      create_appointment, update_appointment, create_quote, submit_quote, add_comment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/servicetrade-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=servicetrade, requests ServiceTrade in the Cotlet console and creates an API key there.
2. The user signs in to ServiceTrade once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables ServiceTrade for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted ServiceTrade server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to ServiceTrade in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get ServiceTrade only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no ServiceTrade login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following ServiceTrade's terms; Cotlet is not affiliated with ServiceTrade.
```

## What can an AI agent do in ServiceTrade?

Cotlet is best for service contractors and dispatchers who want an AI agent to schedule jobs, release appointments and draft repair quotes without running or fixing a server.

- **[Schedule unscheduled jobs](https://cotlet.dev/integrations/servicetrade-api-mcp-server/schedule-unscheduled-jobs.md)** (runs: daily): "List ServiceTrade jobs with status Unscheduled, find a free technician for each on Monday morning, and create an appointment for them as a draft I can release later." → `list_jobs`, `list_technicians`, `list_appointments`, `get_job`, `create_appointment`
- **[Draft repair quotes from deficiencies](https://cotlet.dev/integrations/servicetrade-api-mcp-server/draft-repair-quotes-from-deficiencies.md)** (runs: weekly): "List ServiceTrade deficiencies found this week that are not on a quote yet, with severity inoperable or deficient. For each one, draft a repair quote from its open service request and show me the list before submitting anything." → `list_deficiencies`, `list_service_requests`, `create_quote`, `submit_quote`
- **[Release appointments to technicians](https://cotlet.dev/integrations/servicetrade-api-mcp-server/release-appointments-to-technicians.md)** (runs: daily): "List tomorrow's ServiceTrade appointments that are scheduled but not released, check each has a technician, and release the ones that do." → `list_appointments`, `get_job`, `update_appointment`
- **Find quotes sent but not answered** (runs: weekly): "List ServiceTrade quotes in status submitted that were sent more than 7 days ago, group them by customer and give me the total value for each." → `list_quotes`, `get_quote`
- **Report completed jobs not yet invoiced** (runs: weekly): "Every Friday, list ServiceTrade jobs with status completed or pending_invoice, grouped by customer, with the date each was completed." → `list_jobs`, `get_job`

## Can ServiceTrade automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a ServiceTrade connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to schedule unscheduled jobs, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/servicetrade/jobs. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/servicetrade/jobs with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to ServiceTrade.

### list_jobs

List jobs filtered by status, location, customer, technician or due date. Access: read. REST: `GET /api/v1/servicetrade/jobs`. MCP: `servicetrade_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One or more of new (shown as Unscheduled), scheduled, canceled, bidding, completed, pending_invoice, sending_invoice, invoiced, closed, comma-separated. |
| `location_id` | integer | no | Only jobs at this location, from list_locations. |
| `customer_id` | integer | no | Only jobs for this customer company. |
| `technician_id` | integer | no | Only jobs with an appointment for this technician, from list_technicians. |
| `due_by_before` | string | no | ISO 8601 date or date-time; only jobs due on or before it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the job number, name, type, status, location, customer and due date, and the number of services still open. The agent sorts by due date itself. A job with status new is shown by ServiceTrade as Unscheduled. What you see follows your role in ServiceTrade.

Example response:

```json
{
  "jobs": [
    {
      "id": 48213,
      "number": 1042,
      "name": "Fire pump test",
      "type": "planned_maintenance",
      "status": "new",
      "display_status": "Unscheduled",
      "location": {
        "id": 5120,
        "name": "Harbor Point Mall"
      },
      "customer": {
        "id": 2211,
        "name": "Harbor Point Properties"
      },
      "due_by": "2026-10-30",
      "open_services": 2
    }
  ],
  "next_cursor": null
}
```

### get_job

Read one job with its services, appointments and notes. Access: read. REST: `GET /api/v1/servicetrade/jobs/{job_id}`. MCP: `servicetrade_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job id from list_jobs. |

Returns the status, location, customer, the services (service requests) with their descriptions and statuses, the current appointment and the technicians on it, and the job notes. Use it right before changing a job to see what another user has done.

Example response:

```json
{
  "id": 48213,
  "number": 1042,
  "name": "Fire pump test",
  "type": "planned_maintenance",
  "status": "new",
  "display_status": "Unscheduled",
  "location": {
    "id": 5120,
    "name": "Harbor Point Mall"
  },
  "services": [
    {
      "id": 77302,
      "description": "Annual fire pump flow test",
      "status": "open"
    }
  ],
  "appointments": [],
  "notes": []
}
```

### list_appointments

List appointments by status, technician, job or time window. Access: read. REST: `GET /api/v1/servicetrade/appointments`. MCP: `servicetrade_read → list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One or more of scheduled, unscheduled, canceled_by_vendor, canceled_by_customer, completed, no_show, comma-separated. |
| `job_id` | integer | no | Only appointments of this job. |
| `technician_id` | integer | no | Only appointments for this technician. |
| `window_from` | string | no | ISO 8601 date or date-time; only appointments whose window starts on or after it. |
| `window_to` | string | no | ISO 8601 date or date-time; only appointments whose window starts on or before it. |
| `released` | boolean | no | true for appointments released to technicians, false for drafts. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each appointment with its status, window, job, location, technicians and whether it is released. Use it to see who is free before booking, or to find drafts to release.

Example response:

```json
{
  "appointments": [
    {
      "id": 90388,
      "status": "scheduled",
      "window_start": "2026-10-26T08:00:00-04:00",
      "window_end": "2026-10-26T11:00:00-04:00",
      "job": {
        "id": 48190,
        "name": "Sprinkler inspection"
      },
      "location": {
        "id": 5133,
        "name": "Delta Plaza"
      },
      "technicians": [
        {
          "id": 3302,
          "name": "Dana Ruiz"
        }
      ],
      "released": false
    }
  ],
  "next_cursor": null
}
```

### list_service_requests

List the services on jobs and quotes by status, job, location or deficiency. Access: read. REST: `GET /api/v1/servicetrade/service-requests`. MCP: `servicetrade_read → list_service_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One or more of open, in_progress, closed, void, canceled, pending, comma-separated. |
| `job_id` | integer | no | Only services on this job. |
| `location_id` | integer | no | Only services at this location. |
| `deficiency_id` | integer | no | Only services meant to repair this deficiency, from list_deficiencies. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the description, status, service line, location and the deficiency each service addresses. A quote is made from these ids, and an appointment can carry them.

Example response:

```json
{
  "service_requests": [
    {
      "id": 77302,
      "description": "Replace failed pressure switch on fire pump controller",
      "status": "open",
      "service_line": "Fire protection",
      "location": {
        "id": 5120,
        "name": "Harbor Point Mall"
      },
      "deficiency_id": 9031
    }
  ],
  "next_cursor": null
}
```

### list_deficiencies

List deficiencies found on inspections by severity, status, resolution or location. Access: read. REST: `GET /api/v1/servicetrade/deficiencies`. MCP: `servicetrade_read → list_deficiencies`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `severity` | string | no | One of inoperable, deficient, suggested. |
| `status` | string | no | One of new, invalid, verified, fixed. |
| `resolution` | string | no | One of new, out_for_quote, notified, out_for_repair, fixed, rejected, invalid. |
| `location_id` | integer | no | Only deficiencies at this location. |
| `quoted` | boolean | no | false returns only deficiencies that are not on a quote yet. |
| `created_after` | string | no | ISO 8601 date or date-time; only deficiencies created on or after it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the reference number, severity, status, resolution, description, proposed fix, asset, location and the date it was reported. Newest first is not guaranteed, so sort on reported_on when order matters.

Example response:

```json
{
  "deficiencies": [
    {
      "id": 9031,
      "ref_number": "D-9031",
      "severity": "inoperable",
      "status": "new",
      "resolution": "new",
      "title": "Inoperable - Fire pump controller",
      "description": "Pressure switch failed on test.",
      "proposed_fix": "Replace pressure switch and retest.",
      "asset": "Fire pump controller",
      "location": {
        "id": 5120,
        "name": "Harbor Point Mall"
      },
      "reported_on": "2026-10-21"
    }
  ],
  "next_cursor": null
}
```

### list_quotes

List quotes by status, customer, location or date. Access: read. REST: `GET /api/v1/servicetrade/quotes`. MCP: `servicetrade_read → list_quotes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One or more of draft, new, submitted, accepted, rejected, canceled, pending_sales_tax, comma-separated. |
| `customer_id` | integer | no | Only quotes for this customer company. |
| `location_id` | integer | no | Only quotes at this location. |
| `submitted_before` | string | no | ISO 8601 date or date-time; only quotes last submitted on or before it. |
| `created_after` | string | no | ISO 8601 date or date-time; only quotes created on or after it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the name, reference number, status, customer, location, total price and the dates it was last submitted and accepted. Use get_quote for the line items.

Example response:

```json
{
  "quotes": [
    {
      "id": 20391,
      "name": "Repair: emergency lighting, Delta Plaza",
      "ref_number": "20391",
      "status": "submitted",
      "customer": {
        "id": 2214,
        "name": "Delta Plaza LLC"
      },
      "location": {
        "id": 5133,
        "name": "Delta Plaza"
      },
      "total_price": "1840.00",
      "latest_submission": "2026-10-12",
      "latest_accepted": null
    }
  ],
  "next_cursor": null
}
```

### get_quote

Read one quote with its line items and services. Access: read. REST: `GET /api/v1/servicetrade/quotes/{quote_id}`. MCP: `servicetrade_read → get_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | integer | yes | Quote id from list_quotes. |

Returns the status, the line items with descriptions, subtotal, tax and total, the service requests it covers, the expiry date and who it is assigned to.

Example response:

```json
{
  "id": 20391,
  "name": "Repair: emergency lighting, Delta Plaza",
  "status": "submitted",
  "items": [
    {
      "id": 51120,
      "description": "Replace 6 emergency light batteries"
    }
  ],
  "subtotal": "1700.00",
  "tax_amount": "140.00",
  "total_price": "1840.00",
  "service_requests": [
    {
      "id": 77190,
      "description": "Replace emergency light batteries",
      "status": "open"
    }
  ],
  "expires_on": "2026-11-12"
}
```

### list_locations

List customer locations by name, company or status. Access: read. REST: `GET /api/v1/servicetrade/locations`. MCP: `servicetrade_read → list_locations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | no | Part of the location name or store number. |
| `company_id` | integer | no | Only locations of this company. |
| `status` | string | no | One of active, inactive, pending. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the id, name, reference number, address and status of each location. Use the id in list_jobs, list_deficiencies and create_quote.

Example response:

```json
{
  "locations": [
    {
      "id": 5120,
      "name": "Harbor Point Mall",
      "ref_number": "HPM",
      "address": {
        "street": "100 Harbor Point Rd",
        "city": "Baltimore",
        "state": "MD",
        "postal_code": "21230"
      },
      "status": "active"
    }
  ],
  "next_cursor": null
}
```

### list_technicians

List the technicians of your company. Access: read. REST: `GET /api/v1/servicetrade/technicians`. MCP: `servicetrade_read → list_technicians`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of a name, username or email. |

Returns the id and name of each active technician in your company. It returns no skills or certifications, so name who may take which job type in your prompt. The list is not paged.

Example response:

```json
{
  "technicians": [
    {
      "id": 3301,
      "name": "Marcus Hill"
    },
    {
      "id": 3302,
      "name": "Dana Ruiz"
    }
  ]
}
```

### create_appointment

Book an appointment for a job with a technician and a time window. Access: write, asks the user first. REST: `POST /api/v1/servicetrade/jobs/{job_id}/appointments`. MCP: `servicetrade_write → create_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | integer | yes | Job to book, from list_jobs. |
| `technician_ids` | array | no | Technician ids from list_technicians. |
| `window_start` | string | no | ISO 8601 date-time with offset. |
| `window_end` | string | no | ISO 8601 date-time with offset. |
| `service_request_ids` | array | no | Services of the job to do at this appointment; none means an appointment without services. |
| `released` | boolean | no | true gives the appointment to the technicians now, false keeps it as a draft. |

Returns the new appointment with its status, window, technicians and released flag. Service requests must belong to the job. Leave released false to review the day first, and use update_appointment to release it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 90417,
  "job_id": 48213,
  "status": "scheduled",
  "window_start": "2026-10-26T08:00:00-04:00",
  "window_end": "2026-10-26T10:00:00-04:00",
  "technicians": [
    {
      "id": 3301,
      "name": "Marcus Hill"
    }
  ],
  "released": false
}
```

### update_appointment

Change an appointment: status, window, technicians or release it. Access: write, asks the user first. REST: `PATCH /api/v1/servicetrade/appointments/{appointment_id}`. MCP: `servicetrade_write → update_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | integer | yes | Appointment id from list_appointments. |
| `status` | string | no | One of scheduled, canceled_by_vendor, canceled_by_customer, completed, no_show. |
| `window_start` | string | no | ISO 8601 date-time with offset. |
| `window_end` | string | no | ISO 8601 date-time with offset. |
| `technician_ids` | array | no | Replaces the whole technician list of the appointment. |
| `released` | boolean | no | true gives the appointment to its technicians. |

Send only the fields to change; the rest stay as they are. Technicians and services are replaced as a whole, not added to. Releasing or cancelling reaches technicians and can reach the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 90417,
  "status": "scheduled",
  "window_start": "2026-10-26T08:00:00-04:00",
  "window_end": "2026-10-26T10:00:00-04:00",
  "technicians": [
    {
      "id": 3301,
      "name": "Marcus Hill"
    }
  ],
  "released": true
}
```

### create_quote

Create a quote for services at a location, as a draft. Access: write, asks the user first. REST: `POST /api/v1/servicetrade/locations/{location_id}/quotes`. MCP: `servicetrade_write → create_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | yes | Location where the work is done, from list_locations. |
| `name` | string | yes | Quote name. |
| `description` | string | yes | Description of the work to be quoted. |
| `job_type` | string | yes | A ServiceTrade job type for the job the quote creates, such as repair, inspection_repair or replacement. |
| `service_request_ids` | array | yes | Services the quote covers, from list_service_requests. They must belong to the location. |
| `status` | string | no | One of draft, new. |

Returns the new quote with its number and status. A draft quote is not sent to the customer; use submit_quote for that. Prices come from the contract and line items in ServiceTrade. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": 20418,
  "ref_number": "20418",
  "name": "Repair: fire pump controller, Harbor Point Mall",
  "status": "draft",
  "location": {
    "id": 5120,
    "name": "Harbor Point Mall"
  },
  "service_request_ids": [
    77302
  ]
}
```

### submit_quote

Submit a draft quote so the customer can review and approve it. Access: write, asks the user first. REST: `POST /api/v1/servicetrade/quotes/{quote_id}/submit`. MCP: `servicetrade_write → submit_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quote_id` | integer | yes | Quote id from create_quote or list_quotes. |

Moves a quote in status draft or new to submitted. Any other status is refused. The customer then sees the quote online. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": 20418,
  "status": "submitted",
  "submitted_at": "2026-10-26T14:05:00-04:00"
}
```

### add_comment

Add a comment to a job, location, quote or deficiency. Access: write, asks the user first. REST: `POST /api/v1/servicetrade/entities/{entity_id}/comments`. MCP: `servicetrade_write → add_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `entity` | string | yes | One of job, location, quote, deficiency. |
| `entity_id` | integer | yes | Id of the job, location, quote or deficiency. |
| `content` | string | yes | Text of the comment. |
| `visibility` | string | no | One of private, customer. private is visible only to users of your account. |

Returns the comment id. A private comment is seen by your own staff; a customer comment can also be seen by the customer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": 604411,
  "entity": "job",
  "entity_id": 48213,
  "visibility": "private",
  "created_at": "2026-10-26T09:12:00-04:00"
}
```

## How do I connect ServiceTrade to Claude Code, Codex or Cursor?

Connecting ServiceTrade takes three steps: sign up, sign in to ServiceTrade once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect ServiceTrade to your agent.

1. **Create an account** Sign up and add ServiceTrade in the console. Your API key is there too.

2. **Sign in to ServiceTrade in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to ServiceTrade there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the ServiceTrade tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List ServiceTrade jobs with status Unscheduled, find a free technician for each on Monday morning, and create an appointment for them as a draft I can release later.
```

### Call ServiceTrade from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/servicetrade with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/servicetrade/jobs/48213/appointments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"technician_ids":[3301],"window_start":"2026-10-26T08:00:00-04:00","window_end":"2026-10-26T10:00:00-04:00","released":false}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "appointment_id": 90417,
  "job_id": 48213,
  "status": "scheduled",
  "window_start": "2026-10-26T08:00:00-04:00",
  "window_end": "2026-10-26T10:00:00-04:00",
  "technicians": [
    {
      "id": 3301,
      "name": "Marcus Hill"
    }
  ],
  "released": false
}
```

## Why use Cotlet for ServiceTrade?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to ServiceTrade yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When ServiceTrade changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect ServiceTrade to Cotlet?

Yes. You sign in to ServiceTrade yourself, in your own Cloud Browser, and we never save your password. Your agents only get ServiceTrade once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official ServiceTrade integration?**

No, Cotlet is independent of ServiceTrade. ServiceTrade's own API is too limited for this work. Cotlet works through your own ServiceTrade account, the way you use ServiceTrade in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to ServiceTrade in your console: your agents lose access at once and you stay signed in. Signing out of ServiceTrade in the browser works too, and Reset browser deletes the whole profile.

## Is there a ServiceTrade MCP server on GitHub?

No ServiceTrade MCP server from ServiceTrade or the community works on live data that we could verify on 23 Oct 2026. The realistic options are Zapier, which has a ServiceTrade app and an MCP wrapper of its actions, or code against the REST API. Cotlet hosts one MCP server and REST API for the same jobs, and our team keeps it working.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect ServiceTrade in Zapier, then build each Zap or pick actions for Zapier MCP | Sign up, sign in to ServiceTrade once, add one MCP server or API key |
| Reading data | Triggers on new or updated records, and searches that find one record by ID or number | Lists you can filter: jobs by status, appointments by technician, deficiencies by severity, quotes by status |
| Writing data | Create and update appointments, create quotes and jobs, add comments | Create and update appointments, create and submit quotes, add comments, each one confirmed by you |
| When ServiceTrade changes | Zapier maintains its app | Our team tests it daily and fixes it for you; failed calls are free |
| Your ServiceTrade session | Zapier holds the connection to your account | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Where it runs | Inside Zapier workflows and Zapier MCP | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | A Zapier plan; see Zapier for its tiers | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when ServiceTrade changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the ServiceTrade API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the ServiceTrade API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own ServiceTrade account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to ServiceTrade yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get ServiceTrade only after you enable it. When ServiceTrade signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to ServiceTrade, sign out of ServiceTrade in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **ServiceTrade's terms:** You use your own ServiceTrade account and stay responsible for following ServiceTrade's terms. Cotlet is independent and not affiliated with ServiceTrade. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open ServiceTrade in the console and press Request access. Then you create your API key and connect ServiceTrade there.

**Do I need to be technical?**

No. You sign in to ServiceTrade once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect ServiceTrade to Cotlet?**

Yes. You sign in to ServiceTrade yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get ServiceTrade once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My ServiceTrade sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your ServiceTrade cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through ServiceTrade's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. ServiceTrade sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no ServiceTrade login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

ServiceTrade offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which ServiceTrade role does my agent need?**

The agent works as your own ServiceTrade user, so your role decides what it can do. ServiceTrade grants permissions to roles as activities such as job.manage and quote.edit, and an action without the activity is refused. Use an office or admin account for scheduling and quotes.

**Does Cotlet use the ServiceTrade API?**

No. Cotlet works in the ServiceTrade web app in your Cloud Browser, as you do, so you need no API client credentials. The REST API stays the better fit for a custom integration you build and host yourself.

**What can it not do yet?**

Invoices, payments, contracts, time cards, inspections, attachments and creating jobs are not built yet. Reading and drafting come first: nothing is sent to a customer or technician without your OK unless you switch confirmation off for that tool.

**Can my agent post or send messages in ServiceTrade without asking me?**

No. Every call to create_appointment, update_appointment, create_quote, submit_quote or add_comment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the ServiceTrade API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/servicetrade from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.