Groove MCP connector
The Groove connector brings your help desk tickets, customer conversations, mailboxes, agents, groups, and knowledge bases to Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, where each person works inside their own Groove access and every action is logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize open Groove tickets in the Support mailbox today.
Working in Groove with Elaichi
-
List all Groove tickets
-
Get single Groove ticket by ID
-
List all Groove messages
How to connect Groove to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Groove 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.
Groove MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith 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.
Groove 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.
Groove 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.
Groove 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 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.
What teams do with Groove through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Groove is logged.
-
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.”
What connecting Groove gets you
6 screens from Elaichi, each doing one job for your Groove account.
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, Cursor or Microsoft Copilot
The agent
Ask about Groove tickets in plain language.
The agent reads live Groove tickets, messages and customers to answer.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Groove.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
73 Groove tools ready to call.
Tickets, messages, customers, mailboxes, folders and agents, with no custom code.
Toolboxes
Every team gets its own Groove toolbox.
Support, escalations and reporting each see a curated set of Groove tools.
Shared connections
Share a Groove mailbox, not a credential.
Teammates work through a connection while the Groove login stays with its owner.
Audit log
Every Groove call is on the record.
When, who, what happened, type and resource, in an append only log.
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.
Groove digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Groove
Queued
Automations
A schedule fires, a Groove digest ships.
Fetch tickets, group them, draft a digest, approve it, post back to Groove.
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%
Collections and dashboards
Groove ticket health, counted on a schedule.
Four metrics, 14 days of tickets created, and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Groove
All three can connect Groove to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Groove tools | Allow or restrict single Groove 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 Groove 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.
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.
Questions, answered
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, Microsoft Copilot, 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 role, 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 restricting deleting groups or knowledge bases, or updating customer records. 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 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, Microsoft Copilot, and every other client in one step.
Does the Groove MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Groove 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 Groove?
Yes. Both let Claude, ChatGPT or Cursor use Groove. 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 Groove call.
How is Elaichi different from Composio for Groove?
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 Groove: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Groove in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
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