Skip to main content
Glama
millerchou

rocketchat-mcp

by millerchou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROCKETCHAT_USER_IDYesYour Rocket.Chat user ID
ROCKETCHAT_AUTH_TOKENYesPersonal Access Token
ROCKETCHAT_SERVER_URLYesWorkspace URL, e.g. https://chat.example.com
ROCKETCHAT_WATCHDOG_INTERVALNo(optional) orphan-watchdog interval in seconds, default 6060

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_usersA

List all users available to the user.

send_message_in_channelB

Send a message to a RocketChat channel.

Args:
    channel: Channel name (e.g., 'general') or channel ID
    text: Message text to send
send_direct_messageB

Send a direct message to a user.

Args:
    username: Username of the recipient
    text: Message text to send
delete_messageB

Delete a message.

Args:
    room_id: ID of the room containing the message
    msg_id: ID of the message to delete
get_unreadA

Get all rooms with unread messages and their latest unread content.

send_fileA

Send a file (image, document, etc.) to a channel or user.

Args:
    channel: Channel name, channel ID, or @username for DM
    file_path: Absolute path to the file to upload
    message: Optional text message to send with the file
list_all_roomsA

List all rooms (channels, groups and DMs) available to the user.

get_user_infoB

Get information about a specific user.

Args:
    username: Username to get information about
create_channelC

Create a new channel.

Args:
    name: Name of the channel to create
get_channel_messagesA

Get messages from a channel, group or DM (newest first).

Args:
    room_id: Room ID or room name of the channel/group/DM
    count: Number of messages to retrieve (default: 20, max: 100)
    offset: Skip this many newest messages — use to page back through history
            instead of re-reading with a larger count (e.g. offset=20 to get
            the 20 messages older than the first page)
search_messagesA

Search messages in a room by keyword. Much cheaper than paging through history with get_channel_messages when looking for a specific message.

Args:
    room_id: Room ID or room name of the channel/group/DM to search in
    query: Search keyword(s)
    count: Max results to return (default: 20, max: 100)
download_attachmentB

Download attachments from a message. Returns local file paths that can be viewed with the Read tool.

Args:
    message_id: The message ID (shown as 'id: xxx' in message listings)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct operation: creating channels, sending messages to channels or DMs, sending files, retrieving and searching messages, user info, listing rooms and users, and deleting messages. There is no overlapping functionality; even the two send message tools are clearly differentiated by target (channel vs DM).

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., create_channel, delete_message, send_direct_message). The exception is 'get_unread', which is less descriptive and deviates from the pattern (could be 'get_unread_rooms'). Otherwise, naming is predictable and clear.

Tool Count5/5

With 12 tools, the set is well-scoped for a chat server. It covers essential operations without being overwhelming. The count falls within the ideal range and each tool serves a clear purpose.

Completeness4/5

The tool surface covers core CRUD operations for messages and channels, plus user info and file sharing. Minor gaps exist: no tool for editing or deleting channels, no message editing, and no channel metadata retrieval. These are not critical but would enhance completeness.

Resources