Can I use Matrix as a CLI?

Yes. KosmoKrator exposes a Matrix CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Matrix through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Matrix tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Matrix credentials stored?

Matrix credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Matrix MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

communication

Matrix MCP Integration for Generic MCP Clients

Connect Matrix to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 5 read 2 write Bearer token auth

Submit Matrix feedback View package source

Connect Matrix to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Matrix MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-matrix": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=matrix",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=matrix --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Matrix instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Matrix Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Matrix integration catalog.

MCP tool	Source function	Type	Description
`integration__matrix__matrix_list_rooms`	`matrix.matrix_list_rooms`	Read	List rooms the authenticated user has joined on Matrix. Returns room IDs, names, and aliases.
`integration__matrix__matrix_get_room`	`matrix.matrix_get_room`	Read	Get details of a specific Matrix room, including name, topic, members, and aliases.
`integration__matrix__matrix_create_room`	`matrix.matrix_create_room`	Write	Create a new room on the Matrix homeserver. Returns the newly created room ID.
`integration__matrix__matrix_send_message`	`matrix.matrix_send_message`	Write	Send a text message to a Matrix room. Uses a unique transaction ID to prevent duplicate messages.
`integration__matrix__matrix_list_members`	`matrix.matrix_list_members`	Read	List members of a Matrix room. Returns user IDs, display names, and avatar URLs.
`integration__matrix__matrix_get_profile`	`matrix.matrix_get_profile`	Read	Get a Matrix user's profile information, including display name and avatar URL.
`integration__matrix__matrix_get_current_user`	`matrix.matrix_get_current_user`	Read	Get the currently authenticated Matrix user's information, including user ID and device ID.

Related Matrix Pages

Matrix CLIUse direct JSON commands instead of MCP discovery. Matrix MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.