4,000+ servers built on vurb.ts
Vinkius

Matrix/Element MCP Server for CrewAIGive CrewAI instant access to 19 tools to Change Password, Claim Keys, Create Room, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Matrix/Element through Vinkius, pass the Edge URL in the `mcps` parameter and every Matrix/Element tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Matrix/Element MCP Server for CrewAI is a standout in the Communication Messaging category — giving your AI agent 19 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Matrix/Element Specialist",
    goal="Help users interact with Matrix/Element effectively",
    backstory=(
        "You are an expert at leveraging Matrix/Element tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Matrix/Element "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 19 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Matrix/Element
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 Matrix/Element MCP Server

Connect your Matrix account to any AI agent and take full control of your decentralized communications through natural conversation.

When paired with CrewAI, Matrix/Element becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Matrix/Element tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Room Management — Create, join, knock, or leave rooms using simple commands like create_room and join_room.
  • Messaging & Events — Send messages or custom events to any room with transaction tracking via send_message.
  • State Synchronization — Use sync_client to fetch the latest state from the homeserver and stay updated on all conversations.
  • User Discovery — Search the global user directory using search_user_directory to find and connect with others.
  • Account Control — Manage your profile, change passwords, or handle account registration and deactivation.
  • Encryption & Keys — Handle cryptographic keys (upload_keys, query_keys) for secure, end-to-end encrypted communication.

The Matrix/Element MCP Server exposes 19 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 19 Matrix/Element tools available for CrewAI

When CrewAI connects to Matrix/Element through Vinkius, your AI agent gets direct access to every tool listed below — spanning matrix, element, chat, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

change

Change password on Matrix/Element

Change the account password

claim

Claim keys on Matrix/Element

Claim E2EE keys from the homeserver

create

Create room on Matrix/Element

Create a new Matrix room

deactivate

Deactivate account on Matrix/Element

Deactivate the current Matrix account

download

Download media on Matrix/Element

Download media from the homeserver

get

Get room state on Matrix/Element

Get state events for a room

join

Join room on Matrix/Element

Join a Matrix room by ID or alias

knock

Knock room on Matrix/Element

Knock on a Matrix room to request access

leave

Leave room on Matrix/Element

Leave a Matrix room

login

Login account on Matrix/Element

Log in to a Matrix account

logout

Logout account on Matrix/Element

Log out of the current Matrix account

query

Query keys on Matrix/Element

Query E2EE keys from the homeserver

register

Register account on Matrix/Element

Register a new Matrix account

search

Search user directory on Matrix/Element

Search the user directory

send

Send message on Matrix/Element

Send a message or event to a Matrix room

set

Set room state on Matrix/Element

Set state events for a room

sync

Sync client on Matrix/Element

Synchronize client state with the homeserver

upload

Upload keys on Matrix/Element

Upload E2EE keys to the homeserver

upload

Upload media on Matrix/Element

Upload media to the homeserver

Connect Matrix/Element to CrewAI via MCP

Follow these steps to wire Matrix/Element into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 19 tools from Matrix/Element

Why Use CrewAI with the Matrix/Element MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Matrix/Element through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Matrix/Element + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Matrix/Element MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Matrix/Element for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Matrix/Element, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Matrix/Element tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Matrix/Element against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Matrix/Element in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Matrix/Element immediately.

01

"Sync my Matrix client to see if I have any new notifications."

02

"Send a message to room !abc:matrix.org saying 'The deployment is complete'."

03

"Search the user directory for 'bob'."

Troubleshooting Matrix/Element MCP Server with CrewAI

Common issues when connecting Matrix/Element to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Matrix/Element + CrewAI FAQ

Common questions about integrating Matrix/Element MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →