Skip to content

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.

1

In Elaichi

Connect Groove once

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

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

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

groove
Groove
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
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 Groove 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 Groove 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 Groove 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 Groove 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.

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

See all 73 Groove tools below

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.

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.

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

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
ElaichiTools
Tool Action Description
List all Groove tickets List List tickets in Groove. Returns fields such as number, created_at, updated_at, summary, tags, message_count, and links for each ticket.
Get single Groove ticket by ID Get Get a specific ticket in Groove by id. Returns fields such as number, title, status links, assigned_group, created_at, updated_at, and summary.
Create a Groove ticket Create Create a new ticket in Groove. Requires body, from, and to. Returns ticket number, href, and links to assignee, customer, state, and messages.
List all Groove messages List List all messages for a given ticket_number in Groove. Returns message details including created_at, updated_at, note, body, plain_text_body, href, and links information.
Get single Groove message by ID Get Get details of a specific message in Groove using id. Returns created_at, updated_at, note, body, plain_text_body, and related links for author, recipient, and ticket.

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
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Groove · tickets and messages

Groove starter 18 Mar 4, 2026

Escalations toolbox

Groove · aged and reopened tickets

9 Mar 2, 2026

Customer success toolbox

Groove · customers and ticket history

24 Feb 27, 2026

Quality toolbox

Groove · agents and ticket counts

Groove starter 6 Feb 19, 2026

Operations toolbox

Groove · mailboxes and folders

31 Jan 30, 2026

Analytics toolbox

Groove · ticket volume reporting

12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
GR

Groove (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
GR

Groove (Support US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
GR

Groove (Escalations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
GR

Groove (Billing inbox)

Connected by Daniel Ortega

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

Groove (Customer success)

Connected by Clara Nowak

Personal • Active Not shared
GR

Groove (Onboarding)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

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
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]

Groove Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Groove Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Groove Tickets 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 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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch tickets

    Groove

    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

    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

Live

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%

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 my team share one Groove connection?

Yes. One person connects Groove in Elaichi and shares the connection with a team, and nobody else ever handles the Groove client ID, secret, or password. Each teammate still signs in to Elaichi as themselves, so every ticket reply or customer update in the audit log is recorded under the name of the person who made it.

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.