Groove MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Groove MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 16 tools. Last commit 2 Nov 2026.

Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

164 ms

Response time

average over 24h

Stars

last commit 2 Nov 2026

What changed 48

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

2 Nov a tool changed version

31 Oct a tool changed version4 times that day

30 Oct a tool changed version2 times that day

29 Oct a tool changed version2 times that day

28 Oct a tool changed version2 times that day

27 Oct a tool changed version

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

23 Oct a tool changed version

22 Oct a tool changed version

and 38 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Groove MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add groove-hq --transport http https://groove-hq.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://groove-hq.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.groove-hq]
url = "https://groove-hq.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "groove-hq": {
      "url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "groove-hq": {
      "type": "http",
      "url": "https://groove-hq.usefulapi.io/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

groove

groove_assign_conversation

ASSIGNS a conversation to an agent and/or team. Pass agent_id, team_id, or both (at least one is required). Groove GraphQL: conversationAssign.

groove_close_conversation

CLOSES a conversation (marks it resolved) in the shared inbox. Groove GraphQL: conversationClose.

groove_get_contact

Get a single contact by id — name, email, role, type, and conversation count. Groove GraphQL: contact(contactId: ID!).

groove_get_conversation

Get a single conversation by id — subject, state, assignment, contact, channel, counts, and tags. Groove GraphQL: conversation(id: ID!).

groove_list_agents

List agents (support staff / users) in the account, with role and state. Paginate with first/after. Groove GraphQL: agents.

groove_list_channels

List channels (mailboxes / inboxes — email, chat, etc.) configured in the account. Paginate with first/after. Groove GraphQL: channels.

groove_list_contacts

List customer contacts (people who wrote in). Optional keyword search over name/email; paginate with first/after. Groove GraphQL: contacts(keywords: String).

groove_list_conversations

List support conversations (tickets) in the shared inbox, with rich filters. Filter by state, channel_id, folder_id, tag_name, assigned, starred, or keywords; paginate with first/after. Groove GraphQL: conversations(filter: ConversationFilter).

groove_list_folders

List folders (saved views / smart folders that group conversations), with conversation counts. Paginate with first/after. Groove GraphQL: folders.

groove_list_tags

List tags defined in the account (id, name, color) — use tag ids with the tag/untag write tools. Paginate with first/after. Groove GraphQL: tags.

groove_list_teams

List teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams.

groove_open_conversation

RE-OPENS a closed/snoozed conversation in the shared inbox. Groove GraphQL: conversationOpen.

groove_snooze_conversation

SNOOZES a conversation until the given time (ISO8601) — it drops out of the inbox until then. Groove GraphQL: conversationSnooze.

groove_star_conversation

STARS a conversation (flags it for attention) in the shared inbox. Groove GraphQL: conversationStar.

groove_tag_conversation

ADDS tags (by tag id) to a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationTag.

groove_untag_conversation

REMOVES tags (by tag id) from a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationUntag.

Endpoints

URL	Transport	State	Latency	Checked
https://groove-hq.usefulapi.io/mcp	streamable-http	answering	70 ms	12 min ago

Alternatives to Groove MCP by usefulapi

same job, measured the same way

Helpwise MCP by usefulapi

by usefulapi

Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.

21 tools answering

Chatwoot MCP by usefulapi

by usefulapi

Read conversations and contacts; add replies or notes, set status and assign in Chatwoot.

18 tools answering

Text Request MCP by usefulapi

by usefulapi

Read inboxes, messages, contacts, groups, tags and scheduled messages.

19 tools answering

SuperPhone MCP by usefulapi

by usefulapi

MCP server for SuperPhone — contacts, conversations, tags and consent-based text messages.

17 tools answering

Userlike MCP by usefulapi

by usefulapi

Read conversations, contacts and operators, and add notes or set operators away in Userlike.

13 tools answering

Re:amaze MCP by usefulapi

by usefulapi

Manage Re:amaze conversations, messages, contacts and help articles.

17 tools answering

Missive MCP by usefulapi

by usefulapi

Read email/chat conversations, messages, contacts and teams; draft, send and update threads.

19 tools answering

Botpress MCP by usefulapi

by usefulapi

Read bots, logs, analytics, conversations, messages, tables and files in Botpress.

19 tools answering

Groove MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Groove MCP by usefulapi do?

It exposes 16 tools, read directly from the server on our last check. Among them: groove_assign_conversation, groove_close_conversation, groove_get_contact, groove_get_conversation, groove_list_agents, groove_list_channels and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Groove MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 164 ms. The bar chart above shows every period we have measured.

How do I connect Groove MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Groove MCP by usefulapi need an API key?

No. Groove MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Groove MCP by usefulapi?

It answers our handshake in 164 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Groove MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at groove-hq.usefulapi.io, which runs on its operator's own terms.