Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"groove-hq": {
"url": "https://groove-hq.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"groove-hq": {
"type": "http",
"url": "https://groove-hq.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Groove API token.
Find it in Groove → Settings → API. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Groove API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Groove connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
groove_list_conversations | read | 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_get_conversation | read | Get conversation Get a single conversation by id — subject, state, assignment, contact, channel, counts, and tags. Groove GraphQL: conversation(id: ID!). |
groove_list_contacts | read | 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_get_contact | read | Get contact Get a single contact by id — name, email, role, type, and conversation count. Groove GraphQL: contact(contactId: ID!). |
groove_list_agents | read | List agents List agents (support staff / users) in the account, with role and state. Paginate with first/after. Groove GraphQL: agents. |
groove_list_channels | read | List channels List channels (mailboxes / inboxes — email, chat, etc.) configured in the account. Paginate with first/after. Groove GraphQL: channels. |
groove_list_tags | read | 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_folders | read | List folders List folders (saved views / smart folders that group conversations), with conversation counts. Paginate with first/after. Groove GraphQL: folders. |
groove_list_teams | read | List teams List teams (groups of agents that conversations can be assigned to). Paginate with first/after. Groove GraphQL: teams. |
groove_close_conversation | write | Close conversation CLOSES a conversation (marks it resolved) in the shared inbox. Groove GraphQL: conversationClose. |
groove_open_conversation | write | Open conversation RE-OPENS a closed/snoozed conversation in the shared inbox. Groove GraphQL: conversationOpen. |
groove_snooze_conversation | write | Snooze conversation SNOOZES a conversation until the given time (ISO8601) — it drops out of the inbox until then. Groove GraphQL: conversationSnooze. |
groove_star_conversation | write | Star conversation STARS a conversation (flags it for attention) in the shared inbox. Groove GraphQL: conversationStar. |
groove_assign_conversation | write | 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_tag_conversation | write | Tag conversation ADDS tags (by tag id) to a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationTag. |
groove_untag_conversation | write | Untag conversation REMOVES tags (by tag id) from a conversation. Use groove_list_tags to find tag ids. Groove GraphQL: conversationUntag. |
groove_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
groove_request_feature | Request a missing feature Tell usefulapi that the user needs something the Groove tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
groove_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Groove tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
groove_cancel_subscription | Cancel the Pro subscription Cancel the caller's Groove Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run groove_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Groove server only. Subscribe with groove_upgrade (it returns a Stripe Checkout link). Cancel any time with groove_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running groove_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Groove. The server calls the Groove API with your own Groove access, so it sees only the data that your account can see.
The login page asks for your Groove API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Groove API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Groove API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Groove.
Yes, if you approve it. 7 of the 16 Groove tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Groove server only. Run groove_usage_status to see how many calls you used.
Ask the AI to run groove_upgrade: it returns a Stripe Checkout link. To cancel, run groove_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with groove_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.