Jitbit MCP connector
Connecting Jitbit to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Show open Jitbit tickets assigned to me this week
Working in Jitbit with Elaichi
-
List all Jitbit authorization
-
List all Jitbit tickets
-
Get single Jitbit ticket by ID
How to connect Jitbit to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Jitbit MCP connector for 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.
Jitbit MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Jitbit MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Jitbit MCP connector for 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.
Jitbit MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Jitbit through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Jitbit is logged.
-
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”
What connecting Jitbit gets you
6 screens from Elaichi, each doing one job for your Jitbit account.
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, Cursor or Microsoft Copilot
The agent
Ask about Jitbit tickets in plain language.
Answers come from live Jitbit tickets, assignees and comments, not a stale export.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Jitbit here.
One governed MCP endpoint for Jitbit, no SDK work and no shared API key.
Tool catalog
64 Jitbit tools are ready to call.
Tickets, assignees, links and subtickets are covered without writing custom code.
Toolboxes
Every team gets its own Jitbit toolbox.
Support, IT and operations each see the Jitbit tools their work needs.
Shared connections
Teammates work Jitbit tickets without a credential.
Each Jitbit connection shows who connected it and which teams and members share it.
Audit log
Every Jitbit call is written down.
When, who, what happened, type and resource for each ticket read and update.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Jitbit digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Jitbit
Queued
Automations
A schedule turns Jitbit tickets into a digest.
Six steps fetch and group Jitbit tickets, draft a digest, await approval, post back.
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%
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.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting closing, merging or editing them. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot