Helpdesk
Ada MCP connector
The Ada connector links your Ada helpdesk to Claude, ChatGPT, Cursor, and any MCP client, so your team can look up end users, tidy knowledge articles and sources, review audit events, and start email conversations by asking in plain language.
-
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 Ada to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Ada once
-
Open Connections, choose Add connection, and pick Ada.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Ada API key. One person generates a token in Ada 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.
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 Ada to 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.
Connect Ada to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Ada to 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.
Connect Ada 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.
Use cases
What teams do with Ada through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Look up a customer before replying
Ask for an end user's record in Ada by their ID and get their details back in the chat, then correct a name or contact detail without opening another tab.
-
Knowledge
Prune outdated knowledge articles
List the knowledge articles Ada is answering from, spot the ones that are stale, and remove them one at a time or in a batch so the assistant stops quoting old policy.
-
Knowledge
Add a new knowledge source
Point Ada at a new help center or document set by creating a knowledge source, or update the details of an existing one when the content moves.
-
Knowledge
Clean up knowledge tags in bulk
Review the tags applied across Ada knowledge articles, retire the ones nobody uses, and apply the right tags to a batch of articles in one go.
-
Support operations
Open a new channel for customers
See which channels Ada is already serving and create a new one when a team launches on a fresh surface, so conversations start landing in the right place.
-
Security and compliance
Review what changed in Ada
Pull the Ada audit log events for a given period to see who changed settings, articles, or connected platforms, and summarize them for a review.
Try asking
- “List Ada knowledge sources with no articles updated recently.”
- “Which Ada knowledge tags cover the most articles?”
- “Show Ada end users created in the last seven days.”
AI tools
Ada tools for your AI agents
47 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ada, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Ada gets you
6 screens from the product, each doing one job for your Ada account.
The agent
Ask about end users, get real answers.
Plain language questions run against live Ada end users, articles and tags.
- end users
- knowledge sources
- knowledge articles
- knowledge tags
Ask Elaichi to work across your apps.
List Ada knowledge sources with no articles updated recently.
Which Ada knowledge tags cover the most articles?
Show Ada end users created in the last seven days.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Ada.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
47 Ada tools ready to call.
End users, knowledge sources, articles and tags, with no custom code written.
- List all Ada audit log events
- Get single Ada end user by ID
- Update a Ada end user by ID
- List all Ada end users
Toolboxes
Every team gets its own Ada toolbox.
Support, knowledge and analytics each see only the Ada tools they need.
- Support
- Knowledge
- Content Ops
- Compliance
Shared connections
Share Ada access, never the credential.
See who connected each Ada account and which teams and members use it.
- Support EMEA
- Support US
- Knowledge Base
- Compliance
Audit log
Every Ada call is on the record.
When, who, what happened, type and resource for each article and end user.
- When
- Who
- What happened
- Type
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 fires, Ada work finishes.
Fetch end users, group them, draft a digest, approve, post back to Ada.
Ada digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch end users
Ada
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 Michael Brennan
Approve Deny -
Post the digest
Ada
Queued
Collections and dashboards
Ada health, counted not guessed.
Four metrics, 14 days of articles created, split by team, refreshed on schedule.
Ada health
Refreshed 4 minutes ago · every 15 minutes · from the end users collection
End users
1,284 ↓ 12%
Knowledge sources
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
End users created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Knowledge Base 21%
Compliance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Ada to Claude?
First connect Ada in Elaichi, which asks you for your Ada API key and nothing else. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Ada is available in your next conversation.
Does Ada work with ChatGPT and Cursor as well as Claude?
Yes. Once Ada 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 Ada once and every client you use picks it up.
What can an AI agent actually do with my Ada data?
With Ada connected, an agent can look up or update an end user, list and remove knowledge articles, create or change knowledge sources, manage knowledge tags in bulk, list and create channels, start an email conversation, and read audit log events. Ada exposes a large set of actions, so the agent searches for the right one as you ask. Short, concrete asks like "list Ada knowledge sources" work better than long paragraphs.
Does connecting Ada give the AI access to everything in my Ada account?
No. Every call to Ada runs under the API key that the person connected, so the agent can only reach what that key is allowed to see and change in Ada. Elaichi can narrow that further, for example to read-only knowledge work, and it can never grant more than the Ada key itself allows.
Can I stop an agent from deleting or changing things in Ada?
Yes. In Elaichi you can restrict individual Ada actions, such as deleting knowledge articles or updating end users, for a team or for everyone. A restricted action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to an Ada connection when someone leaves?
When you offboard a person in Elaichi, their access to Ada through every AI client ends at once. If they had shared an Ada connection with a team, it keeps working for everyone else. If you want Ada gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Ada in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.