MX Stage

Name: MX Stage
Author: mxstage

作者：mxstage版本 0.2.9i★ –i在你的电脑上运行

注册名称io.github.mxstage/mxstage

安装

概览

作者提供的说明（英文原文）

Local AI workbench for IBM Maximo data: every change is staged, diffed and approved before commit.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

claude mcp add mxstage -- npx -y @mxstage/mxstage

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "mxstage": {
      "command": "npx",
      "args": [
        "-y",
        "@mxstage/mxstage"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "mxstage": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mxstage/mxstage"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 mxstage 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32371 个服务器的 0%
发布到注册中心的时间比此分类中其他 32371 个服务器的 69% 更新
基础检查结果等于或优于此分类中其他 32371 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MX Stage 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.9）于17天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB, Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, DepTime

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

DepTime

作者：cschmertz

What changed in a Python library, in which release, and what replaces it. Answered locally.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

MX Stage

English | 日本語

MX Stage is a local-only AI workbench for correcting IBM Maximo data with your own AI assistant (Claude Desktop, ChatGPT, Antigravity, IBM Bob): every change is staged, diffed and approved by a human before it is written to Maximo.

Website: https://mxstage.tsunagi.app · Contact: mxstage@tsunagi.app

Your AI works on a staging sheet, not on Maximo. The AI assistant loads Maximo data into a sheet in the *work screen* (a browser tab), analyses it and proposes changes with reasons. You see every changed cell. The sheets live only in the work screen tab and the bridge's memory; loaded tables are never written to disk.
Only a person can commit. The AI's tools cannot write to Maximo. Changes are written only when you press Commit to Maximo in the work screen. MX Stage writes one record first and lets you check it before it sends the rest. Records that someone else changed after you loaded them are skipped and listed; it stops on an error or a result it cannot confirm. Any batch of changes can be undone before you commit. You choose in the commit panel how many records one commit sends (all of them, or a number; 200 by default).
Keep a record of what was approved. The commit panel saves a diff report (Excel): one row per changed cell with the old value, the new value, who changed it (the AI assistant or a person) and why. After a commit, it also holds the write log of that commit.
Nothing leaves your PC except calls to your Maximo and your AI assistant. There is no MX Stage cloud and no telemetry. There are two optional exceptions: if you turn on Settings → Updates → Update automatically (off by default), the bridge asks GitHub once a day for the latest version number; and if you choose Settings → Demo → Download data and connect, it downloads fictional sample data once from mxstage-demo.pages.dev (nothing is sent). Installs made with the setup script then update themselves while no work is open (the new version from GitHub, its packages from the npm registry); the Claude Desktop extension downloads the new file from GitHub and checks it for you to install. A small local process (the *bridge*) serves the work screen, talks MCP to your AI assistant and relays requests to Maximo, so Maximo needs no CORS settings. Your Maximo API key is saved on this PC by the bridge, encrypted with Windows data protection (DPAPI), and is not sent to the browser (on macOS, untested, the Keychain protects it; on Linux, a file only your user can read). Every window of the work screen — the installed app, a browser tab, or the browser inside your AI assistant — connects automatically, even after a restart, and you can switch between saved Maximo environments in Settings. (You can also connect without saving; the key then stays only in the tab's memory.)
Teach it your procedures. Save a procedure worked out in a conversation as a *Skill*; the AI follows it next time.
Keep the customer's way of writing. *Customer dictionaries* hold how a customer writes names, the words that mean a failure code, and how values such as maker or department names are written. The AI adds entries and the work screen applies them as rules (matching, codes from text, value replacement), so the next month's files need less reading. You check and save them in the work screen. Each connection keeps its dictionaries and Skills in its own folder (Documents\MX Stage\ by default); choose a shared folder (OneDrive, SharePoint, a network folder…) in Settings → Skills & dictionaries, and saved entries reach every member through your own file sync. MX Stage itself sends them nowhere.

Why not call the Maximo REST API from the AI directly?

Several Maximo MCP servers let the AI call the REST API. That is fine for reading, but risky for bulk changes: you cannot see what the AI is about to write, and a wrong guess goes straight into production. MX Stage puts a staging sheet, a diff, an undo and a human approval in between.

Supported AI assistants

Assistant	Status
Claude Desktop (chat and Code tab)	Supported
ChatGPT desktop — Codex or Work mode (Chat mode cannot use local MCP servers)	Supported
Antigravity (2.0, IDE)	Supported (registered by the installer)
IBM Bob	Supported (registered by the installer)
Claude Code, Codex CLI and IDE extension	Work, not officially supported

Requirements

Windows (macOS and Linux are untested)
For the installer: Node.js 22.6 or later and Git (the installer offers to install them). The Claude Desktop extension needs neither; the npm package (npx @mxstage/mxstage) needs Node.js 20 or later.
Chrome or Edge
IBM Maximo or Maximo Application Suite (Manage) with the JSON API at /maximo/api and an API key

Install

Claude Desktop (simplest)

Download mxstage- .mcpb from the latest release.
In Claude Desktop, open Settings → Extensions, then Advanced settings → Install Extension… and choose the file (or double-click the file, or drag it onto the Extensions page). Choose Install.
Open http://127.0.0.1:8788/app in Chrome or Edge and enter your Maximo URL and API key in Settings. Never paste the API key into the chat.
In a new chat, ask "show the MX Stage status".

The extension needs no Node.js or Git: Claude Desktop runs it. To use MX Stage from other assistants as well (ChatGPT desktop, IBM Bob, Claude Code in the terminal, Antigravity), use the installer below; it detects the extension and does not register MX Stage twice.

Try without Maximo

No Maximo at hand? MX Stage includes a demo: a fictional Maximo with three waste incineration plants (assets, locations, about 52,000 work orders, inventory and the data quality problems migrations leave behind), in Japanese or English, running inside the bridge on your PC.

Install MX Stage (above), then open http://127.0.0.1:8788/settings#demo.
Choose Download data and connect. MX Stage downloads about 10 MB of fictional data (no programs) once from mxstage-demo.pages.dev and checks it against a SHA-256 built into this version.
Ask your AI assistant, for example "Check the data quality of the operating assets at North Clean Center and list the problems with counts."

Commits change only the copy on your PC (Reset to the initial state puts it back), and no license is needed. The demo takes about 0.5 GB of memory while in use. Five sample Excel files to merge with Maximo (purchase orders without work order numbers, a legacy equipment register, daily work reports printed as A4 forms (a repair log table in the English data), an equipment register ahead of Maximo, a star chart) are in the same tab. See docs/demo.en.md.

Claude plugin (Skills)

The mxstage plugin in plugin/ adds two Skills to Claude (planning a safe bulk correction of Maximo data; explaining, installing and troubleshooting MX Stage) and, in Claude Code and Cowork, starts the MX Stage server with npx @mxstage/mxstage (Node.js 20 or later). Chat does not start local servers, so use the extension there. In Claude Code: /plugin marketplace add mxstage/mxstage, then /plugin install mxstage@mxstage.

Other assistants (installer)

Ask Claude Code (or the Code tab of Claude Desktop) to install it: give it this repository's URL and say "install this". It follows Installation steps for Claude Code below and asks before running each command.

To install by hand, clone this repository to %USERPROFILE%\mxstage and run node scripts/setup-local.mjs in it.

One install registers MX Stage with every supported assistant found on this PC. Then restart the assistant you use, open mxstage on the desktop (or http://127.0.0.1:8788/app), and enter your Maximo URL and API key in Settings. Never paste the API key into the chat.

In Settings, also choose for each Maximo whether it is production or test. Committing to production needs a license (see License); everything else is free.

MCP clients that start servers with npm can also run the server alone with npx -y @mxstage/mxstage (Node.js 20 or later; the Skills and shortcuts come only with the installer).

To update, say "update MX Stage"; to remove it, say "uninstall MX Stage" (see Uninstall).

Where it is registered

~ is %USERPROFILE%. The installer only touches assistants that are installed (Claude Desktop: its settings folder exists; Antigravity: ~\.gemini; Codex: ~\.codex; IBM Bob: ~\.bob), backs up every file before changing it (to ~\.config\mxstage\backup\), and never changes other servers' settings. node scripts/setup-local.mjs --status shows what is registered without changing anything. To leave an assistant out, add --no-claude-desktop, --no-antigravity, --no-codex or --no-bob (--no-skills copies no Skills). --claude-code registers Claude Code even when the extension is enabled.

Assistant	MCP server	Skills	After installing or updating
Claude Code (CLI)	`mcpServers.mxstage` in `~\.claude.json`. Not registered when the MX Stage extension (`.mcpb`) is enabled in Claude Desktop, because the Code tab already gets MX Stage from the extension and would show every tool twice (an entry the installer added earlier is removed). Add `--claude-code` to register anyway for Claude Code in a terminal (remembered for later runs)	`~\.claude\skills\ \SKILL.md`	Restart Claude Code
Claude Desktop (Code tab)	Same as Claude Code, or the extension (`.mcpb`) when it is enabled	Same as Claude Code	Quit Claude Desktop from the system tray and open it again
Claude Desktop (chat)	`mcpServers.mxstage` in `%APPDATA%\Claude\claude_desktop_config.json`. Microsoft Store version: also in `%LOCALAPPDATA%\Packages\Claude_ \LocalCache\Roaming\Claude\claude_desktop_config.json` when that folder exists. Not registered when the MX Stage extension (`.mcpb`) is installed and enabled in Claude Desktop (an entry the installer added earlier is removed)	Not copied (see Skills)	Quit from the system tray (closing the window is not enough) and open again
Antigravity	`mcpServers.mxstage` in `~\.gemini\config\mcp_config.json`	`~\.gemini\config\skills\ \SKILL.md`	Start a new conversation
Codex (ChatGPT desktop, CLI, IDE extension)	`[mcp_servers.mxstage]` in `~\.codex\config.toml`	`~\.agents\skills\ \SKILL.md`	Restart Codex
IBM Bob	`mcpServers.mxstage` in `~\.bob\settings\mcp.json`	`~\.bob\skills\ \SKILL.md`	Restart IBM Bob

The installer copie

只显示了开头部分；其余内容请在仓库中阅读

MX Stage

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

DepTime

作者的 README

MX Stage

Why not call the Maximo REST API from the AI directly?

Supported AI assistants

Requirements

Install

Claude Desktop (simplest)

Try without Maximo

Claude plugin (Skills)

Other assistants (installer)

Where it is registered