Helpdesk
Groove MCP connector
The Groove connector brings your help desk tickets, customer conversations, mailboxes, agents, groups, and knowledge bases to Claude, ChatGPT, Cursor, and the Elaichi Agent, where each person works inside their own Groove access and every action is logged.
-
How it connects. Connects over OAuth. 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 Groove to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Groove once
-
Open Connections, choose Add connection, and pick Groove.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Groove app, then approve. Groove needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
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 Groove 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 Groove 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 Groove 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 Groove 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 Groove through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Reply to a ticket from your chat window
Pull up a Groove ticket, read the thread so far, and send the reply as a new message on that ticket without switching tabs.
-
Support
See what is waiting in each mailbox
Ask for the ticket counts across your Groove mailboxes and folders at the start of a shift and see where the backlog actually is.
-
Customer success
Catch up on a customer before a call
Pull the customer's Groove record together with their past tickets and messages so you know their history before you dial.
-
Sales
Open a ticket after a handoff
When a prospect raises a problem during a demo, create the Groove ticket with the details and the right mailbox so support picks it up.
-
Support leads
Reshuffle groups when the roster changes
List your Groove agents, then create or update groups as people join, leave, or move between queues.
-
Knowledge
Keep knowledge bases tidy
Review the knowledge bases in Groove, create a new one for a product line, and rename or retire the ones nobody uses.
Try asking
- “Summarize open Groove tickets in the Support mailbox today.”
- “Which Groove agents have the most unresolved tickets this week?”
- “List Groove customers with more than three tickets this month.”
AI tools
Groove tools for your AI agents
73 tools are ready to call through Elaichi's MCP endpoint the moment you connect Groove, 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 Groove gets you
6 screens from the product, each doing one job for your Groove account.
The agent
Ask about Groove tickets in plain language.
The agent reads live Groove tickets, messages and customers to answer.
- tickets
- messages
- customers
- mailboxes
Ask Elaichi to work across your apps.
Summarize open Groove tickets in the Support mailbox today.
Which Groove agents have the most unresolved tickets this week?
List Groove customers with more than three tickets this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Groove.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
73 Groove tools ready to call.
Tickets, messages, customers, mailboxes, folders and agents, with no custom code.
- List all Groove tickets
- Get single Groove ticket by ID
- Create a Groove ticket
- List all Groove messages
Toolboxes
Every team gets its own Groove toolbox.
Support, escalations and reporting each see a curated set of Groove tools.
- Support
- Escalations
- Customer success
- Quality
Shared connections
Share a Groove mailbox, not a credential.
Teammates work through a connection while the Groove login stays with its owner.
- Support EMEA
- Support US
- Escalations
- Billing inbox
Audit log
Every Groove call is on the record.
When, who, what happened, type and resource, in an append only log.
- 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, a Groove digest ships.
Fetch tickets, group them, draft a digest, approve it, post back to Groove.
Groove digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Groove
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
Groove
Queued
Collections and dashboards
Groove ticket health, counted on a schedule.
Four metrics, 14 days of tickets created, and a breakdown by team.
Groove health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Messages
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Escalations 21%
Billing inbox 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Groove to Claude?
Connecting Groove to Claude takes two steps. First, connect Groove in Elaichi: because Groove connects over OAuth, you register an OAuth application inside your Groove account, paste its client ID and secret into Elaichi once, and then sign in to Groove as yourself. Second, in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. That is the same address for every Elaichi customer, and Groove is ready once you have signed in.
Does Groove work with ChatGPT and Cursor as well as Claude?
Yes. Once Groove 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 Groove once and every client you use picks it up.
What can an AI agent actually do with my Groove data?
An AI agent connected to Groove can look up tickets and read the messages on them, create new tickets and send replies, find a customer and update their details, and check ticket counts across your mailboxes and folders. It can also list your agents, create and change groups, and create, rename, or remove knowledge bases. Because Groove has a large set of actions, short concrete asks such as "show me open tickets in the billing mailbox" work better than long paragraphs.
Does connecting Groove give the AI access to every mailbox?
No. Access to Groove follows the person who signed in, so the AI can only see the mailboxes, tickets, and customers that person can already see in Groove. Elaichi can narrow that further by turning off individual actions for a team, but it can never widen it beyond what the person's own Groove permissions allow.
Can I stop an agent from deleting or changing things in Groove?
Yes. In Elaichi, restrictions apply per action, so you can allow reading and replying to Groove tickets while blocking deleting groups or knowledge bases, or updating customer records. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, accidental or otherwise, can reach it.
What happens to a Groove connection when someone leaves?
When you offboard a person in Elaichi, their access to Groove through every client ends at once. If they had shared a Groove connection with a team, that connection keeps working for everyone else. Disconnecting Groove once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Put Groove in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.