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

# Teamleader API and MCP server

> Teamleader has a full public API, version 2, but no official MCP server (checked 20 Oct 2026). Each call is a POST such as companies.list or invoices.send. To use it you register an integration as an OAuth 2 client on the Teamleader Marketplace. Access tokens last 1 hour and each refresh token works once. Teamleader also has Focus AI, an assistant built into the app.

Belgian business software for small and mid-size companies: CRM, deals, quotations, invoices, projects and time tracking in one account, called Teamleader Focus.

## What is the Teamleader API?

Cotlet's Teamleader API exposes 12 endpoints for your own Teamleader account: search companies, list deals, get deal, list deal phases, list quotations, list invoices, get invoice, add note, create task, move deal, send quotation and send invoice reminder. The search_companies endpoint returns companies that match a search term, with their ID, status and main contact details. Each endpoint takes simple JSON inputs like status, page or page_size and works both as an operation of the teamleader_read or teamleader_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 12 (7 read, 5 write)
- **Updated:** 2026-10-21

Teamleader has a full public API, version 2, but no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Teamleader with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Teamleader have an official API?

Teamleader has a full public API, version 2, but no official MCP server (checked 20 Oct 2026). Each call is a POST such as companies.list or invoices.send. To use it you register an integration as an OAuth 2 client on the Teamleader Marketplace. Access tokens last 1 hour and each refresh token works once. Teamleader also has Focus AI, an assistant built into the app.

| Task | Teamleader official | Cotlet |
|---|---|---|
| Search companies | Yes: companies.list | Yes |
| List deals and deal phases | Yes: deals.list and dealPhases.list | Yes |
| Move a deal to another phase | Yes: deals.move | Yes |
| Send a quotation by email | Yes: quotations.send | Yes |
| List overdue invoices | Yes: invoices.list filters by status; overdue is worked out from due_on | Yes |
| Send an invoice reminder | Partly: invoices.send sends an invoice by email; the API docs list no separate reminder action | Yes |
| Create tasks and notes | Yes: tasks.create and notes.create | Yes |
| Call all of it from your own AI agent | No: No official MCP server; Focus AI works in the Teamleader chat only | Yes |

