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

# Jitbit API and MCP server

> Jitbit has a full REST API and an official MCP server built into every SaaS helpdesk (checked 22 Oct 2026). The MCP searches and reads tickets and KB articles and posts replies and internal notes. It cannot assign, change status or priority, close, create or merge tickets: that takes the REST API and code you write and host.

Help desk software for support teams: tickets from email, a web form and a widget, a knowledge base, automation rules and reports, as SaaS or self-hosted.

## What is the Jitbit API?

Cotlet's Jitbit API exposes 14 endpoints for your own Jitbit account: list tickets, search tickets, get ticket, list categories, list technicians for a category, list canned responses, search knowledge base, get knowledge base article, reply to ticket, update ticket, assign ticket, close ticket, create ticket and merge tickets. The list_tickets endpoint returns tickets you may see, filtered by mode, category, status, priority, tag, company or date. Each endpoint takes simple JSON inputs like ticket_id, category_id or status and works both as an operation of the jitbit_read or jitbit_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 (8 read, 6 write)
- **Updated:** 2026-10-18

Jitbit has a full REST API and an official MCP server built into every SaaS helpdesk (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Jitbit with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Jitbit have an official API?

Jitbit has a full REST API and an official MCP server built into every SaaS helpdesk (checked 22 Oct 2026). The MCP searches and reads tickets and KB articles and posts replies and internal notes. It cannot assign, change status or priority, close, create or merge tickets: that takes the REST API and code you write and host.

| Task | Jitbit official | Cotlet |
|---|---|---|
| Search tickets and KB articles and read a ticket thread | Yes: Official MCP and REST API | Yes |
| List tickets by mode, category, status, tag, company or date | Partly: The MCP filters by mode and status only; the REST API filters by more | Yes |
| Reply to a ticket or add an internal note | Yes: Official MCP and REST API | Yes |
| Assign a ticket to a technician | Partly: REST API only; the MCP cannot | Yes |
| Change priority, status, category, due date or tags | Partly: REST API only; the MCP cannot | Yes |
| Close a ticket, with or without the closed email | Partly: REST API only; the MCP cannot | Yes |
| Create a ticket on behalf of a user | Partly: REST API only; the MCP cannot | Yes |
| Merge duplicate tickets | Partly: REST API only; the MCP cannot, and a merge cannot be undone | Yes |

Sources: [Jitbit Helpdesk Docs: MCP Server](https://www.jitbit.com/docs/mcp/), [Jitbit Helpdesk Docs: Helpdesk API reference](https://www.jitbit.com/helpdesk/helpdesk-api/), [Jitbit Helpdesk Docs: Ticket page](https://www.jitbit.com/docs/viewissue/), [Jitbit Helpdesk Docs: Tickets grid (list)](https://www.jitbit.com/docs/activetickets/)

## For AI agents

```text
Jitbit has a full REST API and an official MCP server built into every SaaS helpdesk (checked 22 Oct 2026). The MCP searches and reads tickets and KB articles and posts replies and internal notes. It cannot assign, change status or priority, close, create or merge tickets: that takes the REST API and code you write and host.
Cotlet provides a hosted MCP server and REST API for Jitbit: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=jitbit, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    jitbit_read, jitbit_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/jitbit, each operation at its own route, e.g. POST /api/v1/jitbit/technicians/{technician_id}/tickets/{ticket_id}/assign
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, search_tickets, get_ticket, list_categories, list_technicians, list_canned_responses, search_kb, get_kb_article, reply_to_ticket, update_ticket, assign_ticket, close_ticket, create_ticket, merge_tickets
Confirm      reply_to_ticket, update_ticket, assign_ticket, close_ticket, create_ticket, merge_tickets (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/jitbit-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=jitbit, requests Jitbit in the Cotlet console and creates an API key there.
2. The user signs in to Jitbit once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Jitbit 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 Jitbit server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Jitbit 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 Jitbit 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 Jitbit 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 Jitbit's terms; Cotlet is not affiliated with Jitbit.
```

## What can an AI agent do in Jitbit?

Cotlet is best for support leads and small teams who want an AI agent to triage, assign, close and merge Jitbit tickets without running or fixing a server, or writing REST code for what the official MCP skips.

- **[Triage unassigned tickets](https://cotlet.dev/integrations/jitbit-api-mcp-server/triage-unassigned-tickets.md)** (runs: daily): "Go through the unassigned Jitbit tickets. Pick the right category and a technician from that category, set the priority from what the customer wrote, and leave anything unclear for me." → `list_tickets`, `get_ticket`, `list_categories`, `list_technicians`, `update_ticket`, `assign_ticket`
- **[Close stale tickets](https://cotlet.dev/integrations/jitbit-api-mcp-server/close-stale-tickets.md)** (runs: weekly): "Find Jitbit tickets nobody has touched for 14 days where we sent the last reply. Add an internal note saying why, then close them without the closed email. Show me anything where the customer wrote last." → `list_tickets`, `get_ticket`, `reply_to_ticket`, `close_ticket`
- **[Merge duplicate tickets](https://cotlet.dev/integrations/jitbit-api-mcp-server/merge-duplicate-tickets.md)** (runs: weekly): "Find open Jitbit tickets from the same customer about the same problem this week. Merge the newer ones into the oldest and leave an internal note on the one that stays." → `search_tickets`, `get_ticket`, `merge_tickets`, `reply_to_ticket`
- **Create tickets on behalf of customers** (runs: weekly): "Take this list of customer requests from our call notes and create a Jitbit ticket for each in the right category on behalf of the customer, assigned to me." → `list_categories`, `create_ticket`
- **Reply from canned responses** (runs: daily): "For the unanswered Jitbit tickets, find the canned response that fits and post it as a reply. If none fits, search the knowledge base and show me a draft instead of sending." → `list_tickets`, `get_ticket`, `list_canned_responses`, `search_kb`, `reply_to_ticket`
- **Weekly support backlog report** (runs: weekly): "Every Monday, tell me how many Jitbit tickets are unanswered, unassigned and unclosed per category, the oldest unclosed ticket in each, and anything Critical with no technician." → `list_categories`, `list_tickets`

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

Yes. Cotlet does not replace your automation platform: it gives it a Jitbit 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 unassigned 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/jitbit/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/jitbit/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 Jitbit.

### list_tickets

Tickets you may see, filtered by mode, category, status, priority, tag, company or date. Access: read. REST: `GET /api/v1/jitbit/tickets`. MCP: `jitbit_read → list_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `mode` | enum | no | unanswered, unclosed, unassigned, handledbyme or all. Default: all. |
| `category` | string | no | Category name, as in the left menu of the Tickets page. |
| `status` | string | no | Status name, for example New, In process, Resolved or one of your custom statuses. |
| `priority` | string | no | Priority name, for example Low, Normal, High, Critical or a custom one. |
| `tag` | string | no | Only tickets with this tag. |
| `company` | string | no | Only tickets from this company. |
| `updated_before` | string | no | ISO date, for example 2026-10-08. Only tickets last updated before it. |
| `updated_after` | string | no | ISO date. Only tickets last updated after it. |
| `limit` | integer | no | How many to return. Default: 25. |
| `offset` | integer | no | How many to skip, for the next page. Default: 0. |

Returns tickets with status, priority, category, submitter, company, assigned technician and last update, without comments. mode matches the tabs of the Tickets page: unanswered, unclosed, unassigned, handledbyme or all. Only tickets your Jitbit user may see are returned: a technician sees the categories they handle and an administrator sees everything. Use offset to read the next page and get_ticket for the full thread.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 5128,
      "subject": "Cannot log in after password reset",
      "status": "New",
      "priority": "Normal",
      "category": "Technical support",
      "submitter": "Maya Brandt",
      "company": "Brandt Studio",
      "assigned_to": null,
      "created_at": "2026-10-22T06:41:00Z",
      "last_updated": "2026-10-22T06:41:00Z",
      "last_updated_by": "customer"
    }
  ],
  "offset": 0
}
```

### search_tickets

Tickets that match a search phrase, with optional category, status, technician or date filters. Access: read. REST: `GET /api/v1/jitbit/tickets/search`. MCP: `jitbit_read → search_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Words to find in the ticket subject and body. |
| `category_id` | integer | no | Category ID from list_categories. |
| `status` | string | no | Status name. |
| `technician_id` | integer | no | Only tickets assigned to this technician, from list_technicians. |
| `created_after` | string | no | ISO date. Only tickets created after it. |
| `created_before` | string | no | ISO date. Only tickets created before it. |
| `limit` | integer | no | How many to return. Default: 25. |

Searches the tickets you may see for a phrase and returns the matches with status, priority, category, submitter and assigned technician, without comments. Narrow the search with a category, a status, a technician or a creation date range. Use get_ticket for the full thread.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 5104,
      "subject": "Still cannot log in",
      "status": "New",
      "priority": "Normal",
      "category": "Technical support",
      "submitter": "Maya Brandt",
      "assigned_to": null,
      "created_at": "2026-10-22T08:05:00Z"
    }
  ]
}
```

### get_ticket

One ticket with its details, tags and every comment, public and technician-only. Access: read. REST: `GET /api/v1/jitbit/tickets/{ticket_id}`. MCP: `jitbit_read → get_ticket`.

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

Returns one ticket with subject, body, status, priority, category, submitter, company, assigned technician, due date, time spent, tags and all comments in order, oldest first. Each comment says who wrote it and whether it is for technicians only. System entries such as status changes are marked as system. Use it before replying or closing so your agent sees the whole thread.

Example response:

```json
{
  "ticket_id": 4871,
  "subject": "Invoice copy",
  "body": "Hi, could you resend the invoice for September?",
  "status": "In process",
  "priority": "Normal",
  "category": "Billing",
  "submitter": {
    "name": "Dana Whitfield",
    "email": "dana@example.com",
    "company": "Whitfield Print"
  },
  "assigned_to": "Priya Nair",
  "due_date": null,
  "tags": [
    "invoice"
  ],
  "created_at": "2026-10-01T09:12:00Z",
  "last_updated": "2026-10-01T10:30:00Z",
  "comments": [
    {
      "comment_id": 90112,
      "author": "Priya Nair",
      "for_techs_only": false,
      "system": false,
      "body": "Hi Dana, the invoice is attached.",
      "created_at": "2026-10-01T10:30:00Z"
    }
  ]
}
```

### list_categories

Ticket categories you may see, with their section. Access: read. REST: `GET /api/v1/jitbit/categories`. MCP: `jitbit_read → list_categories`.

No parameters.

Lists the categories your Jitbit user has permission to see, with ID, name, section and whether the category is for technicians only. A ticket has one category, and categories decide which technicians handle it. Use category_id with update_ticket, create_ticket and list_technicians.

Example response:

```json
{
  "categories": [
    {
      "category_id": 7277,
      "name": "Technical support",
      "section": null,
      "for_techs_only": false
    },
    {
      "category_id": 7278,
      "name": "Billing",
      "section": null,
      "for_techs_only": false
    },
    {
      "category_id": 7290,
      "name": "Onboarding",
      "section": "Customers",
      "for_techs_only": false
    }
  ]
}
```

### list_technicians

Technicians who can be assigned tickets in one category. Access: read. REST: `GET /api/v1/jitbit/categories/{category_id}/technicians`. MCP: `jitbit_read → list_technicians`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `category_id` | integer | yes | Category ID from list_categories. |

Returns the technicians and administrators who can take tickets in the category, with ID, name and how many tickets each one has assigned. Use technician_id with assign_ticket or create_ticket. A technician who has no access to the category is not listed.

Example response:

```json
{
  "technicians": [
    {
      "technician_id": 14,
      "name": "Priya Nair",
      "tickets_assigned": 12
    },
    {
      "technician_id": 9,
      "name": "Sam Okafor",
      "tickets_assigned": 7
    }
  ]
}
```

### list_canned_responses

Canned responses with name, folder and text. Access: read. REST: `GET /api/v1/jitbit/canned-responses`. MCP: `jitbit_read → list_canned_responses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `category_id` | integer | no | Category ID from list_categories. |
| `query` | string | no | Only responses whose name contains this text. |

Lists the canned responses available to your Jitbit user, with name, folder and body. Responses can be mapped to ticket categories in the admin area, so pass category_id to get the ones that apply to a ticket. Use the body as the text of reply_to_ticket.

Example response:

```json
{
  "responses": [
    {
      "response_id": 1420,
      "name": "Resend invoice",
      "folder": "Billing",
      "body": "Hi, the invoice you asked for is attached to this reply."
    },
    {
      "response_id": 362,
      "name": "Which app?",
      "folder": null,
      "body": "Could you tell me which app you are talking about?"
    }
  ]
}
```

### search_kb

Knowledge base articles that match a phrase, with category and tags. Access: read. REST: `GET /api/v1/jitbit/kbs/search`. MCP: `jitbit_read → search_kb`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Words to find in the article subject, body and tags. |
| `limit` | integer | no | How many to return. Default: 25. |

Searches article subjects, bodies and tags and returns the matches with ID, subject, category and tags. Only articles your Jitbit user may see are returned. Use get_kb_article to read one. The official Jitbit MCP offers the same search.

Example response:

```json
{
  "articles": [
    {
      "article_id": 87,
      "subject": "Reset your password",
      "category": "Accounts",
      "tags": [
        "password",
        "login"
      ]
    }
  ]
}
```

### get_kb_article

One knowledge base article with its full text. Access: read. REST: `GET /api/v1/jitbit/articles/{article_id}/kb-article`. MCP: `jitbit_read → get_kb_article`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `article_id` | integer | yes | Article ID from search_kb. |

Returns the article with subject, category, tags, dates and the full text, which your agent can summarize or paste into a reply. Only articles your Jitbit user may see can be read. The official Jitbit MCP offers the same read.

Example response:

```json
{
  "article_id": 87,
  "subject": "Reset your password",
  "category": "Accounts",
  "tags": [
    "password",
    "login"
  ],
  "body": "Open the login page, click the forgot password link, enter your email and follow the link we send you.",
  "updated_at": "2026-09-12T10:00:00Z"
}
```

### reply_to_ticket

Post a reply to the customer or an internal note for technicians on a ticket. Access: write, asks the user first. REST: `POST /api/v1/jitbit/tickets/{ticket_id}/replies`. MCP: `jitbit_write → reply_to_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets or search_tickets. |
| `body` | string | yes | Comment text. Plain text is fine. |
| `for_techs_only` | boolean | no | true for a note only technicians see, false for a reply the customer sees. Default: false. |

Posts a comment as your Jitbit user. With for_techs_only set to true it is a note only technicians see. Otherwise the comment is emailed to the ticket followers, by default the submitter and the assigned person. The official Jitbit MCP can post comments too; use this tool when the same job also assigns, closes or merges. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 4871,
  "comment_id": 90140,
  "for_techs_only": true,
  "created_at": "2026-10-22T09:00:00Z"
}
```

### update_ticket

Change priority, status, category, due date or tags of one ticket. Access: write, asks the user first. REST: `PATCH /api/v1/jitbit/tickets/{ticket_id}`. MCP: `jitbit_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets or search_tickets. |
| `priority` | string | no | Priority name: Low, Normal, High, Critical or a custom one. |
| `status` | string | no | Status name from your helpdesk, for example In process or a custom status. |
| `category_id` | integer | no | Category ID from list_categories. |
| `due_date` | string | no | ISO date. |
| `add_tags` | string[] | no | Tags to add, keeping the existing ones. |

Updates the fields you pass and leaves the rest. A new ticket must be In process before it can move to a custom status. Moving a ticket to another category runs your automation rules for category changes, and a status change can email the submitter. Tags are added to the ticket, not replaced. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 5128,
  "status": "In process",
  "priority": "High",
  "category": "Technical support",
  "due_date": null,
  "tags": [
    "login"
  ],
  "updated_at": "2026-10-22T09:02:00Z"
}
```

### assign_ticket

Assign one ticket to a technician. Access: write, asks the user first. REST: `POST /api/v1/jitbit/technicians/{technician_id}/tickets/{ticket_id}/assign`. MCP: `jitbit_write → assign_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets or search_tickets. |
| `technician_id` | integer | yes | Technician ID from list_technicians. |

Sets the Assigned to field of the ticket, the same as choosing a technician on the ticket page. Assigning a new ticket moves it to In process. Pick the technician from list_technicians for the ticket's category. The technician may be notified by email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 5128,
  "assigned_to": {
    "technician_id": 14,
    "name": "Priya Nair"
  },
  "status": "In process",
  "updated_at": "2026-10-22T09:03:00Z"
}
```

### close_ticket

Close one ticket, optionally without the closed email. Access: write, asks the user first. REST: `POST /api/v1/jitbit/tickets/{ticket_id}/close`. MCP: `jitbit_write → close_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets or search_tickets. |
| `silent` | boolean | no | true to close without the Ticket closed email. Default: false. |

Closes the ticket, which sets its status to Resolved. With silent set to true the Ticket closed email to the user is skipped, the same as Close silently in the more menu; that option exists only if the closed email notification is enabled in your helpdesk. A closed ticket can be re-opened from its page. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 4871,
  "status": "Resolved",
  "notification_sent": false,
  "closed_at": "2026-10-22T09:04:00Z"
}
```

### create_ticket

Create a ticket in a category, optionally on behalf of a user and assigned to a technician. Access: write, asks the user first. REST: `POST /api/v1/jitbit/categories/{category_id}/tickets`. MCP: `jitbit_write → create_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `category_id` | integer | yes | Category ID from list_categories. |
| `subject` | string | yes | Ticket subject. |
| `body` | string | yes | Ticket text. |
| `priority` | string | no | Priority name: Low, Normal, High, Critical or a custom one. Default: Normal. |
| `on_behalf_of` | string | no | Email of the user the ticket is created for. Needs technician or administrator permissions. |
| `technician_id` | integer | no | Technician ID from list_technicians. |
| `suppress_confirmation` | boolean | no | true to skip the confirmation email to the user. Default: false. |

Creates a ticket with subject, body and priority, the same as the New ticket form. With on_behalf_of the ticket is created for another user, which needs technician or administrator permissions, and with technician_id it is assigned right away. The user may get a confirmation email unless suppress_confirmation is true. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 5140,
  "subject": "Export to CSV fails",
  "category": "Technical support",
  "priority": "Normal",
  "submitter": "Dana Whitfield",
  "assigned_to": "Priya Nair",
  "status": "In process",
  "created_at": "2026-10-22T09:05:00Z"
}
```

### merge_tickets

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

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket that stays and receives the merge. |
| `merged_ticket_id` | integer | yes | Ticket that is merged in and deleted. |

Merges the second ticket into the first, the same as Merge on the ticket page. A merge cannot be undone, and the ticket that is merged in is deleted. Read both threads with get_ticket first so only tickets about the same problem are joined. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 5090,
  "merged_ticket_id": 5104,
  "merged_at": "2026-10-22T09:06:00Z"
}
```

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

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

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

