Jitbit API and MCP server

Jitbit's built-in AI connection can search, read and reply to tickets, but it cannot assign, close, merge or create them. Sign in to Jitbit once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with Jitbit.

Jitbit has no API for this. So we run one for you.

Jitbit's own API, a GitHub MCP server and Cotlet compared
What you need Jitbit's APIGitHub MCP serverCotlet
Assign, close, merge and create tickets No No Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Jitbit changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 22, 2026. Sources: Jitbit Helpdesk Docs: MCP Server · Jitbit Helpdesk Docs: Helpdesk API reference · Jitbit Helpdesk Docs: Ticket page · Jitbit Helpdesk Docs: Tickets grid (list)

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Jitbit in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Jitbit to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Jitbit and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/jitbit with its own method and path, such as POST /api/v1/jitbit/technicians/{technician_id}/tickets/{ticket_id}/assign, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Jitbit API and MCP server do?

14 tools on your own Jitbit account. Agents call them as operations of the MCP tools jitbit_read and jitbit_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

Jitbit tools in Cotlet's MCP server and REST API
Tool What it does Access
list_tickets Tickets you may see, filtered by mode, category, status, priority, tag, company or date. read
search_tickets Tickets that match a search phrase, with optional category, status, technician or date filters. read
get_ticket One ticket with its details, tags and every comment, public and technician-only. read
list_categories Ticket categories you may see, with their section. read
list_technicians Technicians who can be assigned tickets in one category. read
list_canned_responses Canned responses with name, folder and text. read
search_kb Knowledge base articles that match a phrase, with category and tags. read
get_kb_article One knowledge base article with its full text. read
reply_to_ticket Post a reply to the customer or an internal note for technicians on a ticket. writeasks first
update_ticket Change priority, status, category, due date or tags of one ticket. writeasks first
assign_ticket Assign one ticket to a technician. writeasks first
close_ticket Close one ticket, optionally without the closed email. writeasks first
create_ticket Create a ticket in a category, optionally on behalf of a user and assigned to a technician. writeasks first
merge_tickets Merge one ticket into another. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect Jitbit?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the Jitbit API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Jitbit is enabled for agents, so 20 calls a day come to 550 credits.

Cotlet credit packs: price, credits and calls at 25 credits each
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.

Questions

Does Jitbit have an 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.

How do I get access?

Sign up free, open Jitbit under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Jitbit yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Jitbit sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: reply_to_ticket, update_ticket, assign_ticket, close_ticket, create_ticket, merge_tickets wait for your OK by default. You can switch that off per tool for scheduled runs.

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

Should I use a Jitbit MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Jitbit changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Jitbit?

No. Cotlet is independent and not affiliated with Jitbit.

Give your agent access to Jitbit.

Free 7-day trial with 2,000 credits, no card needed.