mcpbeat

Groove Hq MCP Server

io.usefulapi/groove-hq
answering

Groove Hq is answering right now. Last checked 1 min ago. It exposes 16 tools. Last commit 1 Aug 2026.

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

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
29.3%
Uptime 24h
27 of 92 checks
16
Tools
read from the server
188 ms
Response time
average over 24h
0
Stars
last commit 1 Aug 2026

Connect this server

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

run in your terminal
claude mcp add groove-hq --transport http https://groove-hq.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "groove-hq": {
      "url": "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
{
  "mcpServers": {
    "groove-hq": {
      "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

URLTransportStateLatencyChecked
https://groove-hq.usefulapi.io/mcp streamable-http answering 306 ms 1 min ago

Groove Hq — questions

Answers built from our own checks of this server.

What can Groove Hq 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 Hq working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 27 of 92 checks got a reply (29.3%), average response time 188 ms. The bar chart above shows every period we have measured.
How do I connect Groove Hq?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Groove Hq need an API key?
No. Groove Hq 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 Hq?
It answers our handshake in 188 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Groove Hq open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.