2. **Sign in to Jitbit in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Jitbit 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 Jitbit 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 the unassigned Jitbit tickets. Pick the right category and a technician from that category, set the priority from what the customer wrote, and leave anything unclear for me.
```

### Call Jitbit 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/jitbit 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/jitbit/technicians/14/tickets/5128/assign \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

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

```
{
  "ticket_id": 5128,
  "assigned_to": {
    "technician_id": 14,
    "name": "Priya Nair"
  },
  "status": "In process",
  "updated_at": "2026-10-22T09:03:00Z"
}
```

## Why use Cotlet for Jitbit?

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

## Is it safe to connect Jitbit to Cotlet?

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

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

## Is there a Jitbit MCP server on GitHub?

Yes. Jitbit ships its own MCP server, free with your helpdesk, and it reads and replies well. It stops at search, read and replies. For assigning, closing, merging or creating tickets you would call the REST API from code you write and host. Cotlet hosts the full set for you and signs in as your technician user.

|  | Jitbit MCP | Cotlet |
|---|---|---|
| Setup | Add your helpdesk URL with /api/mcp and your API token to each MCP client, or sign in with OAuth | Sign up, sign in to Jitbit once, add one MCP server or API key |
| What it does | Searches and reads tickets and KB articles, posts replies and internal notes | The same, plus assign, change priority and status, close, merge and create tickets |
| Your Jitbit access | A personal API token in each client config, or an OAuth approval you grant per client | 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 | A changed password invalidates your API token, so every client config needs the new one | Your Cloud Browser keeps you signed in; if Jitbit logs you out, your agent gets a link to sign in again |
| When Jitbit changes | Jitbit maintains it; anything outside it is your own code against the REST API | Our team tests it daily and fixes it for you; failed calls are free |
| Where it runs | Hosted by your helpdesk; your own scripts run where you host them | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Included with your helpdesk | 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 Jitbit 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 Jitbit API cost?

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

**Do I need to be technical?**

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

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

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

**The official Jitbit MCP can already reply. What does Cotlet add?**

The official MCP searches and reads tickets and KB articles and posts replies and internal notes, and nothing else. Cotlet covers those too and adds assigning, priority, status and category changes, closing, merging and creating tickets (Jitbit Docs: MCP Server, checked 22 Oct 2026).

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

It acts as your own user, so it sees only the tickets you can see: a technician sees the categories they handle and an administrator sees all. Creating a ticket on behalf of someone needs technician or administrator permissions (Jitbit Docs: New Ticket Form).

**Does closing a ticket email the customer?**

By default Jitbit sends a Ticket closed email if that notification is enabled. close_ticket can close silently, the same as Close silently in the ticket menu, which appears only when the notification is enabled (Jitbit Docs: Ticket page).

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

No. Every call to reply_to_ticket, update_ticket, assign_ticket, close_ticket, create_ticket or merge_tickets waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Jitbit 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/jitbit 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.