Skip to content

Ticketing

Dixa MCP connector

The Dixa connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read the custom attributes set up in your Dixa account, so anyone can ask what fields exist and how each one is defined.

Connect on Elaichi How to connect

  • 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 Dixa to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Dixa once

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

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

  3. Paste a Dixa API key. One person generates a token in Dixa 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.

dixa
Dixa
Airtable
Asana
Autotask
Basecamp
ClickUp
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.

Connect Dixa to 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.

Connect Dixa to 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.

Connect Dixa to 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 Dixa 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.

Connect Dixa on Elaichi See pricing

Use cases

What teams do with Dixa through Elaichi

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

  • Support

    Check which conversation fields agents must fill

    Ask which custom attributes are set up in Dixa before a shift starts, so nobody guesses at field names or picks the wrong one when tagging a conversation.

  • Support operations

    Look up the options behind a dropdown

    Pull a single Dixa custom attribute by its ID and see exactly which values it offers, useful when someone asks why a reason code is missing from the list.

  • Quality assurance

    Spot duplicate or stale attributes

    List every custom attribute in Dixa and ask the AI to point out fields with near-identical names or labels that no longer match how the team works.

  • Enablement

    Write the handbook page on Dixa fields

    Draft a plain-language guide to every custom attribute in Dixa, with its label, type, and options, without copying anything by hand from the admin screen.

  • Analytics

    Confirm the field a report depends on

    Before building a dashboard on a Dixa attribute, check its ID, type, and current options so the report matches what agents are actually able to select.

  • IT

    Review attribute setup after a Dixa change

    After an admin edits fields in Dixa, ask for the full list of custom attributes and compare it with last week's to confirm only the intended changes landed.

Try asking

  • “List all Dixa custom attributes used on conversations.”
  • “Show the Dixa custom attribute behind ticket priority.”
  • “Which Dixa custom attributes are missing values this week?”

See all 2 Dixa tools below

AI tools

Dixa tools for your AI agents

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

See it in Elaichi

What connecting Dixa gets you

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

The agent

Ask Dixa questions, get answers back.

Type a question in plain language and read live Dixa custom attributes.

  • custom attributes
  • conversations
  • tickets
  • queues

Ask Elaichi to work across your apps.

List all Dixa custom attributes used on conversations.

Show the Dixa custom attribute behind ticket priority.

Which Dixa custom attributes are missing values this week?

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Dixa.

One org-wide MCP endpoint over OAuth, no SDK 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

Emma Laurent

 • Connected 4 minutes ago
Cursor
S

Sofia Ricci

 • Connected 2 hours ago
ChatGPT
C

Clara Nowak

 • Connected Yesterday

Tool catalog

2 Dixa tools ready without custom code.

Browse every Dixa tool name, resource and method in one catalog.

  • List all Dixa custom attributes
  • Get single Dixa custom attribute by ID
ElaichiTools
Tool Action Description
List all Dixa custom attributes List List all custom attributes in Dixa. Returns id, entityType, identifier, label, inputDefinition, description, createdAt, updatedAt, isRequired, isArchived, and isDeactivated fields for each custom attribute.
Get single Dixa custom attribute by ID Get Get custom attribute by id in Dixa. Returns id, entityType, identifier, label, inputDefinition, description, createdAt, updatedAt, isRequired, isArchived, and isDeactivated.

Toolboxes

Every team gets its own Dixa toolbox.

Support, quality and operations each see the Dixa tools their work needs.

  • Support
  • Quality
  • Operations
  • Customer Success
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Dixa · conversations and tickets

 Dixa starter 18 Mar 4, 2026

Quality toolbox

Dixa · conversation reviews and tags

 — 9 Mar 2, 2026

Operations toolbox

Dixa · queues and routing

 — 24 Feb 27, 2026

Customer Success toolbox

Dixa · accounts and escalations

 Dixa starter 6 Feb 19, 2026

Analytics toolbox

Dixa · custom attributes and reporting

 — 31 Jan 30, 2026

Enablement toolbox

Dixa · agents and workflows

 — 12 Jan 22, 2026

Shared connections

Teammates use Dixa without seeing credentials.

See who connected each Dixa account and how many teams share it.

  • Support EMEA
  • Support Americas
  • Support APAC
  • Quality
ElaichiConnections
Connection Scope Status Access
DI

Dixa (Support EMEA)

Connected by Emma Laurent

 Personal • Active 1 team · 6 members
DI

Dixa (Support Americas)

Connected by James Whitfield

 Organization • Active 3 teams · 24 members
DI

Dixa (Support APAC)

Connected by Sofia Ricci

 Organization • Active 2 teams · 11 members
DI

Dixa (Quality)

Connected by Daniel Ortega

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

Dixa (Operations)

Connected by Clara Nowak

 Personal • Active Not shared
DI

Dixa (Customer Success)

Connected by Michael Brennan

 Personal • Active 2 teams · 9 members

Audit log

Every Dixa call is written down.

When, who, what happened, type and resource for each Dixa request.

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

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emma Laurent

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

James Whitfield

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
S

Sofia Ricci

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
D

Daniel Ortega

[email protected]

 Dixa Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
C

Clara Nowak

[email protected]

 Dixa Custom attributes Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
M

Michael Brennan

[email protected]

 Dixa Custom attributes 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 runs Dixa work end to end.

Fetch custom attributes, group them, draft a digest, approve, post back to Dixa.

Dixa digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch custom attributes

    Dixa

    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

    Dixa

    Queued

Collections and dashboards

Dixa health arrives before anyone asks.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

Dixa health

Refreshed 4 minutes ago · every 15 minutes · from the custom attributes collection

Live

Custom attributes

1,284 ↓ 12%

Conversations

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Custom attributes created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support Americas 27%

Support APAC 21%

Quality 18%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

How do I connect Dixa to Claude?

Connect Dixa in Elaichi first: paste a Dixa API key from your Dixa settings, since Dixa connects with an API key and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when prompted and Dixa is available in Claude.

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

Yes. Once Dixa 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 Dixa once and every client sees it.

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

With this connector an agent can read the custom attributes defined in Dixa: the list of every field, plus the details of any one field such as its label, type, and the options it offers. That means you can ask which fields agents fill on a conversation, what values a dropdown allows, or whether two attributes overlap. It does not create, edit, or delete anything in Dixa.

Does connecting Dixa give the AI access to my whole Dixa account?

No. Access to Dixa follows the API key that was used to connect, and the AI can only read what that key can read, which through this connector is limited to custom attributes. Elaichi can narrow that further with restrictions, and it never widens what the Dixa key itself allows.

Can my team share one Dixa connection?

Yes. One person connects Dixa with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so every question asked of Dixa is logged under the name of the person who asked it.

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

This Dixa connector is read-only, so an agent cannot delete or change custom attributes through it. Restrictions in Elaichi also work per action, and a blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Dixa connection when someone leaves?

When a person is offboarded in Elaichi their access to the Dixa connection ends immediately, in every client they had set up. A shared Dixa connection keeps working for everyone else on the team. If you want to remove Dixa entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Dixa in front of your team

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

Connect Dixa Talk to us