Skip to content

Jitbit MCP connector

Connecting Jitbit to Elaichi lets Claude, ChatGPT, Cursor and the Elaichi Agent search, create, update, merge and close Jitbit tickets inside each person's own help desk access, with every action written to an audit log.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Jitbit to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Jitbit once

  1. Open Connections, choose Add connection, and pick Jitbit.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Jitbit API key. One person generates a token in Jitbit and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

jitbit
Jitbit
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Jitbit MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Jitbit MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Jitbit MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Jitbit to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Jitbit through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Log a ticket straight after a call

    Describe the problem in plain words and the agent creates the Jitbit ticket, sets the priority and fills in the custom fields, so nothing waits until the end of the shift.

  • IT

    Merge duplicate tickets about one outage

    When the same printer or VPN failure lands as five tickets, ask the agent to find them, merge them into one and tag it, so the fix is tracked in a single place.

  • Support

    Pull in a second pair of hands

    Add a secondary assignee to a stuck Jitbit ticket and link it to the related ones, so the colleague picking it up sees the whole thread of the problem.

  • Operations

    Break a big request into subtickets

    Turn a new hire setup or office move into a parent ticket with subtickets for each piece of work, then check which subtickets are still open.

  • Customer Success

    Review a company's open tickets before a call

    Ask what is still unresolved for a particular company in Jitbit, with priorities and attachments, and walk into the renewal conversation already knowing the answer.

  • Team leads

    Check the help desk numbers each morning

    Ask for the current Jitbit stats, open tickets by priority and anything that has sat untouched, then close out what has been resolved without opening the queue.

Try asking

  • “Show open Jitbit tickets assigned to me this week”
  • “Close the duplicate Jitbit tickets linked to ticket 4821”
  • “Which Jitbit tickets have no assignee since Monday”

See all 64 Jitbit tools below

Compare

Elaichi vs Zapier MCP vs Composio for Jitbit

All three can connect Jitbit to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Jitbit, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Jitbit tools Allow or restrict single Jitbit tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Jitbit call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Jitbit tools for your AI agents

64 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jitbit, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Jitbit gets you

6 screens from the product, each doing one job for your Jitbit account.

The agent

Ask about Jitbit tickets in plain language.

Answers come from live Jitbit tickets, assignees and comments, not a stale export.

  • tickets
  • assignees
  • comments
  • subtickets

Ask Elaichi to work across your apps.

Show open Jitbit tickets assigned to me this week

Close the duplicate Jitbit tickets linked to ticket 4821

Which Jitbit tickets have no assignee since Monday

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Jitbit here.

One governed MCP endpoint for Jitbit, no SDK work and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

64 Jitbit tools are ready to call.

Tickets, assignees, links and subtickets are covered without writing custom code.

  • List all Jitbit authorization
  • List all Jitbit tickets
  • Get single Jitbit ticket by ID
  • Create a Jitbit ticket
ElaichiTools
Tool Action Description
List all Jitbit authorization List Test Jitbit authentication by verifying the current user's credentials. Returns the authenticated helpdesk user object including UserID, Username, Email, FirstName, LastName, IsAdmin, IsTech, IsManager, and LastSeen.
List all Jitbit tickets List List Jitbit helpdesk tickets with optional filters by category, status, date, assignee, tag, and more. Returns: UserName, FirstName, LastName, UserID, CompanyID, CompanyName, Email, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Max 300 per page.
Get single Jitbit ticket by ID Get Get details of a single Jitbit ticket by id. Returns: Attachments, Tags, Status, OnBehalfUserName, SubmitterUserInfo, CategoryName, AssigneeUserInfo, TicketID, UserID, AssignedToUserID, IssueDate, Subject, Body, Priority, StatusID, CategoryID, DueDate, ResolvedDate, StartDate, TimeSpentInSeconds, UpdatedByUser, UpdatedByPerformer, UpdatedForTechView, IsCurrentCategoryForTechsOnly, Username,…
Create a Jitbit ticket Create Create a new ticket in Jitbit. Returns the created ticket ID. Required: categoryId, body, subject, priorityId.
Update a Jitbit ticket by ID Update Update one or many ticket parameters in Jitbit by id. Returns an empty 204 response on success. Required: id. Subject and body are editable by admins or technicians only.

Toolboxes

Every team gets its own Jitbit toolbox.

Support, IT and operations each see the Jitbit tools their work needs.

  • Support
  • IT helpdesk
  • Escalations
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Jitbit · tickets and replies

Jitbit starter 18 Mar 4, 2026

IT helpdesk toolbox

Jitbit · internal tickets and assignees

— 9 Mar 2, 2026

Escalations toolbox

Jitbit · linked tickets and subtickets

— 24 Feb 27, 2026

Operations toolbox

Jitbit · ticket queues and reporting

Jitbit starter 6 Feb 19, 2026

Engineering toolbox

Jitbit · bug tickets and links

— 31 Jan 30, 2026

Customer success toolbox

Jitbit · account tickets and follow ups

— 12 Jan 22, 2026

Shared connections

Teammates work Jitbit tickets without a credential.

Each Jitbit connection shows who connected it and which teams and members share it.

  • Support EMEA
  • IT helpdesk
  • Escalations
  • Operations
ElaichiConnections
Connection Scope Status Access
JI

Jitbit (Support EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
JI

Jitbit (IT helpdesk)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
JI

Jitbit (Escalations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
JI

Jitbit (Operations)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
JI

Jitbit (Engineering triage)

Connected by Ryan Hayes

Personal • Active Not shared
JI

Jitbit (Customer success)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Jitbit call is written down.

When, who, what happened, type and resource for each ticket read and update.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Jitbit Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Jitbit Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Jitbit Tickets List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Jitbit tickets into a digest.

Six steps fetch and group Jitbit tickets, draft a digest, await approval, post back.

Jitbit digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tickets

    Jitbit

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Jitbit

    Queued

Collections and dashboards

Jitbit ticket health, counted on a schedule.

Four metrics, 14 days of tickets created and a team breakdown, computed without a model.

Jitbit health

Refreshed 4 minutes ago · every 15 minutes · from the tickets collection

Live

Tickets

1,284 ↓ 12%

Assignees

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Tickets created

Last 14 days

By team

Share of activity

Support EMEA 34%

IT helpdesk 27%

Escalations 21%

Operations 18%

FAQ

Frequently asked questions

How do I connect Jitbit to Claude?

Connect Jitbit in Elaichi first: paste in a Jitbit API key when asked, and the connection is ready. There is no OAuth application to register in Jitbit and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and from then on it can work with your Jitbit tickets.

Does Jitbit work with ChatGPT and Cursor as well as Claude?

Yes. Once Jitbit is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Jitbit once and every client you use picks it up.

What can an AI agent actually do with my Jitbit data?

It can search and read Jitbit tickets, create new ones, update them, set priorities and custom fields, add tags, assign a second person, link related tickets, merge duplicates, build parent and subtickets, close tickets and read attachments. It can also list your companies and pull the help desk stats for a quick status check. Because Jitbit brings a lot of actions, short concrete asks like "close ticket 4821" work better than long paragraphs.

Does connecting Jitbit give the AI access to every ticket in the help desk?

No. Each person signs in to Elaichi as themselves, so an agent working with Jitbit only sees the tickets, companies and fields that person's own Jitbit access allows. Elaichi can narrow that further with restrictions, and it can never widen what Jitbit already permits.

Can my team share one Jitbit connection?

Yes. One person connects Jitbit with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who created, updated or closed each Jitbit ticket.

Can I stop an agent from deleting or changing things in Jitbit?

Yes. Restrictions in Elaichi work per action, so you can allow reading and searching Jitbit tickets while blocking closing, merging or editing them. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

What happens to a Jitbit connection when someone leaves?

Offboarding that person in Elaichi ends their access to Jitbit through every client at once. If they had shared a Jitbit connection with a team, it keeps working for everyone else. If you want Jitbit gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Jitbit MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Jitbit is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Jitbit?

Yes. Both let Claude, ChatGPT or Cursor use Jitbit. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Jitbit call.

How is Elaichi different from Composio for Jitbit?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Jitbit: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Jitbit in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.