Sources: [Teamleader Developers: Authentication](https://developer.focus.teamleader.eu/docs/authentication), [Teamleader API v2 reference (teamleadercrm/api)](https://github.com/teamleadercrm/api), [Teamleader Help: What is API in Teamleader Focus?](https://support.focus.teamleader.eu/hc/en-150/articles/25692808751761-Getting-started-What-is-API-in-Teamleader-Focus), [Teamleader Help: What is Focus AI and what can it do?](https://support.focus.teamleader.eu/hc/en-150/articles/51190317390865-What-is-Focus-AI-and-what-can-it-do)

## For AI agents

```text
Teamleader has a full public API, version 2, but no official MCP server (checked 20 Oct 2026). Each call is a POST such as companies.list or invoices.send. To use it you register an integration as an OAuth 2 client on the Teamleader Marketplace. Access tokens last 1 hour and each refresh token works once. Teamleader also has Focus AI, an assistant built into the app.
Cotlet provides a hosted MCP server and REST API for Teamleader: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=teamleader, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    teamleader_read, teamleader_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/teamleader, each operation at its own route, e.g. POST /api/v1/teamleader/invoices/{invoice_id}/reminder
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   search_companies, list_deals, get_deal, list_deal_phases, list_quotations, list_invoices, get_invoice, add_note, create_task, move_deal, send_quotation, send_invoice_reminder
Confirm      send_quotation, send_invoice_reminder (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/teamleader-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=teamleader, requests Teamleader in the Cotlet console and creates an API key there.
2. The user signs in to Teamleader once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Teamleader 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 Teamleader 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 Teamleader 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.
Sign-in: the user signs in to Teamleader 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 Teamleader 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 Teamleader 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 Teamleader's terms; Cotlet is not affiliated with Teamleader.
```

## What can an AI agent do in Teamleader?

Cotlet is best for Teamleader teams who want their AI agent to chase overdue invoices and open quotations and keep deals moving without running or fixing a server.

- **[Chase overdue invoices](https://cotlet.dev/integrations/teamleader-api-mcp-server/chase-overdue-invoices.md)** (runs: daily): "Go through overdue Teamleader invoices. For each one that is more than 7 days overdue and has had fewer than 2 reminders, send the next reminder with the matching template. List the rest for me with the days overdue." → `list_invoices`, `get_invoice`, `send_invoice_reminder`, `add_note`
- **[Follow up quotations nobody answered](https://cotlet.dev/integrations/teamleader-api-mcp-server/follow-up-open-quotations.md)** (runs: weekly): "Find Teamleader quotations that were sent more than 10 days ago and are not accepted or refused. Skip deals that already have an accepted quotation. For each other one, create a call task for the deal owner in 2 days and add a note on the deal." → `list_quotations`, `get_deal`, `create_task`, `add_note`
- **Send a quotation from a deal** (runs: weekly): "For every deal in the Quotation sent phase that still has a quotation not sent, send it to the deal contact by email." → `list_deals`, `list_quotations`, `send_quotation`
- **Brief me before a customer call**: "Before my call with Northwind Studio, show their open deals, sent quotations and overdue invoices in one list." → `search_companies`, `list_deals`, `list_quotations`, `list_invoices`
- **Weekly pipeline report** (runs: weekly): "Every Monday, tell me how many Teamleader deals are open in each phase and which deals have not changed in 30 days." → `list_deal_phases`, `list_deals`

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

Yes. Cotlet does not replace your automation platform: it gives it a Teamleader 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 chase overdue invoices, 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/teamleader/invoices. | 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/teamleader/invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 Teamleader.

### search_companies

Companies that match a search term, with their ID, status and main contact details. Access: read. REST: `GET /api/v1/teamleader/companies/search`. MCP: `teamleader_read → search_companies`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `term` | string | yes | Name, VAT number, email or phone number to search for. |
| `status` | enum | no | active or deactivated. Default: active. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |
| `page_size` | integer | no | Items per page. Default: 20. |

Searches companies by name, VAT number, email or phone number. Returns one page of companies, 20 by default. The company ID from here is what list_deals and list_invoices take as customer_id. Deactivated companies are only returned if you ask for them.

Example response:

```json
{
  "companies": [
    {
      "company_id": "c4a7e2d1-5b36-4f08-a9c3-7e1d2f4b6a80",
      "name": "Northwind Studio",
      "vat_number": "BE0123456749",
      "email": "accounts@northwind.example",
      "status": "active"
    }
  ],
  "page": 1,
  "total_matches": 1
}
```

### list_deals

Deals with title, customer, phase, estimated value and responsible user. Access: read. REST: `GET /api/v1/teamleader/deals`. MCP: `teamleader_read → list_deals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | open, won or lost. Default: open. |
| `phase_id` | string | no | Only deals in this phase, from list_deal_phases. |
| `customer_id` | string | no | Only deals of this company, from search_companies. |
| `term` | string | no | Search in title, reference and customer name. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |
| `page_size` | integer | no | Items per page. Default: 20. |

Returns one page of deals, newest first. Filter by status, phase, customer or a search term. Each deal shows its current phase, the estimated closing date and the web link to the deal in Teamleader. Deals you cannot see with your user permissions are not returned.

Example response:

```json
{
  "deals": [
    {
      "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
      "title": "Website redesign",
      "customer": "Northwind Studio",
      "phase": "Quotation sent",
      "status": "open",
      "estimated_value": {
        "amount": 8400,
        "currency": "EUR"
      },
      "estimated_closing_date": "2026-11-15",
      "responsible_user": "Lotte Peeters"
    }
  ],
  "page": 1,
  "total_matches": 1
}
```

### get_deal

One deal with its phase, customer, contact person, value and quotations. Access: read. REST: `GET /api/v1/teamleader/deals/{deal_id}`. MCP: `teamleader_read → get_deal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `deal_id` | string | yes | Deal ID from list_deals. |

Returns one deal with its current phase, customer, contact person, estimated value and probability, the responsible user and every quotation on it with its status. Use it to check whether another quotation on the deal is already accepted.

Example response:

```json
{
  "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
  "title": "Website redesign",
  "customer": "Northwind Studio",
  "contact_person": "Jonas Willems",
  "phase": "Quotation sent",
  "status": "open",
  "estimated_value": {
    "amount": 8400,
    "currency": "EUR"
  },
  "responsible_user": "Lotte Peeters",
  "quotations": [
    {
      "quotation_id": "e3b1c7a9-4d52-4086-b7f1-2a9c5d8e0f34",
      "status": "sent",
      "sent_at": "2026-10-08T09:12:00Z",
      "total_excl_tax": {
        "amount": 8400,
        "currency": "EUR"
      }
    }
  ],
  "web_url": "https://focus.teamleader.eu/sale_detail.php?id=9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10"
}
```

### list_deal_phases

The phases of your deal pipelines, in order, with their IDs. Access: read. REST: `GET /api/v1/teamleader/deal-phases`. MCP: `teamleader_read → list_deal_phases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline_id` | string | no | Only the phases of this pipeline. Default: all. |

Returns the phases of one pipeline or of all pipelines. Every pipeline starts with New, Quotation sent, Accepted and Refused, and your account may have more. The phase ID is what move_deal and list_deals take. How many pipelines you have depends on your package.

Example response:

```json
{
  "phases": [
    {
      "phase_id": "1758e847-cc1f-04ce-bd17-5a852e8c01b4",
      "name": "New",
      "pipeline": "Sales"
    },
    {
      "phase_id": "3a90b4d2-6e17-4c85-8f23-9d1e5a7c0b46",
      "name": "Quotation sent",
      "pipeline": "Sales"
    },
    {
      "phase_id": "5c12d8f6-0a39-4b71-a4e5-1f6b8d3c9e72",
      "name": "Accepted",
      "pipeline": "Sales"
    }
  ]
}
```

### list_quotations

Quotations with status, deal, customer, total and the day they were sent. Access: read. REST: `GET /api/v1/teamleader/quotations`. MCP: `teamleader_read → list_quotations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | sent, accepted or refused. Default: all. |
| `sent_before` | date | no | Only quotations sent before this date. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |
| `page_size` | integer | no | Items per page. Default: 20. |

Returns one page of quotations, newest first, with the deal each one belongs to. The status filter matches the Status filter of the Quotations overview. A deal can hold several quotations, so check get_deal before you chase one.

Example response:

```json
{
  "quotations": [
    {
      "quotation_id": "e3b1c7a9-4d52-4086-b7f1-2a9c5d8e0f34",
      "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
      "customer": "Northwind Studio",
      "status": "sent",
      "sent_at": "2026-10-08T09:12:00Z",
      "total_excl_tax": {
        "amount": 8400,
        "currency": "EUR"
      },
      "valid_until": "2026-11-07"
    }
  ],
  "page": 1,
  "total_matches": 1
}
```

### list_invoices

Invoices with number, customer, status, due date, amount due and reminders sent. Access: read. REST: `GET /api/v1/teamleader/invoices`. MCP: `teamleader_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, outstanding or paid. Default: outstanding. |
| `overdue_only` | boolean | no | Only invoices past their due date. Default: false. |
| `customer_id` | string | no | Only invoices of this company, from search_companies. |
| `invoice_date_after` | date | no | Only invoices dated on or after this day. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |
| `page_size` | integer | no | Items per page. Default: 20. |

Returns one page of invoices, by invoice number, ascending. Status is draft, outstanding or paid. overdue_only keeps outstanding invoices whose due date has passed and adds days_overdue. Amounts are in the currency of the invoice. Use get_invoice for the full detail of one.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4",
      "invoice_number": "2026 / 214",
      "customer": "Northwind Studio",
      "status": "outstanding",
      "due_on": "2026-10-06",
      "days_overdue": 14,
      "amount_due": {
        "amount": 1250,
        "currency": "EUR"
      },
      "reminders_sent": 1
    },
    {
      "invoice_id": "7d3e9b1c-2f48-4a60-b5c7-8e1a3d5f7092",
      "invoice_number": "2026 / 188",
      "customer": "Brightside Bakery",
      "status": "outstanding",
      "due_on": "2026-09-09",
      "days_overdue": 41,
      "amount_due": {
        "amount": 480,
        "currency": "EUR"
      },
      "reminders_sent": 2
    }
  ],
  "page": 1,
  "total_matches": 2
}
```

### get_invoice

One invoice with its lines, totals, payment status and how often it was sent. Access: read. REST: `GET /api/v1/teamleader/invoices/{invoice_id}`. MCP: `teamleader_read → get_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |

