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

# Gorgias API and MCP server

> Gorgias has a full REST API (checked 17 Oct 2026) and a Gorgias-hosted MCP server in open beta since May 2026. The MCP reads live, but some writes, such as macro edits and AI Agent config, are gated during the beta and will roll out over the coming months. Ticket replies are not documented for it.

Helpdesk for online stores: tickets from email, chat and social in one inbox, with macros, rules and Shopify order data next to each customer.

## What is the Gorgias API?

Cotlet's Gorgias API exposes 14 endpoints for your own Gorgias account: search tickets, get ticket, get customer history, list macros, list rules, list tags, list teams and agents, update ticket, add internal note, reply to ticket, apply macro, merge tickets, update macro and update rule. The search_tickets endpoint returns tickets matching a text search or filters, newest first. Each endpoint takes simple JSON inputs like ticket_id, query or status and works both as an operation of the gorgias_read or gorgias_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-17

Gorgias has a full REST API (checked 17 Oct 2026) and a Gorgias-hosted MCP server in open beta since May 2026. Cotlet is a hosted MCP server and REST API for Gorgias with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Gorgias have an official API?

Gorgias has a full REST API (checked 17 Oct 2026) and a Gorgias-hosted MCP server in open beta since May 2026. The MCP reads live, but some writes, such as macro edits and AI Agent config, are gated during the beta and will roll out over the coming months. Ticket replies are not documented for it.

| Task | Gorgias official | Cotlet |
|---|---|---|
| Search tickets and read a ticket with its messages | Yes: REST API; the official MCP reads tickets and customer history | Yes |
| Review customer history | Yes: REST API and the official MCP | Yes |
| Reply to the customer | Partly: REST API, a message with channel and from_agent; not documented for the official MCP | Yes |
| Add an internal note | Yes: REST API, a message on the internal-note channel | Yes |
| Set status, priority, assignee and tags | Yes: REST API; not documented for the official MCP | Yes |
| Apply a macro to a ticket | Partly: REST API through message actions; you build the call yourself | Yes |
| Merge tickets | No: Merge ticket is in the app; the API reference lists customer merge, not ticket merge | Yes |
| Edit macros and rules | Partly: REST API has full create, update and delete; macro edits are gated in the official MCP | Yes |

