MX Stage

Name: MX Stage
Author: mxstage

by mxstageversion 0.2.9i★ –iRuns on your computer

Registry nameio.github.mxstage/mxstage

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "mxstage": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mxstage/mxstage"
      ]
    }
  }
}

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.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

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

Runs on your computer; the tool list appears in your AI app after you install it.

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account mxstage, 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 applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32403 servers in this category
Published to the registry more recently than 68% of the other 32403 servers in this category
Basic checks equal to or better than 100% of the other 32403 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 MX Stage 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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

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

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB, Node.js on your computer.

What can I use instead?

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

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 yesterday

Install

LickityClick

by lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

Computer or cloudUpdated 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.

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

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

MX Stage

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

LickityClick

README from the maker

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