Returns the invoice number, customer, due date, totals with tax, the amount still due, whether it was sent and by which route, the number of reminders and the date of the last send. Peppol invoices are marked, because they cannot be reminded through Peppol.

Example response:

```json
{
  "invoice_id": "2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4",
  "invoice_number": "2026 / 214",
  "customer": "Northwind Studio",
  "status": "outstanding",
  "invoice_date": "2026-09-22",
  "due_on": "2026-10-06",
  "days_overdue": 14,
  "total_excl_tax": {
    "amount": 1033.06,
    "currency": "EUR"
  },
  "amount_due": {
    "amount": 1250,
    "currency": "EUR"
  },
  "sent_via": "email",
  "reminders_sent": 1,
  "last_sent_at": "2026-10-13T08:00:00Z",
  "web_url": "https://focus.teamleader.eu/invoice_detail.php?id=2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4"
}
```

### add_note

A note on a company, contact or deal. Access: write. REST: `POST /api/v1/teamleader/subjects/{subject_id}/notes`. MCP: `teamleader_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subject_type` | enum | yes | company, contact or deal. |
| `subject_id` | string | yes | ID of the company, contact or deal. |
| `content` | string | yes | Text of the note. |

Adds a note to the detail page of a company, a contact or a deal. Your colleagues see it there with your name. It reaches nobody by email and can be edited or deleted in Teamleader, so it does not wait for your OK.

