Skip to content

Connectors / Ticketing

Ticketing MCP connectors for Claude, ChatGPT and Cursor

15+ Ticketing connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

Start 14-day free trial Browse the full catalog
https://api.elaichi.ai/mcp The same for every user.

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

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Ticketing connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

19 connectors

Browse all 600+ connectors →

In practice

What teams do with Ticketing connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Support

  • Asana

    Log a customer escalation as a task

    Describe the problem a customer reported and have a task created for the engineering team, with the reproduction steps written up as subtasks and the ticket details in a comment.

  • ClickUp

    Find every open task for one customer

    Ask which ClickUp tasks mention a customer or a problem and get the list back with current status, so the desk knows what is already in progress.

  • Thena

    Find who to contact at an account

    Ask for the contacts on a Thena account and get names and roles back, so the reply goes to the right person the first time.

Operations

  • ConnectWise PSA

    Keep the member list current

    When a technician changes role or joins a new team, update their ConnectWise PSA member record by asking for the change rather than clicking through the setup screens.

  • Kaseya BMS

    Find a site's details without hunting

    Pull up a client location in Kaseya BMS by name or ID to confirm the address and site contacts before a technician heads out.

  • Basecamp

    Set up a new project in minutes

    Describe the kickoff and the agent creates the Basecamp project, adds the to-do lists your team always uses, and fills in the first round of to-dos with owners and due dates.

IT

  • DevRev

    Review who has a DevRev seat

    List DevRev team members and system users, check who is active, and update details when roles change.

  • Hive

    Onboard and offboard Hive users

    Add a new hire as a Hive user, adjust their role tag when they change jobs, and remove the account when they leave, with each change logged to whoever asked for it.

  • Airtable

    Review who is doing what across Airtable

    Ask for recent audit activity, look up a user or a user group, and check which webhooks are set up on a base. Update or remove a user account when someone changes role.

Marketing

  • Linear

    Pull release notes before an announcement

    Ask for the latest Linear release and its release notes, then draft the changelog post or customer email from what actually shipped.

  • Todoist

    See what is overdue before the launch

    Ask which tasks in the campaign project are still open, reopen anything that was closed too early, and add a comment asking the owner for a status.

  • Monday.com

    Pull the brief out of a doc

    Read a campaign brief in Monday.com docs block by block and get the goals, dates, and owners summarized for someone who joined the project late.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Ticketing account you connected.

  • Summarize records added to the Support Queue table this week.

    Airtable

  • List my overdue tasks in the Q3 Launch project.

    Asana

  • How many Autotask tickets are open for Acme this week?

    Autotask

  • Which Basecamp todos are overdue across active projects?

    Basecamp

  • Which tasks in the Engineering space are overdue this week?

    ClickUp

  • Show open tickets on the Service Desk board

    ConnectWise PSA

  • Summarize tickets opened this week by rev org.

    DevRev

  • List all Dixa custom attributes used on conversations.

    Dixa

The tools

What an agent can call in Ticketing

Connectors
15+

in the Ticketing catalog

Tools
4,547

callable the moment you connect

Hosted sign-in
9

connect with nothing to register

Of those 4,547 tools, 10% delete something. Restricting an agent to reads is not a promise here, it is 2,253 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 50%
2,253 tools · list, get, search
Write 26%
1,190 tools · create, update, send
Delete 10%
473 tools · delete, remove, archive
Other 14%
631 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Ticketing connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.

Ticketing connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
ConnectWise PSA 2,858 API key
Kaseya BMS 329 API key
ServiceNow 230 App credentials
Asana 190 Hosted
ClickUp 174 Hosted
Thena 131 API key
Basecamp 104 Hosted
DevRev 101 API key
Hive 73 API key
Linear 68 Hosted
Airtable 56 Hosted
Jira 41 Hosted
Linq 41 API key
Autotask 37 API key
Todoist 35 Hosted
Jira Service Management 30 Hosted
ServiceNow SCIM 24 Your own app
Monday.com 23 Hosted
Dixa 2 API key

FAQ

Frequently asked questions

How many Ticketing connectors does Elaichi have?

15+ Ticketing connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Ticketing connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. Connecting a Ticketing account once makes it reachable from every one of them.

Do Ticketing connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Ticketing connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Ticketing connectors need me to bring my own OAuth app?

Most do not. 9 of the Ticketing connectors use Elaichi's hosted sign-in, with nothing to register. 9 connect with an API key or app credentials that an admin pastes once, with no app to register. 1 asks you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to Ticketing tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is left out of the model's tool list and cannot be called. Read-only access to a Ticketing connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Ticketing connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Ticketing usually connect these too

Put Ticketing connectors in front of your team

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

Start free trial Talk to us
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.