Helpdesk
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.
In Elaichi
Connect Jitbit once
-
Open Connections, choose Add connection, and pick Jitbit.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Jitbit to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Jitbit to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Jitbit to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Jitbit
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.
Put Jitbit in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.