# Introducing 🍃MClusterAdmin: A Lightweight GUI Tool for … | Percona Community **URL:** \ **Category:** Community website\ **Created:** [July 27, 2026, 2:38pm UTC](https://forums.percona.com/t/introducing-mclusteradmin-a-lightweight-gui-tool-for-percona-community/41106 "2026-07-27T14:38:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [July 27, 2026, 2:38pm UTC](https://forums.percona.com/t/introducing-mclusteradmin-a-lightweight-gui-tool-for-percona-community/41106/1 "2026-07-27T14:38:44Z")
Over the years working on various MongoDB troubleshooting cases, I’ve been wondering how to handle the longish JSON outputs from the most common diagnostic commands, like `rs.status()`, `sh.status()`, or `db.currentOp()`, not to mention `db.serverStatus()`! They are just painful and slow to read. I even came up with various scripts to present the data in [table format](https://github.com/kellyjonbrazil/jtbl), similar to what we know from MySQL, but I was never satisfied with them. * * * This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/07/27/introducing-mclusteradmin-a-lightweight-gui-tool-for-mongodb-dba/](https://percona.community/blog/2026/07/27/introducing-mclusteradmin-a-lightweight-gui-tool-for-mongodb-dba/) ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [July 27, 2026, 3:25pm UTC](https://forums.percona.com/t/introducing-mclusteradmin-a-lightweight-gui-tool-for-percona-community/41106/2 "2026-07-27T15:25:47Z")
[@przemyslaw.malkowski](https://forums.percona.com/u/przemyslaw.malkowski) This looks like an excellent “plugin” to PMM (if only PMM had such capability).