rocketchat-mcp
This server lets MCP clients interact with a Rocket.Chat workspace over stdio, covering messaging, file transfer, and room/user management.
Send messages to channels (
send_message_in_channel)Send direct messages to users (
send_direct_message)Delete messages (
delete_message)Read channel/group/DM history with paging (
get_channel_messages)Search messages within a room (
search_messages)Get rooms with unread messages and latest content (
get_unread)Upload files to channels or users (
send_file)Download message attachments, including quoted attachments (
download_attachment)List all channels, groups, and DMs (requires admin/view permission) (
list_all_rooms)List users (requires admin/view permission) (
list_users)Get user profile info (
get_user_info)Create channels (
create_channel)
Provides tools to interact with a Rocket.Chat workspace, including sending and reading messages, direct messages, file uploads/downloads, channel management, and user search.
rocketchat-mcp
An MCP server for Rocket.Chat. It lets MCP clients (Claude Desktop, Cursor, Claude Code, etc.) send and read messages, send DMs, search history, upload/download files, and manage channels on a Rocket.Chat workspace over stdio.
Actively maintained fork of elieworkspace/rocketchat-mcp, adding Personal Access Token auth, more tools, and reliability/security improvements. See NOTICE for attribution.
Tools
Tool | Description |
| Send a message to a channel |
| Send a direct message to a user |
| Delete a message (your own, unless the role has force-delete) |
| Read history of a channel/group/DM; supports |
| Keyword search within a room ( |
| List rooms with unread messages and their latest content |
| Upload a file to a channel or |
| Download a message's attachments to local files |
| List channels, groups and DMs ∗ |
| List users ∗ |
| Get a user's profile |
| Create a channel |
Quoted messages and attachments
Message listings include quoted text and uploaded files inside quotes. A quote is a snapshot shared in the containing message; the original room may no longer be accessible. Use the containing message ID when downloading a quoted attachment. You do not need to read the original room first.
download_attachment(message_id, attachment_id) downloads the selected file ID shown
in the listing. Omitting attachment_id retains the existing behavior of downloading
all supported attachments, now including quoted files. The server still enforces file
access permissions. File references must originate from this Rocket.Chat server's
upload path; redirects to file storage do not receive Rocket.Chat authentication headers.
Downloads use unique temporary filenames and do not overwrite prior downloads.
HTTP errors include the server's error type and message when available, so a missing message, an access failure, and a network failure are not reduced to the same diagnosis. Configured authentication secrets are excluded from these error summaries.
∗ list_all_rooms and list_users call workspace-wide endpoints
(channels.list / users.list) that require admin or the corresponding
view-* permission. Every other tool works for a normal chat user.
Related MCP server: Rocket.Chat MCP Server
Authentication
A normal chat user is enough for the core tools. A Personal Access Token is recommended — it keeps the token out of process arguments:
Variable | Description |
| Workspace URL, e.g. |
| Your Rocket.Chat user ID |
| Personal Access Token |
| (optional) orphan-watchdog interval in seconds, default |
Username/password is also supported via --username / --password.
Use --no-verify-ssl for self-signed certificates.
Usage
Run with uvx
uvx rocketchat-mcp --server-url https://chat.example.comTo run the latest unreleased code straight from GitHub instead:
uvx --from git+https://github.com/millerchou/rocketchat-mcp rocketchat-mcp --server-url https://chat.example.comClient configuration
{
"mcpServers": {
"rocketchat": {
"command": "uvx",
"args": ["rocketchat-mcp"],
"env": {
"ROCKETCHAT_SERVER_URL": "https://chat.example.com",
"ROCKETCHAT_USER_ID": "your_user_id",
"ROCKETCHAT_AUTH_TOKEN": "your_personal_access_token"
}
}
}
}Local development
git clone https://github.com/millerchou/rocketchat-mcp
cd rocketchat-mcp
uv run rocketchat.py --server-url https://chat.example.com \
--auth-token "$ROCKETCHAT_AUTH_TOKEN" --user-id "$ROCKETCHAT_USER_ID"Reliability
Run the offline attachment and API error tests with:
uv run python -m unittest discover -s tests -vThe tests use synthetic messages and an HTTP mock transport; no chat account is needed.
Persistent HTTP connection pool, room-endpoint caching, log rotation (1 MB), and an orphan watchdog that self-exits when the MCP client process dies.
License
Modifications in this fork are released under the MIT License. This is a fork of upstream code originally published without a license; see NOTICE for details.
Available Tools
12 toolscreate_channelC
Create a new channel.
Args:
name: Name of the channel to create
Inputs: name (required). Returns: result
delete_messageB
Delete a message.
Args:
room_id: ID of the room containing the message
msg_id: ID of the message to delete
Inputs: room_id (required), msg_id (required). Returns: result
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)
Inputs: message_id (required). Returns: result
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)
Inputs: room_id (required), count, offset. Returns: result
get_unreadA
Get all rooms with unread messages and their latest unread content.
Inputs: no named parameters. Returns: result
get_user_infoB
Get information about a specific user.
Args:
username: Username to get information about
Inputs: username (required). Returns: result
list_all_roomsA
List all rooms (channels, groups and DMs) available to the user.
Inputs: no named parameters. Returns: result
list_usersA
List all users available to the user.
Inputs: no named parameters. Returns: result
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)
Inputs: room_id (required), query (required), count. Returns: result
send_direct_messageB
Send a direct message to a user.
Args:
username: Username of the recipient
text: Message text to send
Inputs: username (required), text (required). Returns: result
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
Inputs: channel (required), file_path (required), message. Returns: result
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
Inputs: channel (required), text (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
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).
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.
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.
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.
Maintenance
Related MCP Connectors
MCP server for Sendbird — chat users, channels, members, and messages from your AI client.
Your own WhatsApp as an MCP server: read, search and send from any MCP client.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
The official Planning Center MCP server for interacting with your ministry's data.
Related MCP Servers
- AlicenseBqualityDmaintenanceThe most powerful MCP server for Slack Workspaces. This integration supports both Stdio and SSE transports, proxy settings and does not require any permissions or bots being created or approved by Workspace admins 😏.21,901MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Rocket.Chat instances through MCP protocol. Allows users to manage chat operations and integrate with Rocket.Chat servers using natural language commands.6-
- AlicenseNot gradedqualityCmaintenanceRocket.Chat bridge with a local SQLite/FTS5 cache — CLI for humans, MCP server for LLM agents.9 npm3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Rocket.Chat, enabling AI agents to interact with Rocket.Chat workspaces via tools like listing users, sending messages, and managing channels.2-