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.

Ticketing

Dixa MCP connector

The Dixa connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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

Connects with an API key
Free 14-day trial
No credit card

ChatGPT Elaichi connected

List all Dixa custom attributes used on conversations.

Working in Dixa with Elaichi

List all Dixa custom attributes
Get single Dixa custom attribute by ID

Ask anything…

Governance / Audit log Last 24 hours

Get single Dixa custom attribute by ID Emily Carter ·

9:41 AM Done

List all Dixa custom attributes Emily Carter ·

9:41 AM Done

List all Dixa custom attributes Megan Brooks ·

9:38 AM Done

List all Dixa custom attributes Ryan Hayes ·

9:35 AM Done

How to connect Dixa to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

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

Dixa MCP connector for Claude Code

1

In a terminal, run claude mcp add with 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.

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

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

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

Connect Dixa on Elaichi See pricing

What teams do with Dixa through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Dixa is logged.

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 →

What connecting Dixa gets you

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

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Dixa questions, get answers back.

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

ElaichiAI apps

Claude

ChatGPT

Cursor

Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Dixa.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

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.

Tool catalog

2 Dixa tools ready without custom code.

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

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

Toolboxes

Every team gets its own Dixa toolbox.

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

ElaichiConnections

Connection	Scope	Status	Access
DI Dixa (Support EMEA) Connected by Emily Carter	Personal	• Active	1 team · 6 members
DI Dixa (Support Americas) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
DI Dixa (Support APAC) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
DI Dixa (Quality) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
DI Dixa (Operations) Connected by Ryan Hayes	Personal	• Active	Not shared
DI Dixa (Customer Success) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Shared connections

Teammates use Dixa without seeing credentials.

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

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	Dixa Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Dixa Custom attributes Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Dixa Custom attributes List	Toolbox

Audit log

Every Dixa call is written down.

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

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.

Dixa digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch custom attributes

Dixa

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

Dixa

Queued

Automations

A schedule runs Dixa work end to end.

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

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%

Collections and dashboards

Dixa health arrives before anyone asks.

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

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Dixa

All three can connect Dixa to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Dixa, by what to check
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 Dixa tools	Allow or restrict single Dixa 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 Dixa 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.

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.

More from the catalog

Browse all 650+ connectors →

Questions, answered

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, Microsoft Copilot, 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 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 restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, and every other client at the same time.

Does the Dixa MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Dixa 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 Dixa?

Yes. Both let Claude, ChatGPT or Cursor use Dixa. 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 Dixa call.

How is Elaichi different from Composio for Dixa?

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 Dixa: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Dixa in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

Connect Dixa Talk to us

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