Helpdesk
Richpanel MCP connector
Connecting Richpanel to Elaichi lets Claude, ChatGPT, Cursor, and any other MCP client read and update Richpanel conversations, customers, orders, and tags through one governed endpoint, with each person signed in as themselves and every action logged.
-
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 Richpanel to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Richpanel once
-
Open Connections, choose Add connection, and pick Richpanel.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Richpanel API key. One person generates a token in Richpanel 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 Richpanel 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 Richpanel 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 Richpanel 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 Richpanel 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 Richpanel through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Catch up on a customer before replying
Ask for everything Richpanel holds on a shopper, their past conversations and recent orders, and get a plain summary before you type a word.
-
Support
Log a conversation after a phone call
Describe what the customer said and have a new Richpanel conversation created against the right customer, so the thread exists before the follow-up email goes out.
-
Support leadership
Tag and route conversations in bulk
Pull the open conversations on a channel, add or remove tags in one pass, and update their status so the queue reflects what is actually happening.
-
Ecommerce operations
Check an order behind a ticket
Look up the order a customer is asking about, confirm items and status in Richpanel, and answer the question without switching windows.
-
Customer experience
Spot patterns across this week's conversations
List recent Richpanel conversations by tag or channel and ask what customers are complaining about most, then create a new tag to track it going forward.
-
Operations
Set up new customers and teams correctly
Create a Richpanel customer record for a shopper who reached out through a new channel, and check which users sit on which team before assigning work.
Try asking
- “Summarize open Richpanel conversations tagged refund this week.”
- “Which Richpanel channels drove the most conversations yesterday?”
- “Show the order and customer behind Richpanel conversation 48213.”
AI tools
Richpanel tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Richpanel, 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 Richpanel gets you
6 screens from the product, each doing one job for your Richpanel account.
The agent
Ask about Richpanel conversations in plain language.
Starter prompts pull live conversations, orders and customers from Richpanel and answer back.
- conversations
- customers
- orders
- tags
Ask Elaichi to work across your apps.
Summarize open Richpanel conversations tagged refund this week.
Which Richpanel channels drove the most conversations yesterday?
Show the order and customer behind Richpanel conversation 48213.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Richpanel here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
19 Richpanel tools ready without custom code.
Conversations, customers, orders, tags, channels, teams and users, each with listed methods.
- List all Richpanel users
- Get single Richpanel user by ID
- List all Richpanel teams
- List all Richpanel tags
Toolboxes
Every team gets its own Richpanel toolbox.
Support, retail ops and CX leadership each see the Richpanel toolbox scoped to them.
- Support
- Retail ops
- CX leadership
- Escalations
Shared connections
Share a Richpanel account, never the credential.
One person connects Richpanel, teams and members work through it without seeing keys.
- Support EMEA
- Retail ops
- Escalations
- CX leadership
Audit log
Every Richpanel call is written down.
When, who, what happened, type and resource for each conversation, order or tag touched.
- 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 drafts your Richpanel digest.
Fetch conversations, group them, draft a digest, get approval, post back to Richpanel.
Richpanel digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conversations
Richpanel
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
Richpanel
Queued
Collections and dashboards
Richpanel health arrives computed, not requested.
Four metrics, 14 days of conversations created, split by team, refreshed on schedule.
Richpanel health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Customers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Conversations created
Last 14 days
By team
Share of activity
Support EMEA 34%
Retail ops 27%
Escalations 21%
CX leadership 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Richpanel to Claude?
Connect Richpanel in Elaichi first: open the Richpanel connector, paste in a Richpanel API key, and save. 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 https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and your Richpanel conversations, customers, and orders are available.
Does Richpanel work with ChatGPT and Cursor as well as Claude?
Yes. Once Richpanel 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 Richpanel once and every client you use picks it up, with the same access rules in each.
What can an AI agent actually do with my Richpanel data?
An agent connected to Richpanel can read and summarize conversations, look up a customer and their past conversations, check orders, and list your users, teams, channels, and tags. It can also create a new conversation or customer, update an existing conversation, add or remove tags on a conversation, and upload a file. It cannot delete anything in Richpanel through this connector.
Does connecting Richpanel give the AI access to every conversation and customer?
No. Access follows the Richpanel API key and the person who signed in to Elaichi, so an agent can only reach the conversations, customers, and orders that connection can already see. Elaichi can narrow that further with per-action restrictions, but it can never widen what Richpanel itself allows.
Can I stop an agent from deleting or changing things in Richpanel?
Yes. This Richpanel connector has no delete actions at all, and you can block any writing action, such as creating conversations, updating them, or adding tags, so the agent can only read. A blocked action is never shown to Claude, ChatGPT, or Cursor in the first place, so no prompt, however worded, can reach it.
What happens to a Richpanel connection when someone leaves?
When a person is offboarded in Elaichi, their access to Richpanel through every client ends at once. A Richpanel connection they shared with a team keeps working for everyone else on it, and their past actions stay in the audit log. If you want the connection gone entirely, disconnecting Richpanel once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put Richpanel in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.