Jitbit Helpdesk MCP server

What the model can do

Jitbit Helpdesk tickets: lists by status, category, technician, company, tag and created or updated dates, full-text search, a ticket with its replies, helpdesk counts, categories, priorities and technicians, knowledge base articles, users and companies; when you ask, can create tickets, reply or add internal notes, update, assign, close, tag, log time, set custom fields, add or remove subscribers, request or give approval, link or merge tickets, and create or edit knowledge base articles.

Reads

• jitbit_list_ticketsHelpdesk tickets, as the token's user may see them: subject, status, priority, category, who it is from (name and company), assignee, created…
• jitbit_search_ticketsFull-text search of helpdesk tickets for a phrase, optionally narrowed by submitter, assignee, category, status or created dates.
• jitbit_get_ticketOne helpdesk ticket in full: subject, body, status, priority, category, tags, submitter and assignee names, dates, time spent, attachment names…
• jitbit_statsHelpdesk counts right now: total, new, in progress, unanswered, unassigned, unclosed and closed tickets, and those handled by the token's user.
• jitbit_list_categoriesTicket categories (with sections) and priorities, the ids that creating and updating tickets take; with category_id…
• jitbit_knowledge_baseKnowledge base articles: without article_id, the list with titles, categories, dates and links (optionally one category); with article_id…
• jitbit_list_usersHelpdesk users (needs an administrator token): id, name, company, department, whether administrator or disabled, last seen.
• jitbit_list_companiesCompanies the helpdesk knows (needs an administrator token), with their ids and email domain.

Acts, when you ask

These change something in Jitbit Helpdesk. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• jitbit_create_ticketCreates a helpdesk ticket in a category.
• jitbit_replyPosts a reply on a helpdesk ticket.
• jitbit_update_ticketChanges a helpdesk ticket's status, priority, category, assignee (0 unassigns), due date, subject or body; only the fields passed change.
• jitbit_close_ticketCloses a helpdesk ticket.
• jitbit_tag_ticketAdds a tag (new or existing) to a helpdesk ticket, keeping its other tags.
• jitbit_log_timeLogs time spent on a helpdesk ticket, under the token's user (a technician).
• jitbit_set_custom_fieldSets one custom field on a helpdesk ticket: true or false for a checkbox, the option id for a dropdown, a date as text.
• jitbit_add_subscriberSubscribes a helpdesk user to a ticket, so they are emailed its replies from now on.
• jitbit_remove_subscriberUnsubscribes a helpdesk user from a ticket; they stop receiving its replies and are not told.
• jitbit_request_approvalAsks a helpdesk user to approve a ticket.
• jitbit_decide_approvalApproves or rejects a ticket's pending approval request, as the token's user (who must be the approver or an administrator).
• jitbit_link_ticketsLinks two helpdesk tickets as related; both stay open and nobody is notified.
• jitbit_merge_ticketsMerges ticket merge_ticket_id into primary_ticket_id.
• jitbit_create_articlePublishes a knowledge base article in a category; with techs_only false it is visible to customers.
• jitbit_update_articleReplaces a knowledge base article's subject, body, category and visibility (all four are sent, as Jitbit's method takes them).

Connect it

First connect Jitbit Helpdesk on Dashboard → Connections, then add Memtro to your client once. The Jitbit Helpdesk tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Jitbit Helpdesk connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which tickets are unanswered?
• › How many tickets are open and unassigned right now?
• › Search tickets for printer driver.
• › Show ticket 4512 with its replies.
• › Add an internal note to ticket 4512 saying we are waiting on the supplier.

Questions

Is this an official Jitbit Helpdesk MCP server?

No. It is Memtro's MCP server with Memtro's Jitbit Helpdesk connector behind it: the connector reads Jitbit Helpdesk through its API with the credentials you connect on Dashboard → Connections, and Jitbit Helpdesk publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Jitbit Helpdesk?

Only when you ask, and only what it has been granted: create a ticket; reply to a ticket or add an internal note; update, re-assign or re-categorise a ticket; close a ticket; tag a ticket; log time spent on a ticket; set a custom field on a ticket; add a subscriber to a ticket; remove a subscriber from a ticket; request approval on a ticket; approve or reject a ticket's pending approval; link two tickets as related; merge one ticket into another; create a knowledge base article; edit a knowledge base article. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server