Matrix
Send and read messages, manage rooms and membership, and manage your profile on any Matrix homeserver.
About
Matrix ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.matrix- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Communication
Overview
Matrix is an open standard for decentralised, federated real-time communication, and this app puts the daily loop of a Matrix account — sending and reading messages, creating and managing rooms, and inviting, kicking, banning and unbanning members — behind a workflow, against whichever homeserver an account happens to live on (matrix.org, an organisation’s own server, or any other public homeserver).
Messaging covers the core of it: post a message (plain text or HTML) into a room, page through a room’s message history, and list the rooms and members a connection can see. Room lifecycle actions create a room with the usual presets (private, trusted-private, public), join it by id or alias, leave it, and invite, kick, ban and unban members with an optional reason. A small profile surface reads any user’s display name and avatar and lets a connection update its own.
Authentication is either a long-lived access token pasted from a client’s own settings, or a username and password exchanged for one at connect time — both end up as the same bearer credential, verified with Matrix’s own account/whoami endpoint. End-to-end encryption is a deliberate scope cut: Matrix’s E2EE model keys messages to a specific device’s Olm/Megolm session state, which has nowhere to live in a stateless, replayable action model, so every action here talks to rooms that are not end-to-end encrypted. Federation administration, device/cross-signing key management, VoIP and the full sync/timeline API are likewise out of scope for a first version.
Build with Matrix
Three routes to the same 14 actions. The Workflow tab is generated from Matrix's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Joined Rooms
list-joined-rooms List the room IDs the connected account is currently a member of.
Set Avatar
set-avatar-url Set the connected account's own avatar from an already-uploaded mxc:// URI.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Matrix's real ids.
{
"manifestVersion": "2",
"name": "matrix-example",
"steps": [
{
"id": "get-messages",
"uses": {
"app": "io.w6w.matrix",
"action": "get-messages",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"roomId": "<roomId>"
}
}
]
}Here are some of the things you can do
-
Get Room Messages
readget-messages -
Create Room
performcreate-room -
Get User Profile
readget-profile -
Invite User
performinvite-user -
Join Room
performjoin-room
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Matrix, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Matrix. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "get-messages",
payload: {
roomId: "<value>",
// direction: "<value>",
// limit: "<value>",
// from: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action get-messages --payload '{"roomId":"<value>"}'Give an AI agent Matrix — without giving it Matrix's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.matrix#get-messages",
"input": {
"roomId": "<roomId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Matrix connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Matrix's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Matrix itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Matrix declares its own checks, so its health is a property of the app rather than something the host guesses at.
Matrix platform status
Homeserver reachable
This connection's own homeserver, via its unauthenticated /_matrix/client/versions endpoint. Sends no credential — an expired access token must not make a healthy homeserver look down.