groove-hq

Tools

16 tools: 9 read-only, 0 change data, 7 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,555 tokens of tool definitions and a 398 ms handshake.

• high riskgroove_close_conversationCLOSES a conversation (marks it resolved) in the shared inbox. Groove GraphQL: conversationClose.
• high riskgroove_open_conversationRE-OPENS a closed/snoozed conversation in the shared inbox. Groove GraphQL: conversationOpen.
• high riskgroove_snooze_conversationSNOOZES a conversation until the given time (ISO8601) - it drops out of the inbox until then. Groove GraphQL: conversationSnooze.
• high riskgroove_star_conversationSTARS a conversation (flags it for attention) in the shared inbox. Groove GraphQL: conversationStar.
• high riskgroove_assign_conversationASSIGNS a conversation to an agent and/or team. Pass agent_id, team_id, or both (at least one is required). Groove GraphQL: conversationAssign.
• high riskgroove_tag_conversationADDS tags (by tag id) to a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationTag.
• high riskgroove_untag_conversationREMOVES tags (by tag id) from a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationUntag.
• read-onlygroove_list_conversationsList 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).
• read-onlygroove_get_conversationGet a single conversation by id - subject, state, assignment, contact, channel, counts, and tags. Groove GraphQL: conversation(id: ID!).
• read-onlygroove_list_contactsList customer contacts (people who wrote in). Optional keyword search over name/email; paginate with first/after. Groove GraphQL: contacts(keywords: String).
• read-onlygroove_get_contactGet a single contact by id - name, email, role, type, and conversation count. Groove GraphQL: contact(contactId: ID!).
• read-onlygroove_list_agentsList agents (support staff / users) in the account, with role and state. Paginate with first/after. Groove GraphQL: agents.
• read-onlygroove_list_channelsList channels (mailboxes / inboxes - email, chat, etc.) configured in the account. Paginate with first/after. Groove GraphQL: channels.
• read-onlygroove_list_tagsList tags defined in the account (id, name, color) - use tag ids with the tag/untag write tools. Paginate with first/after. Groove GraphQL: tags.
• read-onlygroove_list_foldersList folders (saved views / smart folders that group conversations), with conversation counts. Paginate with first/after. Groove GraphQL: folders.
• read-onlygroove_list_teamsList teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 398 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-042026-10-03

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in CRM and sales, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/groove-hq.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/groove-hq.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=groove-hq.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/groove-hq.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/groove-hq.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=groove-hq.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.