Example response:

```json
{
  "note_id": "ee94b4c0-5786-0517-9d26-8dd1e6406f20",
  "subject_type": "deal",
  "subject_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
  "created_at": "2026-10-20T08:02:00Z"
}
```

### create_task

A task with a due date, work type and optional deal, assignee and customer. Access: write. REST: `POST /api/v1/teamleader/work-types/{work_type_id}/tasks`. MCP: `teamleader_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Task title. |
| `due_on` | date | yes | Due date, YYYY-MM-DD. |
| `work_type_id` | string | yes | Work type ID. Work types are set under Settings > Calendar > Work types. |
| `description` | string | no | Longer text for the task. |
| `deal_id` | string | no | Link the task to this deal. |
| `customer_id` | string | no | Link the task to this company. |
| `assignee_user_id` | string | no | User who gets the task. Default: unassigned. |

Creates a task. A title, a due date and a work type are required, because Teamleader asks for a work type on every task. Link it to a deal or a customer and assign it to a user. It is the same task you would add from a deal. It sends no email to a customer and is deleted in Teamleader if it is wrong, so it does not wait for your OK.

Example response:

```json
{
  "task_id": "1759dfc1-7365-4f1b-8d90-d29787a5d29d",
  "title": "Call Northwind Studio about the website quotation",
  "due_on": "2026-10-23",
  "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
  "assignee": "Lotte Peeters"
}
```

### move_deal

Moves a deal to another phase of its pipeline. Access: write. REST: `POST /api/v1/teamleader/phases/{phase_id}/deals/{deal_id}/move`. MCP: `teamleader_write → move_deal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `deal_id` | string | yes | Deal ID from list_deals. |
| `phase_id` | string | yes | Target phase ID from list_deal_phases. |

Moves one deal to the phase you name. A deal does not have to pass every phase. If that phase has a follow-up action, Teamleader plans the task, meeting or call as it does when you drag the deal in the app. Moving back undoes it, so it does not wait for your OK.

Example response:

```json
{
  "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
  "phase": "Accepted",
  "moved_at": "2026-10-20T08:05:00Z"
}
```

### send_quotation

Emails one or more quotations of a deal to the customer. Access: write, asks the user first. REST: `POST /api/v1/teamleader/quotations`. MCP: `teamleader_write → send_quotation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `quotation_ids` | array | yes | Quotation IDs, all from the same deal. |
| `to` | array | yes | Recipient email addresses. |
| `cc` | array | no | Copy recipients. |
| `subject` | string | no | Subject. Default: your email template. |

Sends quotations by email to the recipients you name. They must belong to the same deal. The customer gets the CloudSign link, and the PDF too if your account attaches it. You can set a sender, copies and a subject. The email leaves from Teamleader and cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "deal_id": "9c1f3a5e-7b24-4d68-8e0a-5f2b4c6d8e10",
  "quotation_ids": [
    "e3b1c7a9-4d52-4086-b7f1-2a9c5d8e0f34"
  ],
  "sent_to": [
    "jonas@northwind.example"
  ],
  "sent_at": "2026-10-20T08:10:00Z"
}
```

### send_invoice_reminder

