# Kickserv API and MCP server

> Kickserv has an XML API, but only on premium plans (checked 11 Oct 2026). It covers customers, jobs, job charges, notes, schedule events and time entries; it has no endpoints for estimates, invoices or payments.

Field service software for small trade businesses: customers, opportunities and estimates, scheduled jobs, time tracking, invoices and payments.

## What is the Kickserv API?

Cotlet's Kickserv API exposes 15 endpoints for your own Kickserv account: list customers, get customer, list jobs, get job, list opportunities, list invoices, create customer, create job, add charge, schedule event, log time entry, send estimate, generate invoice, send invoice and record payment. The list_customers endpoint returns customers and contacts, searchable by name, email, phone or address. Each endpoint takes simple JSON inputs like job_number, page or employee and works both as an MCP tool for agents and as a REST call for scripts.

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

Kickserv has an XML API, but only on premium plans (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Kickserv with 15 endpoints (6 read, 9 write): your AI agent signs in as you and does the work.

## Does Kickserv have an official API?

Kickserv has an XML API, but only on premium plans (checked 11 Oct 2026). It covers customers, jobs, job charges, notes, schedule events and time entries; it has no endpoints for estimates, invoices or payments.

| Task | Kickserv official | Cotlet |
|---|---|---|
| Find customers and their jobs | Partly: Premium plans only, XML | Yes |
| Create a customer and a job | Partly: Premium plans only; a job needs the customer and job type IDs | Yes |
| Add a charge to a job | Partly: Create only, premium plans | Yes |
| Schedule a work event for a technician | Partly: Premium plans only | Yes |
| Log time on a job | Partly: Premium plans only | Yes |
| Send an estimate to the customer | No | Yes |
| Generate and send an invoice | No | Yes |
| Log a payment and mark an invoice paid | No: A balance remaining field exists on a job, no payment records | Yes |

Sources: [Kickserv API documentation](https://app.kickserv.com/api-docs), [Kickserv help: Developer API](https://help.kickserv.com/article/4-developer-api), [Kickserv help: Invoices](https://help.kickserv.com/article/33-invoices), [Kickserv help: Estimates](https://help.kickserv.com/article/31-estimates), [Kickserv help: Mobile Check Capture](https://help.kickserv.com/article/105-mobile-check-capture), [Kickserv blog: Contact Form creates unscheduled opportunities](https://www.kickserv.com/blog/new-and-improved-lead-contact-form-creates-conversations-and-unscheduled-opportunities)

## For AI agents

```text
Kickserv has an XML API, but only on premium plans (checked 11 Oct 2026). It covers customers, jobs, job charges, notes, schedule events and time entries; it has no endpoints for estimates, invoices or payments.
Cotlet provides a hosted MCP server and REST API for Kickserv: 15 tools (6 read, 9 write).
Access       Request access at https://cotlet.dev/app/signup?app=kickserv; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/kickserv
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_customers, get_customer, list_jobs, get_job, list_opportunities, list_invoices, create_customer, create_job, add_charge, schedule_event, log_time_entry, send_estimate, generate_invoice, send_invoice, record_payment
Confirm      schedule_event, send_estimate, send_invoice, record_payment (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/kickserv-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=kickserv (Kickserv is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Kickserv once in a browser. 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 Kickserv server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Kickserv MCP server instead.

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.
Session: the user signs in to Kickserv in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Kickserv's terms; Cotlet is not affiliated with Kickserv.
```

## What can an AI agent do in Kickserv?

Cotlet is best for Kickserv owners and office managers of small trade businesses who want their AI agent to send estimates and invoices, log payments and schedule jobs without running or fixing a server.

- **[Add leads as opportunities](https://cotlet.dev/integrations/kickserv-api-mcp-server/add-leads-as-opportunities)** (runs: daily): "Three lead emails came in overnight from the website and the ads form. Add each one to Kickserv as an opportunity, reuse the customer if we already have them, and tell me which service type you picked." → `list_customers`, `get_customer`, `create_customer`, `create_job`
- **[Build and send an estimate](https://cotlet.dev/integrations/kickserv-api-mcp-server/build-and-send-estimates)**: "Build the estimate for opportunity 1042 from my notes: 40 gal gas water heater $689, expansion tank $85, 3 hours labor at $95, haul-away $45. Show me the total, then send it to the customer and copy the office." → `list_opportunities`, `get_job`, `add_charge`, `send_estimate`
- **[Invoice completed jobs](https://cotlet.dev/integrations/kickserv-api-mcp-server/invoice-completed-jobs)** (runs: daily): "Invoice every Kickserv job completed yesterday and email the invoices. Skip jobs with no charges or with more visits still scheduled, and list them for me." → `list_jobs`, `get_job`, `generate_invoice`, `send_invoice`
- **[Log check and cash payments](https://cotlet.dev/integrations/kickserv-api-mcp-server/log-manual-payments)**: "Log the checks from today's mail in Kickserv: Lee Residence $480 check #2207, Rivera Dental $1,250 check #5531, Tom Becker $150 cash toward his $300 invoice. Mark invoices paid only when the balance is covered." → `list_invoices`, `get_job`, `record_payment`
- **Schedule unscheduled jobs** (runs: daily): "Put job 1050 on Dana's calendar for Thursday at 9:00." → `list_jobs`, `schedule_event`
- **Log technician hours on jobs** (runs: weekly): "Log 2.5 hours for Dana on job 1049 for October 9." → `get_job`, `log_time_entry`

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

Yes. Cotlet does not replace your automation platform: it gives it a Kickserv 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 add leads as opportunities, 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 to https://cotlet.dev/api/v1/kickserv/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/kickserv/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/kickserv/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/kickserv/{tool} with your API key. | cron or GitHub Actions. |

## Tools

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

### list_customers

Customers and contacts, searchable by name, email, phone or address. Access: read. REST: `POST /api/v1/kickserv/list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, email, phone or street address. |
| `page` | integer | no | Page number. Default: 1. |

Returns customers with their number, contact details and service address. Search matches name, email, phone and street address. Pass the customer_number to get_customer, create_job and the other tools.

Example response:

```json
{
  "customers": [
    {
      "customer_number": "2218",
      "name": "Lee Residence",
      "email": "lee@example.com",
      "phone": "555-0142",
      "service_address": "41 Maple St, Austin, TX 78701"
    }
  ],
  "page": 1
}
```

### get_customer

One customer with addresses, contacts, notes and jobs. Access: read. REST: `POST /api/v1/kickserv/get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_number` | string | yes | Customer number from list_customers. |

Returns one customer with service and billing addresses, saved contacts, special instructions, notes and the list of their jobs with status. Use it before creating a job so your agent reuses the right contact.

Example response:

```json
{
  "customer_number": "2218",
  "name": "Lee Residence",
  "billing_address": "41 Maple St, Austin, TX 78701",
  "contacts": [
    {
      "name": "Mrs. Lee",
      "email": "lee@example.com",
      "primary": true
    }
  ],
  "jobs": [
    {
      "job_number": "1037",
      "service_type": "Water heater replacement",
      "status": "complete"
    }
  ]
}
```

### list_jobs

Jobs with status, service type, customer, assigned techs and scheduled date. Access: read. REST: `POST /api/v1/kickserv/list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | unscheduled, scheduled, in_progress, on_hold, canceled or complete. |
| `scheduled` | enum | no | today, tomorrow, yesterday, this_week, next_week, last_week, this_month, next_month, last_month, this_year or last_year. |
| `employee` | string | no | Only jobs assigned to this employee. |
| `page` | integer | no | Page number. Default: 1. |

Returns jobs 30 per page, filtered by status, scheduled date or technician. Use job_number in get_job and the write tools.

Example response:

```json
{
  "jobs": [
    {
      "job_number": "1037",
      "service_type": "Water heater replacement",
      "customer": "Lee Residence",
      "status": "complete",
      "scheduled_on": "2026-10-09",
      "employees": [
        "Dana Ruiz"
      ]
    }
  ],
  "page": 1
}
```

### get_job

Full job: description, scope of work, charges, schedule events, time entries, notes and invoice status. Access: read. REST: `POST /api/v1/kickserv/get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |

Returns one job or opportunity with its internal description, the customer-facing scope of work, charges with the running total, schedule events, time entries, notes and whether an invoice exists and is paid.

Example response:

```json
{
  "job_number": "1042",
  "service_type": "Water heater replacement",
  "customer": "Lee Residence",
  "status": "new",
  "description": "Website lead: 40 gal tank leaking",
  "scope_of_work": "Replace the 40 gallon gas water heater.",
  "charges": [],
  "total": "0.00",
  "events": [],
  "time_entries": [],
  "invoice": null
}
```

### list_opportunities

Opportunities with customer, service type and whether an estimate was sent. Access: read. REST: `POST /api/v1/kickserv/list_opportunities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `stage` | enum | no | new, won or lost. Default: new. |
| `page` | integer | no | Page number. Default: 1. |

Returns opportunities from the Opportunities page. A new opportunity appears under the New tab; in the app an opportunity can be marked won or lost.

Example response:

```json
{
  "opportunities": [
    {
      "job_number": "1042",
      "service_type": "Water heater replacement",
      "customer": "Lee Residence",
      "stage": "new",
      "estimate_sent": false,
      "created_on": "2026-10-10"
    }
  ],
  "page": 1
}
```

### list_invoices

Invoices with customer, total, balance and whether they were sent and viewed. Access: read. REST: `POST /api/v1/kickserv/list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tab` | enum | no | unpaid or paid. Default: unpaid. |
| `page` | integer | no | Page number. Default: 1. |

Returns the invoices shown on the Invoices page, from its unpaid or paid tab. Each has a sent flag and a viewed flag, the same as the blue letter and purple eye icons in the app.

Example response:

```json
{
  "invoices": [
    {
      "job_number": "1037",
      "customer": "Lee Residence",
      "total": "480.00",
      "balance_remaining": "480.00",
      "sent": true,
      "viewed": true
    }
  ],
  "page": 1
}
```

### create_customer

New person or company contact with service and billing address. Access: write. REST: `POST /api/v1/kickserv/create_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Person or company name. |
| `is_company` | boolean | no | Company instead of a person. Default: false. |
| `email` | string | no | Customer email. |
| `phone` | string | no | Phone number. |
| `service_address` | object | no | street, city, state, zip_code, country. |
| `billing_address` | object | no | Same fields. Default: the service address. |

Creates a customer and returns its customer_number. It sends nothing to the customer and one edit in Kickserv undoes it, so it runs without asking first. Search with list_customers before creating one, to avoid duplicates.

Example response:

```json
{
  "customer_number": "2219",
  "name": "Rivera Dental",
  "status": "created"
}
```

### create_job

New job, or a new opportunity to estimate first, for a customer. Access: write. REST: `POST /api/v1/kickserv/create_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_number` | string | yes | Customer number from list_customers. |
| `service_type` | string | yes | Service type as named in your account. |
| `description` | string | no | Internal description, not shown to the customer. |
| `scope_of_work` | string | no | Customer-facing scope of work. |
| `as_opportunity` | boolean | no | Create an opportunity for an estimate instead of a job. Default: false. |

Creates a job for a customer and returns its job_number. With as_opportunity set to true it creates an opportunity under the New tab instead. The description is internal and the scope of work is shown to the customer. It sends nothing to the customer, so it runs without asking first.

Example response:

```json
{
  "job_number": "1051",
  "type": "opportunity",
  "stage": "new",
  "customer_number": "2218",
  "service_type": "Water heater replacement"
}
```

### add_charge

Add one charge item to the estimate or invoice of a job or opportunity. Access: write. REST: `POST /api/v1/kickserv/add_charge`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `item` | string | yes | Charge item from your account, or a new item name. |
| `description` | string | no | Line description. |
| `quantity` | string | no | Decimal, e.g. 1 or 2.5. Default: 1. |
| `price_per_unit` | string | no | Price as a decimal, e.g. 129.00. |
| `taxable` | boolean | no | Apply sales tax. Default: the item setting. |

Adds one charge line and returns the running total of the job. Call it once per line. Nothing reaches the customer until you send the estimate or invoice, so it runs without asking first.

Example response:

```json
{
  "job_number": "1042",
  "charge": {
    "item": "Labor",
    "quantity": "2.5",
    "price_per_unit": "95.00",
    "line_total": "237.50"
  },
  "total": "886.50"
}
```

### schedule_event

Add a work event to a job, optionally assigned to a technician. Access: write, asks the user first. REST: `POST /api/v1/kickserv/schedule_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `starts_at` | datetime | yes | ISO 8601 with time zone. |
| `ends_at` | datetime | no | End of the event. |
| `task_type` | string | no | Task type as named in your account, e.g. Work. Default: Work. |
| `employee` | string | no | Technician to assign. Default: unassigned. |
| `description` | string | no | Notes for the technician. |

Adds an event with a start time, an optional end, a task type and an optional technician. Without a technician the event stays unassigned. Depending on your reminder settings, Kickserv can send reminders for the event. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_number": "1050",
  "event_id": "ev_3381",
  "task_type": "Work",
  "starts_at": "2026-10-15T09:00:00-05:00",
  "employee": "Dana Ruiz",
  "job_status": "scheduled"
}
```

### log_time_entry

Record hours worked on a job by an employee. Access: write. REST: `POST /api/v1/kickserv/log_time_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `hours` | string | yes | Number of hours as a decimal, e.g. 2.5. |
| `date` | date | yes | Day the work was done. |
| `employee` | string | yes | Employee name. |
| `billable` | boolean | no | Billable time. Default: true. |
| `note` | string | no | What was done. |

Adds a time entry to the job and returns it. Hours are a decimal. It reaches no one and an admin can delete the entry in Kickserv, so it runs without asking first.

Example response:

```json
{
  "job_number": "1049",
  "time_entry_id": "te_7702",
  "employee": "Dana Ruiz",
  "date": "2026-10-09",
  "hours": "2.5",
  "billable": true,
  "note": "Installed water heater"
}
```

### send_estimate

Email the estimate of an opportunity to the customer. Access: write, asks the user first. REST: `POST /api/v1/kickserv/send_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `to` | string[] | no | Recipient emails. Default: the main customer of the job. |
| `cc` | string[] | no | Extra emails to copy. |
| `subject` | string | no | Email subject. Default: your Messaging Templates subject. |
| `message` | string | no | Custom message. Default: your Messaging Templates message. |
| `attach_pdf` | boolean | no | Also attach a PDF copy. Default: your Messaging Templates setting. |

Emails the estimate to the main customer of the job and copies the addresses you add. Subject and message come from your Messaging Templates unless you set them. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_number": "1042",
  "status": "sent",
  "sent_to": [
    "lee@example.com"
  ],
  "cc": [
    "office@example.com"
  ],
  "total": "886.50"
}
```

### generate_invoice

Create the invoice for a job from its charges. Nothing is sent. Access: write. REST: `POST /api/v1/kickserv/generate_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |

Creates the invoice from the charges on the job, the same as Generate Invoice in the job header, and returns its total. It sends nothing to the customer and the invoice can be edited afterwards, so it runs without asking first.

Example response:

```json
{
  "job_number": "1037",
  "invoice_status": "not_sent",
  "total": "480.00",
  "balance_remaining": "480.00"
}
```

### send_invoice

Email the invoice of a job to the customer. Access: write, asks the user first. REST: `POST /api/v1/kickserv/send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `to` | string[] | no | Recipient emails. Default: the main customer of the job. |
| `cc` | string[] | no | Extra emails to copy. |
| `subject` | string | no | Email subject. Default: your Messaging Templates subject. |
| `message` | string | no | Custom message. Default: your Messaging Templates message. |
| `attach_pdf` | boolean | no | Also attach a PDF copy. Default: your Messaging Templates setting. |

Emails the invoice to the main customer of the job and copies the addresses you add. The invoice then shows as sent on the Invoices page. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_number": "1037",
  "invoice_status": "sent",
  "sent_to": [
    "lee@example.com"
  ],
  "total": "480.00",
  "balance_remaining": "480.00"
}
```

### record_payment

Log a manual payment (check, cash, other) on a job and mark the invoice paid. No card is charged. Access: write, asks the user first. REST: `POST /api/v1/kickserv/record_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_number` | string | yes | Job number from list_jobs, list_opportunities or get_job. |
| `amount` | string | yes | Amount as a decimal, e.g. 480.00. |
| `method` | string | yes | Payment type as named in your account, e.g. Check. |
| `paid_on` | date | no | Default: today. |
| `mark_paid` | boolean | no | Mark the invoice paid afterwards. Default: true. |

Logs the payment type on the job, then marks the invoice paid when mark_paid is true. Kickserv does not bring the balance to zero for manual payments on its own, so the type is recorded first. No card is charged. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_number": "1037",
  "amount": "480.00",
  "method": "Check",
  "paid_on": "2026-10-10",
  "invoice_status": "paid",
  "balance_remaining": "0.00"
}
```

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

Connecting Kickserv takes three steps: request access, sign in to Kickserv once, then add one MCP server or call the REST API with the same key.

### Connect Kickserv to your agent.

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

2. **Sign in to Kickserv once** Open the connect page from the console and sign in to Kickserv the way you always do. We keep the session, never your password, and you can revoke it anytime.

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

```
Three lead emails came in overnight from the website and the ads form. Add each one to Kickserv as an opportunity, reuse the customer if we already have them, and tell me which service type you picked.
```

### Call Kickserv 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 a POST endpoint at /api/v1/kickserv/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/kickserv/send_invoice \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job_number":"1037"}'
```

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

```
{
  "job_number": "1037",
  "invoice_status": "sent",
  "sent_to": [
    "lee@example.com"
  ],
  "total": "480.00",
  "balance_remaining": "480.00"
}
```

## Why use Cotlet for Kickserv?

**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 Kickserv yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

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

## Is there a Kickserv MCP server on GitHub?

Yes. A community Kickserv MCP server exists on GitHub, maintained by one person. You install it yourself, give it an employee API token from a premium plan and fix it when it breaks. It is limited by the official API, so it cannot send estimates or invoices. Cotlet hosts the same kind of server for you, works from your browser sign-in, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Premium plan, copy an employee API token into environment variables, add it to each MCP client | Request access, sign in to Kickserv once, add one MCP server or API key |
| When Kickserv changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your access | An API token that acts like your password: changing your password changes it | Your session, encrypted in an EU vault, never your password |
| When access expires | Tools fail until you paste a new token by hand | If Kickserv signs you out, your agent gets a link to sign in again |
| Estimates, invoices, payments | Not available: the official API has no endpoints for them | Send estimates and invoices and log manual payments, each send confirmed by you |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, plus the premium plan and your time | Free 7-day trial with 5,000 credits, then credits per call |

### 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 Kickserv 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Kickserv API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Kickserv API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

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

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Kickserv yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Kickserv tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Kickserv in your dashboard: the session is deleted and access ends at once. 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.
- **Kickserv's terms:** You use your own Kickserv account and stay responsible for following Kickserv's terms. Cotlet is independent and not affiliated with Kickserv. [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?**

Request access and pick Kickserv. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Kickserv once in your browser 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 a hosted server safe? My Kickserv session would leave my computer.**

Cotlet keeps your Kickserv session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need a premium plan to use Kickserv with Cotlet?**

No. Cotlet works through your own Kickserv sign-in, so it needs no API token, which Kickserv gives only to premium plans. It can do what your plan and role can do in the app. Check the plan details on Kickserv's pricing page.

**Can it charge a customer's card?**

No. record_payment only logs a manual payment such as a check or cash, and marks the invoice paid. Online payments stay in Kickserv.

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

No. Every call to schedule_event, send_estimate, send_invoice or record_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_customer, create_job, add_charge, log_time_entry, generate_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

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

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/kickserv/{tool} from the HTTP Request node.