Rocket.Chat is automatable through its API

Rocket.Chat · hybrid · collaborationcommunication

Rocket.Chat is automatable today through its REST API. Every authenticated request sends X-Auth-Token and X-User-Id. A personal access token stays valid until it is revoked. POST /api/v1/login with a username and password returns authToken and userId for the same headers. An account with two-factor authentication passes the code in the login body, and some calls also need x-2fa-code. The developer index lists users, rooms, channels, and messaging. The MCP page says its tools are only a subset of that API. The native MCP endpoint is POST /api/v1/mcp on the workspace URL. It ships as alpha in Rocket.Chat 8.8.0, it is off by default, and it stays closed unless the license includes the Rocket.Chat AI add-on, the user has access-mcp, and an admin turns on MCP_Enabled. The default catalog is 11 tools from six REST operations. Turning on MCP_Expose_Extended_API adds 120 tools, 131 in total, and still does not publish the whole API. A GET on the path returns 405. Community Edition is MIT. Starter is a free self-hosted workspace for up to 50 users. Cloud-hosted workspaces are limited to the premium Commercial, Government, and Defense plans, so deployment is hybrid. Incoming and outgoing webhooks are documented, including JavaScript scripts on those integrations. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 8. The MCP server scores 4 because the vendor marks it a preview that is off and add-on gated. The API is the best path.

Best path today: api · Overall automatability: 8/10

Modalities

ModalityStatusDetail
APIyesrestpersonal-access-tokenusername-password
coverage: partial · docs
SDKunknown
official: unknown
MCPyes
verdict: official
Integrationsunknown
CLIunknown
Extensibilityyesjavascript
webhooks: True
Data access
export: json · import: unknown
RPA / UI automationunknownweb-dom
No repeatable UI probe was run. Rocket.Chat is a workspace with a web app and desktop and mobile clients. The documented machine paths are the REST API and the alpha MCP endpoint. This record is Rocket.Chat, not Mattermost or Slack.
Computer useunknown
measured verdicts only — "unknown" means not yet probed by us

Scores

apimcpintegrationsclirpacomputer useoverall
84————8

Evidence

FactTierSourceDate
homepagedeclaredsource2026-10-16
namedeclaredsource2026-10-16
vendordeclaredsource2026-10-16
licensedeclaredsource2026-10-16
deploymentdeclaredsource2026-10-16
deploymentdeclaredsource2026-10-16
platformsdeclaredsource2026-10-16
platformsdeclaredsource2026-10-16
modalities.api.existsdeclaredsource2026-10-16
modalities.api.kinds[0]declaredsource2026-10-16
modalities.api.auth[0]declaredsource2026-10-16
modalities.api.auth[1]declaredsource2026-10-16
modalities.api.coveragedeclaredsource2026-10-16
modalities.api.docsdeclaredsource2026-10-16
modalities.mcp.first_partydeclaredsource2026-10-16
modalities.mcp.verdictdeclaredsource2026-10-16
modalities.extensibility.scripting[0]declaredsource2026-10-16
modalities.extensibility.webhooksdeclaredsource2026-10-16
modalities.data_access.export[0]declaredsource2026-10-16
modalities.agent_docs.llms_txtdeclaredsource2026-10-16
verdict.scores.apideclaredsource2026-10-16
verdict.scores.mcpdeclaredsource2026-10-16
freshness.watch[0].urldeclaredsource2026-10-16
freshness.watch[1].urldeclaredsource2026-10-16
freshness.watch[2].urldeclaredsource2026-10-16
freshness.watch[3].urldeclaredsource2026-10-16
freshness.watch[4].urldeclaredsource2026-10-16

Related tools

Other products in this database that share a category with Rocket.Chat.

Last verified 2026-10-16 · volatility high · JSON record