Groove MCP server
Groove in any MCP client, through Memtro: Groove does not publish this server. Memtro's Groove connector reads Groove through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Groove shared inbox and help desk: conversations by state, assignee, tag, contact or keyword, one conversation with its messages and notes, contacts, agents, channels and tags. Can, when asked, reply to a customer, start a new email conversation, add an internal note, close, reopen, snooze, assign, unassign, retitle, mark as spam, trash or merge conversations, add or remove tags, and create a tag.
Reads
groove_list_conversationsGroove conversations, most recently updated first: number, subject, state, mailbox, contact, assigned agent and team, message count and tags.groove_get_conversationOne Groove conversation by its number, with its messages and internal notes: who wrote each, when, and the text.groove_list_contactsGroove contacts (customers): name, email, role, companies, how many conversations, when last seen.groove_list_agentsThe agents (team members) in the Groove account, with role, state and their ids for filtering conversations by assignee.groove_list_tagsTags used on Groove conversations, with how many conversations carry each and when it was last used.groove_list_channelsThe Groove channels (inboxes: email, chat, …) with their ids, type and state.
Acts, when you ask
These change something in Groove. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
groove_tag_conversationAdds tags to a Groove conversation; tags already on it stay, nothing is removed, and the customer is not told.groove_create_tagCreates a tag in the Groove inbox (it is not applied to anything; use groove_tag_conversation for that).groove_add_noteAdds an internal note to a Groove conversation, seen by agents only and not sent to the customer.groove_reply_to_conversationSends an email reply on a Groove conversation to the address given (and any cc and bcc), as the token's agent.groove_close_conversationCloses a Groove conversation (state CLOSED; a snooze ends).groove_reopen_conversationReopens a Groove conversation (state OPENED), which also ends a snooze.groove_mark_spamMarks a Groove conversation as spam (state SPAM), moving it out of the inbox.groove_trash_conversationMoves a Groove conversation to the trash (state DELETED).groove_assign_conversationAssigns a Groove conversation to an agent (groove_list_agents), a team, or both.groove_unassign_conversationRemoves the assigned agent, the team, or both from a Groove conversation.groove_snooze_conversationSnoozes a Groove conversation until a date and time, or indefinitely when none is given.groove_untag_conversationRemoves tags from a Groove conversation; other tags stay.groove_set_subjectChanges a Groove conversation's subject as agents see it.groove_merge_conversationsMerges one Groove conversation (source) into another (target): the target keeps everything and the source conversation is deleted.groove_start_email_conversationStarts a new email conversation in Groove from a channel (groove_list_channels), sending the first email to the named recipients…
Connect it
First connect Groove on Dashboard → Connections, then add Memtro to your client once. The Groove tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Groove connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What is open in the inbox right now, and who is it assigned to?
- › What has priya@brightwave.co.uk written in about this year?
- › Which conversations were tagged billing this week?
- › Show me conversation 4812 with its notes
- › Reply to conversation 4812 that the refund went out today, then close it
Questions
- Is this an official Groove MCP server?
- No. It is Memtro's MCP server with Memtro's Groove connector behind it: the connector reads Groove through its API with the credentials you connect on Dashboard → Connections, and Groove publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Groove?
- Only when you ask, and only what it has been granted: add an internal note to a conversation; add tags to a conversation; create a tag; reply to a customer on a conversation (sends an email); start a new email conversation (sends an email); close a conversation; reopen a conversation; mark a conversation as spam; move a conversation to the trash; assign a conversation to an agent or team; unassign a conversation; snooze a conversation; remove tags from a conversation; change a conversation's subject; merge two conversations. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.