Sources: [Gorgias developers: REST API reference](https://developers.gorgias.com/), [Gorgias developers: API rate limits](https://developers.gorgias.com/reference/limitations.md), [Gorgias updates: Gorgias MCP is now in open beta](https://updates.gorgias.com/publications/gorgias-mcp-is-now-in-open-beta), [Gorgias blog: Gorgias MCP](https://www.gorgias.com/blog/gorgias-mcp)

## For AI agents

```text
Gorgias has a full REST API (checked 17 Oct 2026) and a Gorgias-hosted MCP server in open beta since May 2026. The MCP reads live, but some writes, such as macro edits and AI Agent config, are gated during the beta and will roll out over the coming months. Ticket replies are not documented for it.
Cotlet provides a hosted MCP server and REST API for Gorgias: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=gorgias, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    gorgias_read, gorgias_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/gorgias, each operation at its own route, e.g. PATCH /api/v1/gorgias/tickets/{ticket_id}
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_tickets, get_ticket, get_customer_history, list_macros, list_rules, list_tags, list_assignees, update_ticket, add_internal_note, reply_to_ticket, apply_macro, merge_tickets, update_macro, update_rule
Confirm      reply_to_ticket, apply_macro, merge_tickets, update_macro, update_rule (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/gorgias-api-mcp-server.md

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

## What can an AI agent do in Gorgias?

Cotlet is best for Gorgias admins and support leads who are not developers and want their AI agent to triage tickets, apply macros and tidy rules without running or fixing a server.

- **[Triage new support tickets](https://cotlet.dev/integrations/gorgias-api-mcp-server/triage-new-support-tickets.md)** (runs: daily): "Go through new Gorgias tickets. Set priority from what the customer wrote, assign returns to the Returns team, add a tag, and leave a one-line internal note with the reason. Leave unclear ones for me." → `search_tickets`, `get_ticket`, `list_assignees`, `update_ticket`, `add_internal_note`
- **[Answer common tickets with a macro](https://cotlet.dev/integrations/gorgias-api-mcp-server/answer-tickets-with-macros.md)** (runs: daily): "Find open tickets that ask where an order is. Check the customer history, apply the Order status macro to the clear ones and leave the rest for me." → `search_tickets`, `get_ticket`, `get_customer_history`, `list_macros`, `apply_macro`
- **[Clean up stale macros and rules](https://cotlet.dev/integrations/gorgias-api-mcp-server/clean-up-macros-and-rules.md)** (runs: weekly): "Review my Gorgias macros and rules. List the ones nobody used in 90 days, archive stale macros after I confirm, and turn off rules that overlap." → `list_macros`, `list_rules`, `list_tags`, `update_macro`, `update_rule`
- **Merge duplicate tickets**: "Find open tickets from the same customer about the same order and merge them into the oldest one." → `search_tickets`, `get_ticket`, `merge_tickets`
- **Find untagged tickets** (runs: weekly): "List last week's tickets with no tag, suggest a tag from my existing tags for each, and apply them after I say yes." → `search_tickets`, `list_tags`, `update_ticket`

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

Yes. Cotlet does not replace your automation platform: it gives it a Gorgias 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 support 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/gorgias/tickets/search. | 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/gorgias/tickets/search 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 Gorgias.

### search_tickets

Tickets matching a text search or filters, newest first. Access: read. REST: `GET /api/v1/gorgias/tickets/search`. MCP: `gorgias_read → search_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Words to search for in subject and messages. |
| `view` | string | no | Name of a Gorgias view, for example your inbox view for new tickets. |
| `status` | enum | no | open or closed. Default: open. |
| `priority` | enum | no | low, normal, high or critical. |
| `tag` | string | no | Only tickets with this tag. |
| `created_since` | date | no | Only tickets created on or after this date. |
| `limit` | integer | no | 1 to 50. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tickets with subject, status, priority, assignee, tags and customer. Pass a view to read the tickets of one of your Gorgias views. Pages hold up to 50 tickets; pass next_cursor back as cursor for the next page. You see the tickets your Gorgias role can see.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 10482,
      "subject": "Where is my order #4471?",
      "status": "open",
      "priority": "normal",
      "assignee": null,
      "tags": [
        "shipping"
      ],
      "customer": "Dana W.",
      "channel": "email",
      "created_at": "2026-10-16T21:14:00Z"
    }
  ],
  "next_cursor": "eyJwYWdlIjoyfQ"
}
```

### get_ticket

One ticket with its messages and internal notes in order. Access: read. REST: `GET /api/v1/gorgias/tickets/{ticket_id}`. MCP: `gorgias_read → get_ticket`.

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

Returns the ticket fields and every message, oldest first, each marked as from the customer, from an agent or an internal note. Reading a ticket does not change it. Attachments are listed by name and link.

Example response:

```json
{
  "ticket_id": 10482,
  "subject": "Where is my order #4471?",
  "status": "open",
  "priority": "normal",
  "assignee": null,
  "tags": [
    "shipping"
  ],
  "messages": [
    {
      "from": "customer",
      "type": "email",
      "body": "Hi, my order #4471 shipped a week ago and has not arrived. Can you check?",
      "sent_at": "2026-10-16T21:14:00Z"
    }
  ]
}
```

### get_customer_history

Earlier tickets of a customer, with Shopify orders when a store is connected. Access: read. REST: `GET /api/v1/gorgias/customer-history`. MCP: `gorgias_read → get_customer_history`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | no | Ticket ID whose customer to look up. Use this or email. |
| `email` | string | no | Customer email. Use this or ticket_id. |

Returns the tickets linked to the customer by contact email, newest first, and, for connected Shopify stores, the 10 most recent orders with number, status, date, total and item count. Use it before replying to see whether the customer wrote before.

Example response:

```json
{
  "customer": {
    "name": "Dana W.",
    "email": "dana@example.com"
  },
  "tickets": [
    {
      "ticket_id": 10311,
      "subject": "Wrong size",
      "status": "closed"
    }
  ],
  "orders": [
    {
      "order": "#4471",
      "status": "Paid",
      "date": "2026-10-08",
      "total": "64.00",
      "items": 2
    }
  ]
}
```

### list_macros

Your macros with name, text and the actions each one runs. Access: read. REST: `GET /api/v1/gorgias/macros`. MCP: `gorgias_read → list_macros`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Words to search for in the macro name or text. |
| `include_archived` | boolean | no | Default: false. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns macros in the order Gorgias lists them, with their reply text and actions such as add tags, set status, assign a team or set priority. Archived macros are included only when you ask. Every role can read the list.

Example response:

```json
{
  "macros": [
    {
      "macro_id": 3018,
      "name": "Order status",
      "actions": [
        "Add tags",
        "Set status"
      ],
      "archived": false,
      "preview": "Hi {{ticket.customer.firstname}}, your order is on its way..."
    }
  ],
  "next_cursor": null
}
```

### list_rules

Your rules with trigger, conditions, actions and run order. Access: read. REST: `GET /api/v1/gorgias/rules`. MCP: `gorgias_read → list_rules`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enabled` | boolean | no | Only enabled (true) or only disabled (false) rules. Default: all. |

