Can the assistant create new channels or invite new users to the Rocket.Chat workspace?

No. This tool package is primarily focused on organic text-based communication, message manipulation (sending, modifying, deleting), and environment querying (listing what already exists). The generative capability to create workspace structural entities like 'new channels' or provisioning administrative user accounts is deactivated for baseline security in this module.

How does `chat_post_message` differ from `chat_send_message`?

`chat_send_message` uses a unique alphanumeric `Room ID` (e.g. 'cxyz123') to target an exact space unambiguously. Meanwhile, `chat_post_message` is designed to be human-readable, allowing your assistant to route messages to named destinations like '#general', '#dev-team', or directly to a user like '@johndoe'.

Can the AI edit or delete messages sent by other users?

Only if the authenticated account has the required admin or moderator permissions in the target channel. The AI inherits the same role-based restrictions as the user whose token is configured.

Rocket.Chat MCP Server for LlamaIndex 10 tools — connect in under 2 minutes

Name: Rocket.Chat
Availability: InStock
Author: Vinkius

docs.llamaindex.ai/en/stable/module_guides/tools/mcp

Built by Vinkius GDPR 10 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Rocket.Chat as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Rocket.Chat. "
            "You have 10 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Rocket.Chat?"
    )
    print(response)

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Rocket.Chat MCP Server

Connect your conversational assistant directly to Rocket.Chat, the open-source team communication platform. This integration transforms your AI into an active participant capable of chatting, sending notifications to channels, identifying active users, and auditing chat room data organically within your workspace.

LlamaIndex agents combine Rocket.Chat tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

Communicate Actively — Instruct your assistant to post messages into public channels or private direct messages (chat_post_message, chat_send_message). Need to fix a typo? The AI can seamlessly edit (chat_update_message) or delete previous messages (chat_delete_message).
Explore Channels & Groups — Give your assistant vision over public discussions (list_public_channels) or private channels you belong to (list_private_groups). You can then extract deep information about specific rooms using get_channel_info.
Audit Users in the Network — Scan the entire user directory (list_users) to locate team members and review their roles and connection status directly (get_user_info).

The Rocket.Chat MCP Server exposes 10 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Rocket.Chat to LlamaIndex via MCP

Follow these steps to integrate the Rocket.Chat MCP Server with LlamaIndex.

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 10 tools from Rocket.Chat

Why Use LlamaIndex with the Rocket.Chat MCP Server

LlamaIndex provides unique advantages when paired with Rocket.Chat through the Model Context Protocol.

Data-first architecture: LlamaIndex agents combine Rocket.Chat tool responses with indexed documents for comprehensive, grounded answers

Query pipeline framework lets you chain Rocket.Chat tool calls with transformations, filters, and re-rankers in a typed pipeline

Multi-source reasoning: agents can query Rocket.Chat, a vector store, and a SQL database in a single turn and synthesize results

Observability integrations show exactly what Rocket.Chat tools were called, what data was returned, and how it influenced the final answer

Rocket.Chat + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the Rocket.Chat MCP Server delivers measurable value.

Hybrid search: combine Rocket.Chat real-time data with embedded document indexes for answers that are both current and comprehensive

Data enrichment: query Rocket.Chat to augment indexed data with live information before generating user-facing responses

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Rocket.Chat for fresh data

Analytical workflows: chain Rocket.Chat queries with LlamaIndex's data connectors to build multi-source analytical reports

Rocket.Chat MCP Tools for LlamaIndex (10)

These 10 tools become available when you connect Rocket.Chat to LlamaIndex via MCP:

chat_delete_message

You must provide both room ID and message ID. Deletes a message from a room

chat_post_message

Sends a message to a channel or user by name

chat_send_message

Sends a message to a specific room by ID

chat_update_message

Updates the text of an existing message

get_channel_info

Retrieves details for a specific channel

get_user_info

Retrieves detailed information for a specific user

list_direct_messages

Lists all active direct message rooms

list_private_groups

Lists all private groups (channels) the user is a member of

list_public_channels

Lists all public channels in the workspace

list_users

Lists all users in the workspace directory

Example Prompts for Rocket.Chat in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with Rocket.Chat immediately.

"List all of my active direct messages."

"Send a welcome message to #general thanking the new members."

"Find and get the user info for the ID abCD123."

Troubleshooting Rocket.Chat MCP Server with LlamaIndex

Common issues when connecting Rocket.Chat to LlamaIndex through the Vinkius, and how to resolve them.

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Rocket.Chat + LlamaIndex FAQ

Common questions about integrating Rocket.Chat MCP Server with LlamaIndex.

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Rocket.Chat tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.