MCP server for Rocket.Chat — messages, DMs, search, files, and channels over stdio
If you already use Rocketchat, the rocketchat mcp server is the piece that lets your assistant work with it directly. MCP server for Rocket.Chat — messages, DMs, search, files, and channels over stdio.
∗ 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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
send_message_in_channel — Send a message to a channelsend_direct_message — Send a direct message to a userdelete_message — Delete a message (your own, unless the role has force-delete)get_channel_messages — Read history of a channel/group/DM; supports offset paging and accepts a room ID or namesearch_messages — Keyword search within a room (chat.search)get_unread — List rooms with unread messages and their latest contentsend_file — Upload a file to a channel or @userdownload_attachment — Download a message's attachments to local fileslist_all_rooms — List channels, groups and DMs ∗list_users — List users ∗get_user_info — Get a user's profilecreate_channel — Create a channelConfiguration is passed through the environment: ROCKETCHAT_SERVER_URL, ROCKETCHAT_USER_ID, ROCKETCHAT_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at rocketchat-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Rocketchat's toolset — send_message_in_channel, send_direct_message, delete_message and 9 more — is a fair guide to whether it matches your workflow. It is maintained by millerchou; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| send_message_in_channel | Send a message to a channel |
| send_direct_message | Send a direct message to a user |
| delete_message | Delete a message (your own, unless the role has force-delete) |
| get_channel_messages | Read history of a channel/group/DM; supports offset paging and accepts a room ID or name |
| search_messages | Keyword search within a room (chat.search) |
| get_unread | List rooms with unread messages and their latest content |
| send_file | Upload a file to a channel or @user |
| download_attachment | Download a message's attachments to local files |
| list_all_rooms | List channels, groups and DMs ∗ |
| list_users | List users ∗ |
| get_user_info | Get a user's profile |
| create_channel | Create a channel |
### Client configuration
```json
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ROCKETCHAT_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| ROCKETCHAT_USER_ID | Configuration value read at startup. | Optional |
| ROCKETCHAT_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.