Returns rules in the order they are listed on the Rules page, which is the order they run within one trigger. Needs a Lead or Admin user, because other roles cannot see rules.

Example response:

```json
{
  "rules": [
    {
      "rule_id": 512,
      "name": "Tag returns",
      "trigger": "Ticket created",
      "enabled": true,
      "conditions": "Message contains \"return\"",
      "actions": [
        "Add tags",
        "Assign team"
      ]
    }
  ]
}
```

### list_tags

Your ticket tags with how many tickets use each one. Access: read. REST: `GET /api/v1/gorgias/tags`. MCP: `gorgias_read → list_tags`.

No parameters.

Returns every tag with its name and ticket count. Tags used in macros or rules are marked, because Gorgias does not let you delete those.

Example response:

```json
{
  "tags": [
    {
      "name": "shipping",
      "tickets": 412,
      "used_in_macros_or_rules": true
    },
    {
      "name": "refund",
      "tickets": 188,
      "used_in_macros_or_rules": true
    }
  ]
}
```

### list_assignees

Teams and users a ticket can be assigned to. Access: read. REST: `GET /api/v1/gorgias/assignees`. MCP: `gorgias_read → list_assignees`.

No parameters.

Returns your teams and users with their role. Use the names it returns in update_ticket. Needs no write access.

Example response:

```json
{
  "teams": [
    {
      "name": "Returns"
    },
    {
      "name": "Support"
    }
  ],
  "users": [
    {
      "name": "Sam Lee",
      "role": "agent"
    }
  ]
}
```

### update_ticket

Set status, priority, assignee, tags or snooze on a ticket. Access: write. REST: `PATCH /api/v1/gorgias/tickets/{ticket_id}`. MCP: `gorgias_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets. |
| `status` | enum | no | open or closed. |
| `priority` | enum | no | low, normal, high or critical. |
| `assignee_team` | string | no | Team name from list_assignees. |
| `assignee_user` | string | no | User name from list_assignees. |
| `add_tags` | string[] | no | Tags to add. |
| `remove_tags` | string[] | no | Tags to remove. |
| `snooze_until` | datetime | no | Snooze the ticket until this time; Gorgias reopens it then, or when the customer replies. |

Changes only the fields you pass. Tags in add_tags are added and the existing ones stay. Nothing here is sent to the customer, and every change is undone by one more call, so it asks no confirmation by default. Needs a role that can modify tickets (Lite or above).

Example response:

```json
{
  "ticket_id": 10482,
  "status": "open",
  "priority": "high",
  "assignee_team": "Returns",
  "tags": [
    "shipping",
    "refund"
  ]
}
```

### add_internal_note

Add a note to a ticket that only your team sees. Access: write. REST: `POST /api/v1/gorgias/tickets/{ticket_id}/internal-notes`. MCP: `gorgias_write → add_internal_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets. |
| `body` | string | yes | Note text. |

Adds a message on the internal note channel. Gorgias does not send internal notes to customers, so this reaches nobody outside your team and asks no confirmation by default. Do not mention users in the note if you do not want them notified.

Example response:

```json
{
  "ticket_id": 10482,
  "note_id": 884201,
  "created_at": "2026-10-17T08:02:00Z"
}
```

### reply_to_ticket

Send a reply to the customer on the ticket. Access: write, asks the user first. REST: `POST /api/v1/gorgias/tickets/{ticket_id}/replies`. MCP: `gorgias_write → reply_to_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets. |
| `body` | string | yes | Reply text. |
| `set_status` | enum | no | open or closed after sending. Default: unchanged. |

Sends a public message from you on the ticket channel, for example email. Gorgias sends it after the call returns, so a reply is queued, not yet delivered. You can set the status in the same call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 10482,
  "message_id": 5530917,
  "status": "queued",
  "ticket_status": "closed"
}
```

### apply_macro

