SkillAgentSearch skills...

rahdar

Open-source operations console for Apache Artemis, Apache Kafka and RabbitMQ: every cluster in one estate, consumer lag shown as the estimate it is, previews before anything destructive, and an approval gate for people and AI assistants.

Install / Use

claude mcp add sudoitir -- npx -y github:sudoitir/rahdar

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

84/100

Supported Platforms

Claude Code
Claude Desktop

Our assessment of rahdar

rahdar scores 84/100 on our quality scale, 301st of 395 Communication skills we index.

Its MCP Server is 22 KB long, well organised into 12 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated yesterday, so rahdar is actively maintained.
  • Our last check on 2026-11-13 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-13. Automated pattern scan on 2026-11-13. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

rahdar compared with similar skills

All 4 of these similar skills score higher than rahdar; compare them before choosing.

SkillScoreStarsUpdatedFormat
rahdar (this skill)by sudoitir84101d agoMCP Server
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install rahdar?
Run claude mcp add sudoitir -- npx -y github:sudoitir/rahdar. The install tabs above show the steps for each supported agent.
Which AI agents does rahdar work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is rahdar safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is rahdar still maintained?
The repository was last updated yesterday, so rahdar is actively maintained.
<div align="center"> <img src="web/public/favicon.svg" alt="" width="96" height="96">

Rahdar

<sub><em>Rahdar</em> (Persian راهدار, "road-keeper") is <em>rah</em> (route) + <em>dar</em> (keeper): it keeps every route your messages travel open and safe.</sub>

One open-source console for your Apache ActiveMQ® Artemis, Apache Kafka® and RabbitMQ clusters.

Every cluster you run in one estate, lag shown as the estimate it is, a preview before anything destructive, and an approval gate that holds people and assistants alike.

<a href="https://rahdar.dev/"><img src="https://img.shields.io/badge/Play%20the%20story-One%20night%20on%20call%20across%20Artemis%20and%20Kafka-0b7285?style=for-the-badge&labelColor=0b1418&logo=data:image/svg%2Bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNDAgMjQwIiByb2xlPSJpbWciIGFyaWEtbGFiZWw9IlJhaGRhciI+PHBhdGggZmlsbD0iIzBjODU5OSIgZD0iTTAgOTAgQTkwIDkwIDAgMCAxIDkwIDAgSDI0MCBWNjAgSDE1MCBBOTAgOTAgMCAwIDAgNjAgMTUwIFYyNDAgSDAgWiBNMTA1IDI0MCBWMTUwIEE0NSA0NSAwIDAgMSAxNTAgMTA1IEgyNDAgVjE1MCBBOTAgOTAgMCAwIDEgMTUwIDI0MCBIMTA1IFoiLz48L3N2Zz4K" alt="Play the story: one night on call across Artemis and Kafka" height="36"></a><br> <sub>An interactive on-call night · about 2 minutes · runs in your browser</sub>

English · 简体中文 · فارسی

CI Latest release Docker pulls OpenSSF Scorecard Quality Gate Coverage Maintainability Reliability Security Licence

Docs · Quickstart · Kafka · RabbitMQ · Flow · SQL Console · MCP · Discussions

</div>

[!WARNING] Alpha. Under active development and not yet feature-complete. Published images are pre-stable dev builds (sudoit1/rahdar:dev; there is no :latest yet). Expect breaking changes.

<picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/estate-dark.webp"><img src="docs/img/readme/estate-light.webp" alt="The estate with an Apache Artemis cluster and an Apache Kafka cluster and their health, above one table of subscriptions sorted by backlog, where Kafka lag is marked as an estimate."></picture>

<sub>Every cluster in one estate: Artemis and Kafka side by side, the worst backlog first.</sub>

Quickstart

Rahdar and its Postgres, from the published image. Your brokers stay as they are: you register them in the UI, and nothing here starts one.

base=https://raw.githubusercontent.com/sudoitir/rahdar/main/deploy/compose
mkdir -p rahdar/compose rahdar/postgres && cd rahdar/compose   # the compose file mounts ../postgres
curl -sO "$base/compose.prod.yaml"
for f in postgresql.conf 10-pg-stat-statements.sql; do curl -s "${base%/compose}/postgres/$f" -o "../postgres/$f"; done
curl -s "$base/.env.example" | sed \
  -e "s|^SECRET_KEY=.*|SECRET_KEY=$(openssl rand -base64 32)|" \
  -e "s|^DB_PASSWORD=.*|DB_PASSWORD=$(openssl rand -hex 24)|" > .env
docker compose -f compose.prod.yaml --env-file .env up -d
docker compose -f compose.prod.yaml logs rahdar | grep -A4 'Created administrator'

Open http://localhost:8080 and sign in as admin with the password the last line prints. It is shown once: you choose your own at the first sign-in, and set up two-step verification, which the admin role requires.

<details> <summary>From a clone with <code>just</code>, or a bare container against your own Postgres</summary>
git clone https://github.com/sudoitir/rahdar && cd rahdar
just up          # two replicas behind HAProxy, pinned to the latest release (just up-single: one replica)
docker run -p 8080:8080 \
  -e RAHDAR_DB_URL=jdbc:postgresql://db:5432/rahdar \
  -e RAHDAR_DB_USER=rahdar \
  -e RAHDAR_DB_PASSWORD=... \
  -e RAHDAR_SECRET_KEY="$(openssl rand -base64 32)" \
  sudoit1/rahdar:dev
