MCP server · Email, calendar and chat

Rocket.Chat MCP server

Rocket.Chat in any MCP client, through Memtro: Rocket.Chat does not publish this server. Memtro's Rocket.Chat connector reads Rocket.Chat 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

A Rocket.Chat workspace: public channels, the rooms the connected user is in, recent messages and threads in channels and private groups, message search, people and their profiles. Can post, edit, delete, react to and pin messages, save a draft, open direct messages, create channels, private groups and discussions, invite and remove members, set a channel's topic and announcement, archive and unarchive channels, and activate or deactivate users.

Reads

  • rocketchat_list_channelsPublic channels in the workspace: id, name, topic, description, members, message count, when the last message was posted…
  • rocketchat_list_my_roomsRooms the connected user belongs to (channels, private groups, direct messages, livechat): room id, name, type, unread count and when last read.
  • rocketchat_read_messagesRecent messages in one channel or private group, newest first: author, time, text (cut short), thread id and reply count.
  • rocketchat_search_messagesSearch one room's messages for words.
  • rocketchat_get_threadReplies in a thread, given the id of the thread's first message (thread_id on a message).
  • rocketchat_get_userOne person's profile by username or user id: name, username, status (online, away…), whether active, roles and time zone offset.
  • rocketchat_list_usersPeople in the workspace, optionally filtered by part of a username: id (for the member tools), username, name, status, whether active, type (user…

Acts, when you ask

These change something in Rocket.Chat. 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.

  • rocketchat_post_messagePost a message as the connected user to a channel or private group (by room id or #name), to one person (@username), or to several of these at once…
  • rocketchat_update_messageReplace the text of a message the connected user may edit (usually their own).
  • rocketchat_delete_messageDelete a message.
  • rocketchat_save_draftSave text as the connected user's unsent draft in a room (or in a thread, with thread_id).
  • rocketchat_react_to_messageAdd an emoji reaction to a message as the connected user (or remove it with remove true).
  • rocketchat_pin_messagePin a message in its room: it appears in the room's pinned list, and Rocket.Chat posts a notice that it was pinned, which everyone in the room sees.
  • rocketchat_unpin_messageUnpin a pinned message; it stays in the room.
  • rocketchat_create_channelCreate a public channel, with the connected user in it and optionally named members, who are added and notified.
  • rocketchat_create_private_groupCreate a private group (a private channel), with the connected user in it and optionally named members, who are added and notified.
  • rocketchat_create_direct_messageOpen (or find) a direct-message room between the connected user and one or more people, and return its room id for rocketchat_post_message.
  • rocketchat_invite_to_channelAdd people to a public channel.
  • rocketchat_invite_to_groupAdd people to a private group.
  • rocketchat_remove_user_from_channelRemove one person (by user id, from rocketchat_list_users) from a public channel.
  • rocketchat_archive_channelArchive a public channel: it becomes read-only for everyone and leaves the active lists; nothing is deleted.
  • rocketchat_unarchive_channelUnarchive a public channel so members can post in it again.
  • rocketchat_set_channel_topicReplace a public channel's topic (shown in its header to everyone); Rocket.Chat posts a notice of the change.
  • rocketchat_set_channel_announcementReplace a public channel's announcement, the banner every member sees at the top of the channel; Rocket.Chat posts a notice of the change.
  • rocketchat_create_discussionStart a discussion (a sub-room) in a room the connected user belongs to, optionally from a message, with named people added…
  • rocketchat_set_user_activeActivate or deactivate a user account (by user id, from rocketchat_list_users).

Connect it

First connect Rocket.Chat on Dashboard → Connections, then add Memtro to your client once. The Rocket.Chat 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 Rocket.Chat 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 was decided in #ops yesterday?
  • › Find the message where Dan mentioned the Northwind contract
  • › What did people reply in the thread about the outage?
  • › Post in #support that the fix is live
  • › Save a draft in #customers about the outage, for me to send

Questions

Is this an official Rocket.Chat MCP server?
No. It is Memtro's MCP server with Memtro's Rocket.Chat connector behind it: the connector reads Rocket.Chat through its API with the credentials you connect on Dashboard → Connections, and Rocket.Chat 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 Rocket.Chat?
Only when you ask, and only what it has been granted: post a message to one or several Rocket.Chat channels, groups or people (members are notified); edit a Rocket.Chat message (replaces its text); delete a Rocket.Chat message (cannot be undone); save the connected user's draft in a Rocket.Chat room (replaces any draft already there; nothing is sent); react to a Rocket.Chat message with an emoji, or remove the reaction; pin a Rocket.Chat message in its room (everyone in the room sees it); unpin a Rocket.Chat message; create a public Rocket.Chat channel (named members are added and notified); create a private Rocket.Chat group (named members are added and notified); open a Rocket.Chat direct message with one or more people (nothing is sent); add people to a Rocket.Chat channel (they are notified and can read its history); add people to a private Rocket.Chat group (they are notified and can read its history); remove a person from a Rocket.Chat channel; archive a Rocket.Chat channel (read-only for everyone); unarchive a Rocket.Chat channel; set a Rocket.Chat channel's topic; set a Rocket.Chat channel's announcement (shown to everyone in the channel); start a Rocket.Chat discussion in a room (members can see it); activate or deactivate a Rocket.Chat user (deactivating signs them out everywhere). 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.

Other MCP servers · Email, calendar and chat

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time