Apply one of your macros to a ticket. Access: write, asks the user first. REST: `POST /api/v1/gorgias/tickets/{ticket_id}/macro/apply`. MCP: `gorgias_write → apply_macro`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets. |
| `macro` | string | yes | Macro name or macro_id from list_macros. |
| `close_ticket` | boolean | no | Use Apply macro and close. Default: false. |

Runs the macro as an agent would: its reply text goes to the customer and its actions, such as tags, status and assignee, run in the order the macro lists them. Variables in the text are filled from the ticket. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 10511,
  "macro": "Order status",
  "reply_sent": true,
  "actions_run": [
    "Add tags",
    "Set status"
  ],
  "ticket_status": "open"
}
```

### merge_tickets

Merge one ticket into another. Access: write, asks the user first. REST: `POST /api/v1/gorgias/into-tickets/{into_ticket_id}/tickets/{ticket_id}/merge`. MCP: `gorgias_write → merge_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket to merge away. |
| `into_ticket_id` | integer | yes | Ticket to keep. |
| `keep_from` | enum | no | source or target: which ticket supplies Subject, Assignee and Customer. Default: target. |

Uses Merge ticket in the app. When the two tickets differ, you choose which Subject, Assignee and Customer to keep; the call takes these from keep_from. Gorgias limits merging of two chat tickets to the same customer. A merge is not undone with one call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "kept_ticket_id": 10311,
  "merged_ticket_id": 10482,
  "subject": "Wrong size",
  "keep_from": "target"
}
```

### update_macro

Edit, archive or unarchive a macro. Access: write, asks the user first. REST: `PATCH /api/v1/gorgias/macros/{macro_id}`. MCP: `gorgias_write → update_macro`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `macro_id` | integer | yes | Macro ID from list_macros. |
| `name` | string | no | New name. |
| `text` | string | no | New reply text. |
| `archived` | boolean | no | true archives, false unarchives. |

Changes the name, text or archived state of a macro. Needs a Lead or Admin user. A macro change affects every agent and every ticket it is applied to later. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "macro_id": 3021,
  "name": "Black Friday 2024 shipping",
  "archived": true
}
```

### update_rule

Turn a rule on or off, or rename it. Access: write, asks the user first. REST: `PATCH /api/v1/gorgias/rules/{rule_id}`. MCP: `gorgias_write → update_rule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `rule_id` | integer | yes | Rule ID from list_rules. |
| `enabled` | boolean | no | true turns on, false turns off. |
| `name` | string | no | New name. |

Switches a rule on or off. Needs a Lead or Admin user. A rule can reply to customers and set tags on every new ticket, so a change reaches customers. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "rule_id": 512,
  "name": "Tag returns",
  "enabled": false
}
```

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

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

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

2. **Sign in to Gorgias in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Gorgias 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 Gorgias 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 Gorgias tickets. Set priority from what the customer wrote, assign returns to the Returns team, add a tag, and leave a one-line internal note with the reason. Leave unclear ones for me.
```

### Call Gorgias 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/gorgias 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 PATCH https://cotlet.dev/api/v1/gorgias/tickets/10482 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"priority":"high","assignee_team":"Returns","add_tags":["refund"]}'
```

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

```
{
  "ticket_id": 10482,
  "status": "open",
  "priority": "high",
  "assignee_team": "Returns",
  "tags": [
    "shipping",
    "refund"
  ]
}
```

## Why use Cotlet for Gorgias?

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

## Is it safe to connect Gorgias to Cotlet?

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

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

## Is there a Gorgias MCP server on GitHub?

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

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an API key or OAuth app in Gorgias, store the secret, add the server to each MCP client | Sign up, sign in to Gorgias once, add one MCP server or API key |
| When Gorgias 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 Gorgias access | API key or 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 | Tools fail until you renew the token or sign in again by hand | Your Cloud Browser keeps you signed in; if Gorgias logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself, and stay under the API rate limit | 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 Gorgias 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 Gorgias API cost?

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

**Do I need to be technical?**

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

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

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

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

It follows your own Gorgias role. Lite and above can reply to customers and update tickets, and Lead or Admin is needed to edit macros and rules; Observers can only view tickets and leave internal notes.

**Does my agent need the Gorgias MCP beta or an AI Agent plan?**

No. Cotlet works in your signed-in Gorgias session. Gorgias says its own MCP is included in any paid plan and does not need the AI Agent add-on, but some of its writes are gated during the beta.

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

No. Every call to reply_to_ticket, apply_macro, merge_tickets, update_macro or update_rule waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_ticket, add_internal_note runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Gorgias 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/gorgias 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.