</details>

Rahdar runs on a managed or highly available PostgreSQL 18 too, in a schema of your choosing and as a role that is not a superuser: see Running Rahdar on an external PostgreSQL.

Every variable, what a reverse proxy needs for the SSE stream, and how to recover a lost first login are in the configuration guide.

Hardware requirements

Measured with a load test on a 4 vCPU / 8 GB machine, Postgres on the same host (sizing guide, which also lists what each size carries and what degrades first). Sizes per host:

| | Minimum | Recommended | | --- | --- | --- | | Rahdar node (single instance, or each replica of a replicated deployment) | 2 vCPU, 2 GB | 4 vCPU, 4 GB | | PostgreSQL 18 (single instance, or the shared server of a replicated deployment) | 2 vCPU, 2 GB, SSD | 4 vCPU, 4 GB, SSD |

A replicated deployment runs two or more Rahdar nodes of that size on one Postgres of that size. The minimum is the observed peak (a Rahdar replica 1.3 GiB and about 1.2 cores, Postgres 0.6 GB and one core) with little headroom, derived from the runs on the reference machine rather than measured on a smaller one. It carries a few clusters of up to four nodes with around a thousand queues per node, a few dozen browsers and about a hundred event-stream subscribers; the recommended size keeps interactive reads under a second at 3,000 queues per node and absorbs a burst of sign-ins. CPU is what runs out first, not memory. Postgres needs about 0.6 GB of its memory for the shipped configuration (deploy/postgres/postgresql.conf); how much disk depends on how long you keep history. The server requirements and settings of an existing PostgreSQL are in Running Rahdar on an external PostgreSQL.

Why

It's 02:51 and two things page you at once: a Kafka consumer group is falling behind on payments, and ORDERS.DLQ is backing up somewhere on an Artemis pair. Without Rahdar that is a management console tab per Artemis broker, kafka-consumer-groups.sh and kafka-transactions.sh in a terminal, and your own arithmetic in between.

Rahdar puts every cluster you run in one estate, whatever the broker. Health is judged on one scale, and every backlog is in one table, sorted worst first: Artemis queues and Kafka groups side by side, each under its own name. A number says how sure it is: an Artemis queue's depth is exact, a Kafka group's lag is an estimate with its per-partition breakdown, and a number Rahdar cannot read says so instead of showing zero. Nothing destructive runs before you have seen what it will do, and where the approval gate is on, a second person approves it.

<a href="https://rahdar.dev/"><img src="docs/img/story.webp" width="1600" height="900" alt="The story opens at 02:51 with two alerts: a Kafka consumer group falling behind on payments, and ORDERS.DLQ rising on an Artemis pair. Play it in your browser."></a>

▶ Play the story: find the hanging transaction behind the lag, abort it, reset a group with a held approval, and clear the Artemis dead-letter queue, all in one estate.

What it does

| | | |---|---| | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/subscriptions-dark.webp"><img src="docs/img/readme/subscriptions-light.webp" alt="The subscriptions table on a Kafka cluster with a group's backlog breakdown open: each partition's committed offset, end offset and lag, slowest first, with the sample's age."></picture> | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/kafka-group-dark.webp"><img src="docs/img/readme/kafka-group-light.webp" alt="A Kafka consumer group's page: its type and state, lag per partition topic by topic, and its members."></picture> | | Kafka lag is an estimate, and opens to every partition, slowest first. | A consumer group's lag per partition and its members. | | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/offset-reset-dark.webp"><img src="docs/img/readme/offset-reset-light.webp" alt="The reset-offsets preview: each partition's current and new offset and the records skipped, with a press-and-hold button that names the partition count."></picture> | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/transactions-dark.webp"><img src="docs/img/readme/transactions-light.webp" alt="The transactions page with a hanging transaction flagged, and its abort preview naming the partitions it unblocks and that the producer is fenced."></picture> | | An offset reset is previewed per partition before it is held to confirm. | A hanging transaction, found and aborted with its reach stated first. | | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/register-kafka-dark.webp"><img src="docs/img/readme/register-kafka-light.webp" alt="The Kafka registration page after a passed check: the version and mode, every broker with its advertised address reached, and the controller quorum."></picture> | <picture><source media="(prefers-color-scheme: dark)" srcset="docs/img/readme/artemis-topology-dark.webp"><img src="docs/img/readme/artemis-topology-light.webp" alt="The Artemis topology: live and backup pairs with their replication state, one node stopped."></picture> | | Registration checks every broker on the address it advertises. | Artemis topology, with HA roles polled from every node. |

Rahdar talks to brokers through OpenBroker, an open-source broker SDK with a driver per system. The screens every system shares (the estate, subscriptions and destinations, browsing, purge, the audit trail, the API and MCP) work on each, in that system's own words, and an action a system cannot do stays visible, disabled, with the reason.

| System | Supported | Guide | | --- | --- | --- | | Apache ActiveMQ® Artemis | 2.33.0 and later | Guide | | Apache Kafka® | 2.8 and later, KRaft and ZooKeeper mode | Kafka | | RabbitMQ | 3.13 and later (4.x tested) | RabbitMQ |

Details and what happens outside those ranges: supported broker versions.

Apache Kafka

  • Consumer groups — classic, consumer and share groups with their state, members and lag. Lag is an estimate and is marked as one: open it for every pa

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryCommunication
Updated1d ago
Forks1

Languages

Java

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info