# Ticketing MCP connectors for Claude, ChatGPT and Cursor 15+ Ticketing connectors in the Elaichi catalog, each callable through https://api.elaichi.ai/mcp once connected, under the same roles, restrictions and audit log as the rest of the catalog. Source: https://elaichi.ai/connectors/category/ticketing/ | | | | --- | --- | | Category | Ticketing | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | ## Ticketing connectors - [Airtable](https://elaichi.ai/connectors/airtable/) — 56 tools · hosted sign-in - [Asana](https://elaichi.ai/connectors/asana/) — 190 tools · hosted sign-in - [Autotask](https://elaichi.ai/connectors/autotask/) — 37 tools · hosted sign-in - [Basecamp](https://elaichi.ai/connectors/basecamp/) — 103 tools · hosted sign-in - [ClickUp](https://elaichi.ai/connectors/clickup/) — 174 tools · hosted sign-in - [ConnectWise PSA](https://elaichi.ai/connectors/connectwisepsa/) — 2858 tools · hosted sign-in - [DevRev](https://elaichi.ai/connectors/devrev/) — 101 tools · hosted sign-in - [Dixa](https://elaichi.ai/connectors/dixa/) — 2 tools · hosted sign-in - [Hive](https://elaichi.ai/connectors/hive/) — 73 tools · hosted sign-in - [Jira](https://elaichi.ai/connectors/jira/) — 40 tools · hosted sign-in - [Jira Service Management](https://elaichi.ai/connectors/jiraservicemanagement/) — 30 tools · hosted sign-in - [Kaseya BMS](https://elaichi.ai/connectors/kaseyabms/) — 329 tools · hosted sign-in - [Linq](https://elaichi.ai/connectors/linq/) — 41 tools · hosted sign-in - [Monday.com](https://elaichi.ai/connectors/mondaycom/) — 23 tools · hosted sign-in - [ServiceNow](https://elaichi.ai/connectors/servicenow/) — 96 tools · hosted sign-in - [Thena](https://elaichi.ai/connectors/thena/) — 131 tools · hosted sign-in - [Todoist](https://elaichi.ai/connectors/todoist/) — 35 tools · hosted sign-in ## What teams do with Ticketing connectors ### Support - **Log a customer escalation as a task** (Asana) — 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. - **Find every open task for one customer** (ClickUp) — 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. - **Find who to contact at an account** (Thena) — 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 - **Keep the member list current** (ConnectWise PSA) — 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. - **Find a site's details without hunting** (Kaseya BMS) — Pull up a client location in Kaseya BMS by name or ID to confirm the address and site contacts before a technician heads out. - **Set up a new project in minutes** (Basecamp) — 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. ### Marketing - **Keep labels tidy across campaigns** (Hive) — Rename a stale Hive label, create a new one for the quarter's campaign, or retire one nobody uses, all from a plain-language request. - **Pull this week's content calendar into a summary** (Airtable) — Ask which pieces in the editorial base are due, blocked, or waiting on review, and get a plain answer instead of scrolling a grid. Create the next batch of records from a brief in one go. - **See what is overdue before the launch** (Todoist) — 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. ### IT - **Review who has a DevRev seat** (DevRev) — List DevRev team members and system users, check who is active, and update details when roles change. - **Clean up stale issues in a project** (Jira) — Find Jira issues nobody has touched in ninety days, add a comment asking the owner to confirm, and update the ones that should be closed. - **Get up to speed before a call** (Jira Service Management) — Pull a single request with its full comment thread and attachments so you walk into the call knowing what the customer already tried and what the last agent told them. ## Things to ask once it is 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) ## What an agent can call in Ticketing 4319 tools across the category. 17 of these connectors use hosted sign-in with nothing to register first; 0 ask you to bring your own OAuth app. ## 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, any MCP client and the Elaichi Agent all connect to that same address with OAuth. 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? No. Every Ticketing connector in the catalog connects through Elaichi's hosted sign-in, so there is nothing to register 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 never advertised to the model, so it cannot be called or guessed at from the tool list. 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. ## Related categories - [Helpdesk](https://elaichi.ai/connectors/category/helpdesk/) - [Incident Management](https://elaichi.ai/connectors/category/incident-management/) - [Application Development](https://elaichi.ai/connectors/category/application-development/) [Browse the full connector catalog](https://elaichi.ai/connectors/)