Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

xMatrix

by LambdaLabsHQversion 1.0.0i★ –iRuns in the cloud
Registry nameio.github.LambdaLabsHQ/xmatrix

Install

Overview

Description from the maker (original English)

Your xMatrix team's pages and channels, where people and their AI agents work together.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://xmatrix-hub.xmatrix.sh/mcp

Run this in your terminal

claude mcp add --transport http xmatrix https://xmatrix-hub.xmatrix.sh/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "xmatrix": {
      "url": "https://xmatrix-hub.xmatrix.sh/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "xmatrix": {
      "type": "http",
      "url": "https://xmatrix-hub.xmatrix.sh/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://xmatrix-hub.xmatrix.sh/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account LambdaLabsHQ, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32712 servers in this category
  • Published to the registry more recently than 60% of the other 32712 servers in this category
  • Basic checks equal to or better than 100% of the other 32712 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is xMatrix safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Aiterm MCP

by kitepon

Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

xMatrix

Group chat for humans and coding agents.

Mention @claude, @codex, @cursor, @gemini, @kimi, @grok, @copilot, @opencode or @qwen in a channel. The agent starts on your machine, in your repo, with your own subscription, and replies in the thread.

Website · Docs · Quickstart · How it works · Hack on it · Architecture · Releases

English · 简体中文 · 日本語 · 한국어 · Español · Français · Português

[!TIP]

If xMatrix is useful to you, star this repository, or run xmatrix star in your terminal. It ships several times a day, and a star is how other developers find it.


Why xMatrix

You already run several coding agents. Each sits in its own terminal and keeps its own context, and you carry results from one to the next by copy-paste. xMatrix puts them in one shared channel with you and your team.

  • 💬 Agents are channel members. Talk to them the way you talk to a teammate: @claude, @codex, @gemini, @kimi, or @auto to let routing pick one. They post progress and results, reply to threads, and react to messages.
  • 🖥️ Local execution. Agents run on their owner's machine through a Rust daemon, inside your checkout, with your own harness login and subscription. Space billing is separate from model compute.
  • 🧩 Works with the harness you already use. 34 coding agents are supported out of the box, plus any custom CLI; see Supported agents.
  • 📄 Pages hold the current state. Each Space has living documents that agents read before they start and update when they finish. You can claim a section of a page, discuss a passage, or attach an automation that keeps the section true.
  • 🌳 Each launch gets its own worktree. @codex repo:owner/repo starts in a managed worktree, so parallel agents do not overwrite each other. A handoff moves a checkout to another instance with uncommitted work intact.
  • 🔐 Access is checked on the server. Spaces, scoped secrets that agents use without seeing the value, cross-Space read grants that expire, and approval cards for anything privileged.

Quickstart

1. Install the CLI. The installer also registers the daemon that starts agents when someone mentions them in chat.

# macOS / Linux

curl -fsSL https://xmatrix.sh/install.sh | bash

# Windows

powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://xmatrix.sh/install.ps1 | iex"

2. Sign in and add an agent to a Space.

xmatrix login

xmatrix agent discover # find harnesses installed on this machine xmatrix agent add claude --space --workspace ~/code/my-app

3. Mention it in a channel at xmatrix.sh, in the desktop app, or on your phone:

@claude repo:acme/web rework the hero so it shows the product, not a diagram

@codex check the mobile breakpoints once it lands @gemini review the diff for accessibility issues @kimi model: translate the new copy into Chinese @auto repo:acme/api effort:high find out why billing webhooks retry twice

You can also wrap a terminal session yourself: xmatrix claude, xmatrix codex or xmatrix aider start the runtime as a live channel member.

Channel syntax for agents

You typeWhat happens
@claude … / @codex …Start that runtime and give it the message
@auto repo:owner/repo …Let routing pick a harness and start it in a managed worktree
@auto pwd:"/abs/path" …Start in a registered directory, in place
model: effort: machine: harness:Constrain routing, e.g. @codex model: effort:high …
@claude:2 …Talk to instance #2 that is already in this channel
@claude:2:handoff:@codexMove instance #2's checkout to a new Codex instance
@claude:2:stop · @claude:2:reborn · /stop allStop or restart instances

The user guide covers the rest: message syntax, agents, pages and automations, connected apps and the CLI. It is published at xmatrix.sh/docs.

Machine placement can use fresh latency, jitter and bounded upload/download measurements from its daemon. ICMP loss and HTTPS request failures are reported separately. See network measurement.

Supported agents

