matrix-mcp-server
A standalone MCP tool server that exposes Matrix chat operations as callable tools, enabling messaging, room management, user management, and ID resolution for MCP-compatible clients.
README
@guan-tends/matrix-mcp-server
A standalone MCP (Model Context Protocol) tool server that exposes Matrix chat operations as callable tools. Any MCP-compatible client — AI agents, automation pipelines, developer tools — can use these tools to send messages, manage rooms, resolve names, and interact with the Matrix protocol.
Built on @vector-im/matrix-bot-sdk with full E2EE (end-to-end encryption) support.
Features
- 15 MCP tools — messaging, room management, user management, and intelligent ID resolution
- E2EE support — full Megolm encryption via Rust crypto backend
- Human-friendly name resolution — refer to rooms and users by name, not opaque IDs
- Alias system — teach the server custom shortcuts (e.g.,
"eng"→"!abc123:matrix.org") - Standalone HTTP server — runs independently, connect any MCP client via HTTP
- Zero-cron, zero-LLM — pure tool server. Scheduling and intelligence live in the agent layer
Install
npm install @guan-tends/matrix-mcp-server
Requirements
- Node.js >= 22.0.0
- A Matrix account with an access token
Quick Start
1. Clone and configure
git clone https://github.com/guan-tends/matrix-mcp-server.git
cd matrix-mcp-server
npm install
cp config.example.json5 config.json5
Edit config.json5 with your Matrix credentials:
{
homeserverUrl: "https://matrix.org",
accessToken: "syt_...",
serverName: "matrix.org",
port: 3456,
host: "0.0.0.0",
storePath: "./data/store.json",
cryptoPath: "./data/crypto",
}
2. Run
npm start
The server listens on http://0.0.0.0:3456 and accepts MCP protocol requests over HTTP.
3. Connect your MCP client
Point any MCP-compatible client at the server:
{
"mcpServers": {
"matrix": {
"url": "http://localhost:3456"
}
}
}
Or use with @guan-tends/mcp-ai aggregator for multi-server tool composition.
Configuration
File-based
Edit config.json5 (see config.example.json5 for all options).
Environment variables
All config values can be set via environment variables (highest precedence):
| Variable | Config Key |
|---|---|
MATRIX_MCP_HOMESERVER_URL |
homeserverUrl |
MATRIX_MCP_ACCESS_TOKEN |
accessToken |
MATRIX_MCP_PORT |
port |
MATRIX_MCP_HOST |
host |
MATRIX_MCP_SERVER_NAME |
serverName |
MATRIX_MCP_STORE_PATH |
storePath |
MATRIX_MCP_CRYPTO_PATH |
cryptoPath |
Tools (15)
Messaging
| Tool | Description |
|---|---|
send_message |
Send text to a room (by ID or resolved name) |
send_html_message |
Send HTML-formatted message |
send_reaction |
React to a message with emoji |
send_dm |
Send a direct message (creates encrypted DM if needed) |
Room Management
| Tool | Description |
|---|---|
join_room |
Join a room by ID or alias |
leave_room |
Leave a room |
get_joined_rooms |
List all joined rooms |
get_room_messages |
Get recent messages from a room |
User Management
| Tool | Description |
|---|---|
get_presence |
Get presence status for a user |
invite_user |
Invite a user to a room |
kick_user |
Kick a user from a room |
ID Resolution
| Tool | Description |
|---|---|
set_room_alias |
Teach the server a room alias (e.g., "eng" → "!abc:matrix.org") |
set_user_alias |
Teach the server a user alias (e.g., "alice" → "@alice:matrix.org") |
resolve_room |
Resolve a room name to its Matrix ID with confidence score |
resolve_user |
Resolve a user name to their Matrix ID with confidence score |
Resolution Strategy
The resolver uses a hybrid approach with confidence scoring:
- User aliases (confidence: 1.0) — User-defined mappings
- Exact match (confidence: 0.9) — Exact display name or canonical alias
- Partial match (confidence: 0.7) — Partial name match
- Ambiguity (confidence: 0.5) — Multiple matches, returns candidates
Architecture
┌─────────────────────────┐
│ index.js │
│ (composition root) │
└──────────┬──────────────┘
│ wires
┌────────────────┼────────────────┐
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ MatrixClient │ │ AliasStore │ │ McpDataStore │
│ (bot-sdk) │ │ (aliases) │ │ (DM cache) │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
└────────┬────────┘ │
▼ │
┌──────────────────┐ │
│ MatrixIdResolver │◄────────────────┘
└────────┬─────────┘
│
▼
┌──────────────────┐
│ mcp-server.js │── MCP SDK SimpleServer
│ (15 tools) │── HTTP transport
└──────────────────┘
Composition-Root IoC: index.js wires all dependencies. No module imports another's deps. Each module is independently testable.
Design Decisions
- Composition-Root IoC —
index.jswires all dependencies. Modules don't cross-import. - Minimal AliasStore — Only 4 methods needed for room/user alias management.
- Simple JSON persistence —
persist.jshandles load/save. Two data files. withErrorHandlingwrapper — DRYs the repeated try/catch in every tool.- No cron, no LLM, no bot — Pure MCP tool server. Agents handle their own scheduling.
Testing
# All tests (unit + E2E)
npm test
# Watch mode
npm run test:watch
# With coverage
npm run test:coverage
65 tests across 6 files (5 unit, 1 E2E).
Project Structure
src/
├── index.js — Composition root: config → Matrix client → wire → start
├── mcp-server.js — 15 MCP tools + helpers (withErrorHandling, resolveRoomInput, etc.)
├── matrix-id-resolver.js — Room/user name → Matrix ID resolution
├── alias-store.js — Minimal per-user alias storage
├── mcp-data-store.js — DM room ID cache
└── persist.js — Simple JSON load/save utility
__tests__/
├── unit/ — Unit tests (alias-store, mcp-data-store, resolver, mcp-server, persist)
├── e2e/ — E2E test (full server start → MCP client → tool calls)
├── mocks/ — Mock MatrixClient for testing
└── vitest.config.js
Sponsors
If this project is useful to you, consider supporting its development:
- GitHub Sponsors
- Solana:
Eu8wQcW68TKMs1a6eqzZu8znzU52QLqQugAMG8uCD6y6 - EVM (Ethereum / Base / Arbitrum / Optimism / Polygon):
0x2733ff7c865C56d565a99BE1DC11B81cc76850A5 - XRP Ledger:
r4X6e7McAQj7e8vBCeued1RYu4mCJrREDG
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.