Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Read-only IBM MQ diagnostics for AI agents. Cited root cause, never destructive.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV, MQS_SERVER_ENVIRONMENT필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"mq-sentinel": {
"command": "uvx",
"args": [
"mq-sentinel"
],
"env": {
"MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV": "your-value",
"MQS_SERVER_ENVIRONMENT": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add mq-sentinel --env MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV=your-value --env MQS_SERVER_ENVIRONMENT=your-value -- uvx mq-sentinel실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"mq-sentinel": {
"command": "uvx",
"args": [
"mq-sentinel"
],
"env": {
"MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV": "your-value",
"MQS_SERVER_ENVIRONMENT": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"mq-sentinel": {
"type": "stdio",
"command": "uvx",
"args": [
"mq-sentinel"
],
"env": {
"MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV": "your-value",
"MQS_SERVER_ENVIRONMENT": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
MQS_AUTH_DISABLE_AUTH_FOR_LOCAL_DEV envMQS_SERVER_ENVIRONMENT env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 9일 점검
레지스트리 이름이 GitHub 계정 pramodreddyboddu 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.5.0)은 30일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Agilitycms MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to Agility CMS. See https://mcp.agilitycms.com for more details.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Production-grade, read-only IBM MQ diagnostic MCP server that AI agents can safely use — with zero hallucinations.
I built this as a serious side project to solve a real, high-stakes problem in enterprise environments. It is now a strong public portfolio piece demonstrating systems engineering, security, observability, production deployment, and building safe infrastructure for AI agents.
0.5.0 — 8 diagnostic tools across all 10 IBM MQ flavors. Read-only by design. Prompt-injection firewall. OIDC + RBAC. Hash-chained audit. Verified IBM Knowledge Center citations (CI-enforced). Production Helm with HPA + air-gapped packaging.
GitHub: https://github.com/pramodreddyboddu/mq-sentinel Live Demo: https://mq-sentinel.io Get it in front of people: docs/LAUNCH.md
Enterprise IBM MQ teams waste hours diagnosing issues like:
Traditional tools require deep expertise and manual log diving. Handing an LLM raw MQ access is unacceptable for security and compliance teams.
MQ-Sentinel gives Claude, Cursor, Grok, and other agents a safe MCP interface that returns accurate, cited diagnostics without ever hallucinating or executing destructive commands.
IBM MQ teams (banks, telcos, insurance, gov) waste hours on:
2035 NOT_AUTHORIZED channel stormsTraditional tools require deep MQSC knowledge and grepping logs. Giving an LLM direct MQ access is a non-starter for security/compliance teams.
MQ-Sentinel solves this by giving Claude, Cursor, Grok, etc. a safe, read-only MCP interface that returns typed Root Cause + Fix Steps + verified IBM docs — never fabricates, never executes destructive commands.
git clone https://github.com/pramodreddyboddu/mq-sentinel.git
cd mq-sentinel make demo
Watch MQ-Sentinel diagnose a real 2035 NOT_AUTHORIZED, an INDOUBT channel, a 1247-message DLQ, and a Native HA replica disconnect — all against the bundled fixture sandbox. No live IBM MQ required.
Want to record it for sharing?
make demo-recordproduces a browser-playable asciinema cast.
Quick self-check (no MQ needed):
uv run mq-sentinel doctor
uv run mq-sentinel tools # list all diagnostics uv run mq-sentinel info # overview + security highlights
One MCP server — not a per-vendor plugin. Copy-paste configs: [docs/mcp-clients.md](docs/mcp-clients.md).
List it where agents discover servers: official MCP Registry (server.json) + Smithery (smithery.yaml). ChatGPT needs a hosted HTTPS endpoint, not local stdio.
flowchart TB
subgraph Client["MCP Client (Claude / Cursor / Grok)"] P[Prompt] end
subgraph Sentinel["MQ-Sentinel (read-only)"] OIDC[OIDC + RBAC] RL[Rate Limiter] DISP[Tool Dispatcher] ALLOW[MQSC Allowlist] CONN[Connector (pymqi / fixture)] RCS[RCS Engine + KC Registry] SAN[Output Sanitizer] AUDIT[Hash-chained Audit Log] end
subgraph MQ["IBM MQ (read-only service account)"] QM[Queue Managers] end
P -->|MCP stdio / HTTP| OIDC OIDC --> RL --> DISP DISP --> ALLOW ALLOW --> CONN CONN -->|raw output| RCS RCS --> SAN SAN --> AUDIT CONN --> QM QM -.->|DISPLAY only| CONN
Safe by design. No LLM inside the server. Every citation verified in CI.
This is not a toy or weekend demo. It demonstrates real engineering depth:
Built with Grok Build (primary coding partner) while maintaining strict engineering standards.
Full journey and plan: docs/ORG-READINESS-PLAN.md
See also: VISION.md · CONTRIBUTING.md · DEVELOPMENT.md
I built MQ-Sentinel to solve a painful, recurring problem in enterprise IBM MQ environments — and I treated the entire effort as a serious engineering and portfolio project.
I used Grok Build (xAI) as my primary coding partner from architecture through implementation, docs, Helm, compliance artifacts, and polish. Every major decision was deliberate: read-only first, citations that can't go stale, defense-in-depth, production packaging.
Key milestones:
This shows end-to-end ownership: deep domain knowledge, security by design, production operations, and shipping artifacts that real organizations can actually use.
This is my public portfolio project. It demonstrates systems engineering, security, observability, AI infrastructure, and disciplined delivery.
Built with Grok Build while holding high standards throughout.
DISPLAY / DIS / PING CHANNEL only). Destructive verbs are rejected by three layers: tool, connector, MQ-side setmqaut.www.ibm.com; all other URLs are redacted. Every citation in the registry (20+ reason codes, 8 AMQ codes, 18 topic pages) is fetched daily in CI — a dead link fails the build, not the customer.mq-sentinel verify-audit detects any retroactive edit.nonprod-read / prod-read / admin-audit. Cannot query prod QMs from a nonprod token.pip-audit + Trivy in CI, every PR security-gated.See SECURITY.md and docs/threat-model.md.
Org / Enterprise Ready? This project was deliberately built for real organizations (banks, gov, large enterprises). See the complete journey:
See VISION.md for the owner product principles and long-term thinking.
What this project demonstrates:
Built iteratively using Grok Build as the primary coding partner while maintaining high engineering standards.
Standalone · Multi-Instance QM · RDQM · Native HA · Native HA + CRR · Uniform Cluster · Traditional Cluster · z/OS Queue Sharing Group · MQ Appliance · Containerized.
| Tool | Covers | Demo finding |
|---|---|---|
diagnose_failed_channels | Distributed channels | 2035 NOT_AUTHORIZED, 2009/2059 connection errors, INDOUBT, AMQ9202/9208/9503 |
analyze_dlq_and_suggest_reprocessing | DLQ (headers only — never bodies) | Grouped by reason 2035/2080/2030/2051/2053/2079, backout-loop detection |
check_cluster_health | Traditional + uniform cluster | Partial repository, stale CLUSQMGR, suspended members, unhealthy cluster channels |
diagnose_native_ha_issues | K8s/OpenShift Native HA | Replica state, quorum, log replay lag, split-brain, CRR lag |
diagnose_rdqm_issues | On-prem RHEL RDQM | Pacemaker quorum, offline nodes, DRBD connection/disk, split-brain |
diagnose_zos_qsg_issues | z/OS Queue Sharing Group | QSG members, CHIN, page sets, buffer pools, CF structures |
diagnose_multi_instance_issues | Traditional MIQM | Active/standby state, dual-active split, standby permission, failover events |
full_mq_health_check | All of the above (composite) | Executive summary + ranked findings |
9.2 LTS, 9.3, 9.4 (incl. 9.4.4+), z/OS. Version is auto-detected at connect time; KC doc links are keyed to the detected version.
| Scenario | Command | Time |
|---|---|---|
| Claude Code plugin | /plugin marketplace add pramodreddyboddu/mq-sentinel then /plugin install mq-sentinel@mq-sentinel (details) | 1 min |
| Solo / startup laptop (dev) | curl -fsSL https://raw.githubusercontent.com/pramodreddyboddu/mq-sentinel/main/scripts/install.sh \| MQS_DEV_MODE=true MQS_DEV_MODE_ACK_INSECURE=yes bash | 5 min
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요