Emails a reminder for an overdue invoice, with the original invoice attached. Access: write, asks the user first. REST: `POST /api/v1/teamleader/invoices/{invoice_id}/reminder`. MCP: `teamleader_write → send_invoice_reminder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices. |
| `template` | string | no | Name of an invoice email template under Settings > Revenue > Email templates for invoices. |
| `body` | string | no | Your own mail text instead of a template. |

Works only on an invoice past its payment term, like the Reminder button in the app. The mail uses the invoice email template you name, or your text, and adds one to the reminder count. A Peppol invoice is reminded by email. Returns the address used and the new count. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4",
  "invoice_number": "2026 / 214",
  "sent_to": "accounts@northwind.example",
  "template": "Second reminder",
  "reminders_sent": 2,
  "sent_at": "2026-10-20T08:00:00Z"
}
```

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

Connecting Teamleader takes three steps: sign up, sign in to Teamleader 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 Teamleader to your agent.

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

2. **Sign in to Teamleader in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Teamleader 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 Teamleader 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.

```
Go through overdue Teamleader invoices. For each one that is more than 7 days overdue and has had fewer than 2 reminders, send the next reminder with the matching template. List the rest for me with the days overdue.
```

### Call Teamleader 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/teamleader 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/teamleader/invoices/2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4/reminder \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"template":"Second reminder"}'
```

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

```
{
  "invoice_id": "2aa4a6a9-9ce8-4851-a9b3-26aea2ea14c4",
  "invoice_number": "2026 / 214",
  "sent_to": "accounts@northwind.example",
  "template": "Second reminder",
  "reminders_sent": 2,
  "sent_at": "2026-10-20T08:00:00Z"
}
```

## Why use Cotlet for Teamleader?

**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 Teamleader 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 Teamleader changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Teamleader to Cotlet?

Yes. You sign in to Teamleader yourself, in your own Cloud Browser, and we never save your password. Your agents only get Teamleader 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 Teamleader integration?**

No, Cotlet is independent of Teamleader. Teamleader's own API is too limited for this work. Cotlet works through your own Teamleader account, the way you use Teamleader 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 Teamleader in your console: your agents lose access at once and you stay signed in. Signing out of Teamleader in the browser works too, and Reset browser deletes the whole profile.

## Is there a Teamleader MCP server on GitHub?

Yes. Open-source Teamleader MCP servers exist on GitHub, usually maintained by one person. You install one yourself, register your own OAuth integration on the Teamleader Marketplace, keep the refresh tokens working and fix the server when it breaks. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, register an OAuth integration on the Marketplace, store its client secret, add the server to each MCP client | Sign up, sign in to Teamleader once, add one MCP server or API key |
| When Teamleader 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 Teamleader access | Client secret and refresh token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Access tokens last 1 hour and a refresh token works once, so a lost token means authorising again by hand | Your Cloud Browser keeps you signed in; if Teamleader logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | 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 Teamleader 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 Teamleader API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Teamleader 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 20 to 30 credits (25 for most tools, about $0.10 to $0.15), 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 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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 Teamleader 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 Teamleader 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 Teamleader only after you enable it. When Teamleader 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 Teamleader, sign out of Teamleader 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.
- **Teamleader's terms:** You use your own Teamleader account and stay responsible for following Teamleader's terms. Cotlet is independent and not affiliated with Teamleader. [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 Teamleader in the console and press Request access. Then you create your API key and connect Teamleader there.

**Do I need to be technical?**

No. You sign in to Teamleader 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 Teamleader to Cotlet?**

Yes. You sign in to Teamleader yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Teamleader 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 Teamleader 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 Teamleader 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 Teamleader's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Teamleader 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 Teamleader 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?**

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

**Is Focus AI the same as an MCP server for my own agent?**

No. Teamleader describes Focus AI as the assistant built into Teamleader Focus. It works in a chat inside the app, shows a preview and waits for your confirmation, and it uses AI credits shared by the whole account: 100 a month on Go and Smart, 200 on Move and Grow, 300 on Boost and Flow. Its help pages describe no MCP server or API for it (checked 20 Oct 2026).

**What Teamleader role or package does my agent need?**

Your own user, with the permissions an admin gave it under Settings > Users. A new user sees only some modules, such as contacts, companies, the calendar and the dashboard, until an admin widens access, and a call outside your permissions fails. The built-in automatic reminders for overdue invoices are not in the GO and SMART packages, but this integration does not depend on them.

**Does the integration use the Teamleader API?**

No. It works in your own signed-in Teamleader Focus account, so you do not register an OAuth integration or renew tokens. The API stays open to you if you build your own; Teamleader allows a separate test account for that, which you request at api@teamleader.eu.

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

No. Every call to send_quotation or send_invoice_reminder waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_note, create_task, move_deal runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Teamleader 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/teamleader 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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.