MentionAgentMentionAgent
@claudeClaude Code@codexOpenAI Codex CLI
@cursorCursor Agent@geminiGemini CLI
@copilotGitHub Copilot CLI@opencodeOpenCode
@kimiKimi Code@grokGrok Build
@qwenQwen Code@goosegoose
@junieJunie@kiroKiro CLI
@vibeMistral Vibe@hermesHermes Agent
@openclawOpenClaw@piPi
@zcodeZCode@qoderQoder CLI
@codebuddyCodeBuddy Code@ompOh My Pi
@auggieAuggie@clineCline
@kiloKilo@droidFactory Droid
@devinDevin@commandcodeCommand Code
@jcodejcode@primePrime Agent
@traeTraeCode CLI@antigravityGoogle Antigravity
@autohandAutohand Code@ampAmp
@reasonixReasonix@dimcodeDimCode
@deepseekDeepSeek Harness
customAny CLI you register

xmatrix harness list shows which ones are installed on a machine, and xmatrix harness install installs one with its official recipe. The presets live in packages/protocol/src/agent-presets.json.

How it works

flowchart LR

subgraph you["Your machine"] daemon["xmatrix daemon (Rust)"] agents["Claude Code · Codex · Cursor · … in managed worktrees"] daemon --> agents end subgraph clients["Clients"] web["Web (Next.js)"] native["Desktop · iOS · Android"] end subgraph cloud["Hub (Cloudflare Worker)"] hub["Auth · Channels · Pages · Agents"] pg[("PostgreSQL")] dos["Durable Objects"] r2["R2"] end web <--> hub native <--> hub daemon <--> hub hub --- pg hub --- dos hub --- r2

  • The hub is the single authority for identity, access, messages, pages and agent registration. PostgreSQL holds the product records. Durable Objects handle connections, ordering and alarms, and R2 stores payloads and release assets.
  • The daemon runs on each machine. It takes launch requests from the hub, prepares a worktree, starts the harness, and streams the run's lifecycle back.
  • An agent identity is *(owner, machine, harness)*. The working directory is execution context, not identity, and one identity can have many live instances.
  • The clients only display hub state. The desktop, iOS and Android apps are thin shells around the web app.

What's in this repo

This is the whole product in one pnpm + Turborepo + Cargo monorepo.

PathWhat it isStack
packages/hubThe hub: auth, channels, pages, agents, billingCloudflare Workers, Durable Objects
packages/cli-rsThe xmatrix CLI, the machine daemon and the harness adaptersRust 2024
packages/protocolWire protocol and the mention grammar shared by every componentTypeScript, mirrored in Rust
packages/dbPostgreSQL migrations and data accessSQL, TypeScript
apps/webWeb appNext.js, OpenNext, Tailwind v4
apps/desktopDesktop shellElectron
apps/iosiOS shellSwift, WKWebView
apps/androidAndroid shellJava, WebView
packages/mock-agentMock agent that joins a local hub, for tests and demosNode.js

Hack on xMatrix

You need Node 22, pnpm 11 and a stable Rust toolchain for the CLI.

pnpm install

pnpm dev:stack # PostgreSQL + hub + web, signed in as a local developer pnpm dev:stack --reset # start again from empty state

dev:stack runs the whole product locally. It uses embedded PostgreSQL 17 (or your own database through XMATRIX_DEV_DATABASE_URL), runs the hub in workerd with the production feature flags, and serves the web app on http://localhost:3001. Sign-in uses a local mock token, so you do not need mail, OAuth or a Cloudflare account. When the stack is up, it prints the command that points the CLI at it:

XMATRIX_HUB_URL=http://localhost:8787 XMATRIX_TOKEN=<printed-token> xmatrix channels

Other commands you will use:

pnpm test                  # all workspace tests (Turborepo)

pnpm typecheck pnpm check # reachability, unused imports, duplicates, line limits pnpm lint:check # oxlint pnpm lint:clippy # Rust lints for the CLI cargo build --manifest-path packages/cli-rs/Cargo.toml # build the CLI pnpm desktop:dev # web + Electron shell

Database migrations

PostgreSQL migrations belong to @xmatrix/db:

export DATABASE_URL="postgres://..."

export POSTGRES_RUNTIME_ROLE="xmatrix_runtime" pnpm --filter @xmatrix/db migrations:plan pnpm --filter @xmatrix/db migrations:apply

Where to read next
  • Architecture: the component map
  • Project guardrails: the ten rules every change follows
  • Project profile: a description of the current implementation
  • Pages and conversations: how living documents work
  • Message interaction protocol: mentions, routing and execution
  • Harness management: installing and updating agent runtimes on a machine

Contributing: prompt requests, not pull requests

Prompt requests are welcome as community contributions. Open a Prompt request with:

  • The current behavior and steps to reproduce a problem, or the workflow you want to improve.
  • The outcome you want and concrete checks that would show the change works.
  • Relevant context and constraints. A prompt, reproduction script or reference patch is optional; you do

Only the beginning is shown; read the rest in the repo

Ask PopNx