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

# Accelo API and MCP server

> Accelo has a full REST API and a hosted MCP server, but the MCP server is built for questions about your data (checked 17 Oct 2026). The API covers companies, contacts, tickets, projects, tasks, activities, quotes and invoices, and you register an OAuth application under Configuration > API to use it. Accelo's MCP page says assistants can read your data today and that teams can soon also act through it, for example logging time or updating tasks.

Professional services automation platform: client records, tickets, projects, retainers, quotes, time tracking and invoicing in one system for agencies, consultancies and IT services.

## What is the Accelo API?

Cotlet's Accelo API exposes 14 endpoints for your own Accelo account: list tickets, get ticket, list companies, list contacts, list projects, list tasks, list invoices, reply to ticket, add ticket note, log time, update ticket, create task, create quote and update project. The list_tickets endpoint returns tickets that match your filters, with standing, status, priority, client and assignee. Each endpoint takes simple JSON inputs like limit, cursor or status and works both as an operation of the accelo_read or accelo_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:** 14 (7 read, 7 write)
- **Updated:** 2026-10-20

Accelo has a full REST API and a hosted MCP server, but the MCP server is built for questions about your data (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Accelo with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Accelo have an official API?

Accelo has a full REST API and a hosted MCP server, but the MCP server is built for questions about your data (checked 17 Oct 2026). The API covers companies, contacts, tickets, projects, tasks, activities, quotes and invoices, and you register an OAuth application under Configuration > API to use it. Accelo's MCP page says assistants can read your data today and that teams can soon also act through it, for example logging time or updating tasks.

| Task | Accelo official | Cotlet |
|---|---|---|
| List and filter tickets | Yes: API, filters by standing, status, assignee, priority and dates; Accelo MCP answers questions about the same data | Yes |
| Reply to a ticket by email | Yes: API, create an email activity against the ticket; no MCP write tool announced for it | Yes |
| Add a note to a ticket | Yes: API, create a note activity | Yes |
| Log time on a ticket or project | Partly: API, create an activity with time; the MCP page lists time logging as coming | Yes |
| Change ticket status, priority or assignee | Yes: API, update an issue; you wire OAuth and paging yourself | Yes |
| Create a task | Yes: API, create a task against a ticket or project | Yes |
| Create a draft quote | Partly: API creates the quote from a title and parent; the quote docs list no calls for estimate lines or publishing | Yes |
| List invoices and what is outstanding | Yes: API, read only; the invoice docs list no create call | Yes |

Sources: [Accelo API reference](https://api.accelo.com/docs), [Accelo: MCP for Professional Services](https://www.accelo.com/ai/mcp), [Accelo Help: Add a Ticket](https://help.accelo.com/guides/user/modules/tickets/add-a-ticket/), [Accelo on Zapier: triggers and actions](https://zapier.com/apps/accelo/integrations)

## For AI agents

```text
Accelo has a full REST API and a hosted MCP server, but the MCP server is built for questions about your data (checked 17 Oct 2026). The API covers companies, contacts, tickets, projects, tasks, activities, quotes and invoices, and you register an OAuth application under Configuration > API to use it. Accelo's MCP page says assistants can read your data today and that teams can soon also act through it, for example logging time or updating tasks.
Cotlet provides a hosted MCP server and REST API for Accelo: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=accelo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    accelo_read, accelo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/accelo, each operation at its own route, e.g. POST /api/v1/accelo/againsts/{against_id}/times
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_tickets, get_ticket, list_companies, list_contacts, list_projects, list_tasks, list_invoices, reply_to_ticket, add_ticket_note, log_time, update_ticket, create_task, create_quote, update_project
Confirm      reply_to_ticket, update_ticket, create_task, create_quote, update_project (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/accelo-api-mcp-server.md

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

## What can an AI agent do in Accelo?

Cotlet is best for service teams on Accelo who want an agent to triage tickets, log time and reply to clients without running or fixing a server.

- **[Triage new tickets](https://cotlet.dev/integrations/accelo-api-mcp-server/triage-new-tickets.md)** (runs: daily): "Go through new Accelo tickets. Set the priority from what the client wrote, put billing questions in the Billing class and bugs in the Bug class, and add a private note with the reason. Leave unclear ones for me." → `list_tickets`, `get_ticket`, `update_ticket`, `add_ticket_note`
- **[Log time on tickets and projects](https://cotlet.dev/integrations/accelo-api-mcp-server/log-time-on-tickets-and-projects.md)** (runs: daily): "From my calendar and the tickets I touched today, log time in Accelo: 45 minutes on ticket 1042 for the export fix and 30 minutes on the Website Redesign project. Mark both billable." → `list_tickets`, `list_projects`, `log_time`
- **[Reply to client tickets](https://cotlet.dev/integrations/accelo-api-mcp-server/reply-to-client-tickets.md)** (runs: daily): "Find open Accelo tickets where the client wrote last and nobody replied for a day. Draft a short reply that answers the question, and send it only after I approve each one." → `list_tickets`, `get_ticket`, `reply_to_ticket`
- **Start a quote for a new sale**: "Create a draft quote on Accelo sale 96 titled "Website Redesign, phase 2", with Priya Nair as manager and the Standard proposal template. Do not publish or send anything." → `create_quote`
- **Weekly overdue invoice report** (runs: weekly): "Every Monday, list Accelo invoices that are past due with the amount outstanding per client, the oldest first, and the main contact for each." → `list_invoices`, `list_companies`, `list_contacts`

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

Yes. Cotlet does not replace your automation platform: it gives it a Accelo 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 triage new tickets, 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/accelo/tickets. | 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/accelo/tickets 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 Accelo.

### list_tickets

Tickets that match your filters, with standing, status, priority, client and assignee. Access: read. REST: `GET /api/v1/accelo/tickets`. MCP: `accelo_read → list_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `standing` | enum | no | submitted, open, resolved, closed or inactive. Default: submitted and open. |
| `status` | string | no | Status name as shown in Accelo, e.g. Active. |
| `assignee_id` | integer | no | Staff ID of the assignee. Use 0 for unassigned. |
| `company_id` | integer | no | Company ID from list_companies. |
| `priority` | string | no | Priority name as shown in Accelo. |
| `submitted_after` | string | no | ISO date. Only tickets submitted after it. |
| `last_interaction_before` | string | no | ISO date. Only tickets with no message or note since then. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tickets without their messages. Filters are standing, status, assignee, company, priority, a submitted-after date and a last-interaction-before date. By default only tickets with a standing of submitted or open are returned. Newest submitted first. Pages hold up to 100 tickets; pass next_cursor back as cursor for the next page. Use get_ticket for the full thread.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 1042,
      "title": "Export fails with an error",
      "standing": "open",
      "status": "Active",
      "priority": "Normal",
      "class": "Bug",
      "company": "Brightwave Studio",
      "contact": "Dana Whitfield",
      "assignee": "Sam Okafor",
      "date_submitted": "2026-10-15T08:12:00Z",
      "date_last_interacted": "2026-10-15T09:40:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_ticket

One ticket with its fields, tasks and every message and note. Access: read. REST: `GET /api/v1/accelo/tickets/{ticket_id}`. MCP: `accelo_read → get_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |

Returns one ticket with title, description, standing, status, priority, class, client, contact, assignee, dates and the activities on it, oldest first. Each activity says whether it is an email, note, call or meeting, who wrote it and the time logged. Use it before replying so your agent sees the whole thread.

Example response:

```json
{
  "ticket_id": 1042,
  "title": "Export fails with an error",
  "description": "Clicking Export on the monthly report shows an error after a few seconds.",
  "standing": "open",
  "status": "Active",
  "priority": "Normal",
  "class": "Bug",
  "company": "Brightwave Studio",
  "contact": {
    "name": "Dana Whitfield",
    "email": "dana@example.com"
  },
  "assignee": "Sam Okafor",
  "billable_minutes": 40,
  "activities": [
    {
      "activity_id": 5530,
      "medium": "email",
      "from": "Dana Whitfield",
      "subject": "Export fails",
      "body": "It fails every time on the October report.",
      "date": "2026-10-15T08:12:00Z",
      "minutes": 0
    },
    {
      "activity_id": 5541,
      "medium": "note",
      "from": "Sam Okafor",
      "subject": "Checked logs",
      "body": "Fails above 5,000 rows.",
      "date": "2026-10-15T09:40:00Z",
      "minutes": 40
    }
  ]
}
```

### list_companies

Client companies that match a search, with status and manager. Access: read. REST: `GET /api/v1/accelo/companies`. MCP: `accelo_read → list_companies`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of the company name. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches companies by name and returns their ID, status and manager. Use the ID to filter tickets, projects and invoices. Pages hold up to 100 companies; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "companies": [
    {
      "company_id": 39,
      "name": "Brightwave Studio",
      "status": "Active client",
      "manager": "Priya Nair",
      "website": "https://brightwave.example"
    }
  ],
  "next_cursor": null
}
```

### list_contacts

People at a client company, with email and phone. Access: read. REST: `GET /api/v1/accelo/contacts`. MCP: `accelo_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `company_id` | integer | no | Company ID from list_companies. |
| `search` | string | no | Part of the name or email. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the contacts of one company, or contacts that match a search across your Accelo. Each contact has the name, email, phone and whether the person is the main contact. Use it to find who a ticket, quote or invoice goes to.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": 98,
      "name": "Dana Whitfield",
      "email": "dana@example.com",
      "phone": "+1 555 0100",
      "company": "Brightwave Studio",
      "main_contact": true
    }
  ],
  "next_cursor": null
}
```

### list_projects

Projects with status, client, manager and due date. Access: read. REST: `GET /api/v1/accelo/projects`. MCP: `accelo_read → list_projects`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `company_id` | integer | no | Company ID from list_companies. |
| `status` | string | no | Status name as shown in Accelo. |
| `manager_id` | integer | no | Staff ID of the project manager. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns projects without their tasks. Filter by company, status or manager. Newest first. Each project has its current status name, which you can pass back to update_project. Pages hold up to 100 projects; pass next_cursor back as cursor.

Example response:

```json
{
  "projects": [
    {
      "project_id": 214,
      "title": "Website Redesign",
      "company": "Brightwave Studio",
      "status": "Active",
      "manager": "Priya Nair",
      "date_due": "2026-12-15"
    }
  ],
  "next_cursor": null
}
```

### list_tasks

Tasks on tickets and projects, with assignee, status and due date. Access: read. REST: `GET /api/v1/accelo/tasks`. MCP: `accelo_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `against_type` | enum | no | ticket or project. |
| `against_id` | integer | no | Ticket or project ID. |
| `assignee_id` | integer | no | Staff ID of the assignee. |
| `status` | string | no | Status name as shown in Accelo, e.g. Started. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tasks that match your filters, with the ticket or project each one belongs to. Task status is one of the names Accelo shows, such as Pending, Started or Complete. Ordered by due date, soonest first. Pages hold up to 100 tasks.

Example response:

```json
{
  "tasks": [
    {
      "task_id": 7710,
      "title": "Reproduce the export error",
      "against": {
        "type": "ticket",
        "id": 1042
      },
      "assignee": "Sam Okafor",
      "status": "Started",
      "priority": "Normal",
      "date_due": "2026-10-17"
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Invoices with amount, amount outstanding, raised date and due date. Access: read. REST: `GET /api/v1/accelo/invoices`. MCP: `accelo_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `company_id` | integer | no | Company ID from list_companies. |
| `due_before` | string | no | ISO date. Only invoices due before it. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns invoices with the subject, amount without tax, tax, amount outstanding including tax, the date raised and the due date, plus the client. Read only: Accelo's API has no call to create an invoice. Filter by company or due date. Pages hold up to 100 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": 75,
      "subject": "October retainer",
      "company": "Brightwave Studio",
      "amount": "1200.00",
      "tax": "120.00",
      "outstanding": "1320.00",
      "date_raised": "2026-10-01",
      "date_due": "2026-10-15"
    }
  ],
  "next_cursor": null
}
```

### reply_to_ticket

Send an email reply to the client on a ticket. Access: write, asks the user first. REST: `POST /api/v1/accelo/tickets/{ticket_id}/replies`. MCP: `accelo_write → reply_to_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `body` | string | yes | The message text. |
| `cc` | array | no | Email addresses to copy. |

Creates an email activity on the ticket and sends it to the ticket's contact, with any CC addresses you pass. It appears in the ticket thread like a reply written in Accelo and is billable by default, as activities on tickets are. It logs no time unless you also call log_time. Accelo sends it as you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "activity_id": 5562,
  "ticket_id": 1042,
  "medium": "email",
  "to": "dana@example.com",
  "sent": true,
  "date": "2026-10-16T09:05:00Z"
}
```

### add_ticket_note

Add a private note to a ticket. Access: write. REST: `POST /api/v1/accelo/tickets/{ticket_id}/note`. MCP: `accelo_write → add_ticket_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `body` | string | yes | The note text. |

Creates a note activity on the ticket, private to your team and sent to no client. Use it to leave the reason for a change. It reaches no one, so it does not ask for confirmation. Edit or delete the note in Accelo if it is wrong.

Example response:

```json
{
  "activity_id": 5563,
  "ticket_id": 1042,
  "medium": "note",
  "visibility": "private",
  "date": "2026-10-16T09:06:00Z"
}
```

### log_time

Log time on a ticket or project, billable or not. Access: write. REST: `POST /api/v1/accelo/againsts/{against_id}/times`. MCP: `accelo_write → log_time`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `against_type` | enum | yes | ticket or project. |
| `against_id` | integer | yes | Ticket or project ID. |
| `minutes` | integer | yes | Minutes to log. |
| `subject` | string | yes | What the time was spent on. |
| `date` | string | no | ISO date of the work. Default: today. |
| `billable` | boolean | no | Default: true. |

Creates a time entry on a ticket or project for the minutes and day you give, as you, with a subject. Time on tickets and projects is billable unless you pass billable false. The entry reaches no one and nothing is invoiced from it until you approve the time in Accelo. Edit or delete the entry in Accelo if it is wrong, so it does not ask for confirmation.

Example response:

```json
{
  "activity_id": 5564,
  "against": {
    "type": "ticket",
    "id": 1042
  },
  "subject": "Export fix",
  "minutes": 45,
  "hours": 0.75,
  "billable": true,
  "date": "2026-10-16"
}
```

### update_ticket

Change a ticket's status, priority, class or assignee. Access: write, asks the user first. REST: `PATCH /api/v1/accelo/tickets/{ticket_id}`. MCP: `accelo_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `status` | string | no | Status name as shown in Accelo. |
| `priority` | string | no | Priority name as shown in Accelo. |
| `class` | string | no | Ticket class name as shown in Accelo. |
| `assignee_id` | integer | no | Staff ID of the new assignee. |

Updates the fields you pass and leaves the rest. Status is set by name, so Accelo runs the progression for that status and may need more details for it; the raw standing field is not used. A locked ticket cannot be changed. Setting an assignee informs that person. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 1042,
  "title": "Export fails with an error",
  "status": "Active",
  "priority": "High",
  "class": "Bug",
  "assignee": "Sam Okafor",
  "updated": true
}
```

### create_task

Create a task on a ticket or project. Access: write, asks the user first. REST: `POST /api/v1/accelo/againsts/{against_id}/tasks`. MCP: `accelo_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `against_type` | enum | yes | ticket or project. |
| `against_id` | integer | yes | Ticket or project ID. |
| `title` | string | yes | Task title. |
| `description` | string | no | Task details. |
| `assignee_id` | integer | no | Staff ID of the assignee. |
| `due_date` | string | no | ISO date. |
| `priority` | string | no | Priority name as shown in Accelo. |

Creates a task with a title against a ticket or project, and returns it with its status, which starts as Pending until the assignee accepts it. An assignee can be notified about the task. Set a due date and priority from the names Accelo shows. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 7712,
  "title": "Ship the export fix",
  "against": {
    "type": "ticket",
    "id": 1042
  },
  "assignee": "Sam Okafor",
  "status": "Pending",
  "priority": "High",
  "date_due": "2026-10-20"
}
```

### create_quote

Create a draft quote on a sale. Access: write, asks the user first. REST: `POST /api/v1/accelo/sales/{sale_id}/quotes`. MCP: `accelo_write → create_quote`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `sale_id` | integer | yes | Sale the quote belongs to. |
| `title` | string | yes | Quote title, usually the project name. |
| `manager_id` | integer | no | Staff ID of the quote manager. |
| `template` | string | no | Quote template name as shown in Accelo. |

Creates a quote with a title on a sale, with the manager and quote template you pass, and returns it as a draft. It does not publish or send the quote; building the estimate and Publish & Send happen in Accelo. Changing the template later does not refill the content. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "quote_id": 318,
  "title": "Website Redesign, phase 2",
  "sale_id": 96,
  "manager": "Priya Nair",
  "template": "Standard proposal",
  "status": "Draft"
}
```

### update_project

Change a project's title, status, manager or due date. Access: write, asks the user first. REST: `PATCH /api/v1/accelo/projects/{project_id}`. MCP: `accelo_write → update_project`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `title` | string | no | New title. |
| `status` | string | no | Status name as shown in Accelo. |
| `manager_id` | integer | no | Staff ID of the new manager. |
| `due_date` | string | no | ISO date. |

Updates the fields you pass and returns the project. Status is set by name from the statuses your Accelo shows in list_projects. A new manager is informed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "project_id": 214,
  "title": "Website Redesign",
  "status": "Active",
  "manager": "Priya Nair",
  "date_due": "2026-12-22",
  "updated": true
}
```

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

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

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

2. **Sign in to Accelo in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Accelo 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 Accelo 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 new Accelo tickets. Set the priority from what the client wrote, put billing questions in the Billing class and bugs in the Bug class, and add a private note with the reason. Leave unclear ones for me.
```

### Call Accelo 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/accelo 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/accelo/againsts/1042/times \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"against_type":"ticket","minutes":45,"subject":"Export fix","billable":true,"date":"2026-10-16"}'
```

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

```
{
  "activity_id": 5564,
  "against": {
    "type": "ticket",
    "id": 1042
  },
  "subject": "Export fix",
  "minutes": 45,
  "hours": 0.75,
  "billable": true,
  "date": "2026-10-16"
}
```

## Why use Cotlet for Accelo?

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

## Is it safe to connect Accelo to Cotlet?

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

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

## Is there a Accelo MCP server on GitHub?

Yes. Community Accelo MCP servers exist on GitHub, usually maintained by one person. You install one yourself, register an OAuth application in Accelo, and fix the server when Accelo changes. Cotlet hosts the same kind of server for you, works in your signed-in Accelo session, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, register an OAuth application under Configuration > API, store its client secret, add the server to each MCP client | Sign up, sign in to Accelo once, add one MCP server or API key |
| When Accelo 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 Accelo access | Client secret and tokens 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 | Tools fail until you refresh the token or sign in again by hand | Your Cloud Browser keeps you signed in; if Accelo 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 Accelo 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 Accelo API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Accelo 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 Accelo 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 Accelo 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 Accelo only after you enable it. When Accelo 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 Accelo, sign out of Accelo 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.
- **Accelo's terms:** You use your own Accelo account and stay responsible for following Accelo's terms. Cotlet is independent and not affiliated with Accelo. [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 Accelo in the console and press Request access. Then you create your API key and connect Accelo there.

**Do I need to be technical?**

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

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

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

**Does Accelo's own MCP server cover this?**

Partly. Accelo's MCP page says an assistant can read your projects, time entries, budgets and invoices through a remote MCP server an admin sets up, and that teams can soon also act through it, for example logging time or updating tasks (checked 17 Oct 2026). Cotlet adds the writes today, such as replying to tickets and creating tasks, and works from your own signed-in session.

**What can my agent change in Accelo?**

What your Accelo user can change. Accelo keeps permissions per user, and a ticket that was approved and reconciled for invoicing is locked and cannot be edited.

**Is there a rate limit?**

Accelo limits its API to 5,000 requests per hour per deployment and answers 429 beyond that (checked 17 Oct 2026). The limit is shared by every integration on your deployment, which is why list tools page in batches of up to 100.

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

No. Every call to reply_to_ticket, update_ticket, create_task, create_quote or update_project 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_ticket_note, log_time runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Accelo 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/accelo 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.