MCP server for node-admin ops on an Alby Hub via its HTTP API: read node info/balances/channels/apps, gated sub-wallet + channel ops, and a generic proxy_request escape hatch. Pairs with nwc-mcp.
claude mcp add albyhub-admin-mcp -- npx -y albyhub-admin-mcp{
"mcpServers": {
"albyhub-admin-mcp": {
"command": "npx",
"args": ["-y", "albyhub-admin-mcp"]
}
}
}Resumen de MCP Servers
# albyhub-admin-mcp
**Node-admin operations on your Alby Hub, exposed to an LLM agent.** MCP server that wraps the Alby Hub HTTP API — read node info, balances, channels, NWC sub-wallets. Where NWC ([`nwc-mcp`](https://npmjs.com/package/nwc-mcp)) ends (it's wallet-scoped), this server picks up: hub-wide on-chain balance, channel state, sub-wallet inventory.
> **v0.1 — defensive design.** Alby Hub's admin API has evolved across versions and isn't publicly versioned in a stable way. So v0.1 ships **one generic proxy tool** that hits any path (the escape hatch) plus typed wrappers around a few well-established endpoints. If a typed wrapper's endpoint-guess fails against your Hub version, the proxy lets you discover the right path without re-shipping. v0.2 hardens the typed wrappers once smoke-tested against real Hubs.
---
## The six tools
| Tool | Method | Path | Purpose |
|---|---|---|---|
| `albyhub_proxy_request` | * | * | Generic HTTP proxy — escape hatch for any endpoint not yet wrapped. |
| `albyhub_confirm_request` | * | * | Two-step confirm dispatcher for proxy_request. |
| `albyhub_get_node_info` | GET | `/api/info` | Node identity, network, version. |
| `albyhub_get_balances` | GET | `/api/balances` | On-chain + Lightning aggregate balances. |
| `albyhub_list_apps` | GET | `/api/apps` | NWC connections (sub-wallets) provisioned on this hub. |
| `albyhub_list_channels` | GET | `/api/channels` | Lightning channels with status + capacities. |
All typed wrappers are safe GETs. Non-GET behavior runs through `albyhub_proxy_request`, which is gated by `ALBYHUB_READ_ONLY` and `ALBYHUB_REQUIRE_CONFIRM`.
---
## Requirements
- Node 20+
- A running Alby Hub instance (desktop app on `http://localhost:8080`, or self-hosted exposed somewhere)
- An Alby Hub API token (Settings → Developer / Apps in the Hub UI)
## Install
```bash
npx -y albyhub-admin-mcp
```
## Configure
```bash
cp .env.example .env
# edit .env: set ALBYHUB_URL (default http://localhost:8080) + ALBYHUB_TOKEN
```
### Required
| Var | Purpose |
|---|---|
| `ALBYHUB_URL` | Base URL of your Hub. Default `http://localhost:8080`. Use HTTPS if exposed remotely. |
| `ALBYHUB_TOKEN` | API access token. **Full-scope tokens can drain the hub's on-chain balance — scope down or use ALBYHUB_READ_ONLY=true if your audience matters.** |
### Optional safety knobs
| Var | Default | Purpose |
|---|---|---|
| `ALBYHUB_READ_ONLY` | `false` | Refuse all non-GET requests via `proxy_request`. Strongly recommended for first-time setup. |
| `ALBYHUB_REQUIRE_CONFIRM` | `false` | Two-step confirm for non-GET requests. |
| `ALBYHUB_MAX_REQUESTS_PER_MINUTE` | `30` | Rolling 60s rate limit. |
| `ALBYHUB_LOG_PATH` | `./albyhub-admin-mcp.log` | Server log. |
| `ALBYHUB_AUDIT_PATH` | `./albyhub-admin-mcp-audit.log` | Append-only JSON-line audit log. |
---
## What if my Hub returns 404 on the typed wrappers?
The endpoint path probably differs in your Hub version. Use `albyhub_proxy_request` to probe — try `/api/node`, `/info`, `/api/v1/info`, etc. Once you find the right path, you can pin it in your usage (and ping the maintainer to fix the typed wrapper in v0.2).
```
agent: albyhub_proxy_request({ method: "GET", path: "/api/v1/info" })
→ { status: 200, body: { ... } } // found it
```
---
## Safety model
The proxy tool's pipeline:
1. **`ALBYHUB_READ_ONLY` gate** — non-GET requests blocked outright.
2. **Rate limit** — rolling 60s window on the `requests` bucket.
3. **`ALBYHUB_REQUIRE_CONFIRM` gate** — non-GET requests return a token; `albyhub_confirm_request` executes.
4. **HTTP request** — Bearer auth, 15s timeout (override via `timeout_ms`).
5. **Audit log** — every attempt (ok / blocked / error) as one structured JSON line.
GET-only convenience wrappers skip steps 1 + 3 (they're safe by construction) but still go through rate limit + audit.
---
## Companion servers
- [`nwc-mcp`](https://npmjs.com/package/nwc-mcp) — wallet ops via NIP-47. Use this for per-sub-wallet spend; use `albyhub-admin-mcp` for hub-wide / node-level operations.
- [`nostr-ops-mcp`](https://npmjs.com/package/nostr-ops-mcp) — NOSTR identity + publishing.
- [`marketplace-mcp`](https://npmjs.com/package/marketplace-mcp) — NIP-15 marketplace storefront.
---
## License
MIT — see [`LICENSE`](./LICENSE).
## Contact / Issues
Built by **LLMOps.Pro**.
- **NOSTR:** [`npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw`](https://njump.me/npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw) — follow, DM, zap.
- **Lightning Address:** `sovereigncitizens@getalby.com` — for support zaps and "this was useful" tips.
- **Bug reports / feature requests:** open a GitHub issue (link forthcoming).
- **Security issues:** please disclose privately via NOSTR DM before opening a public issue.
Lo que la gente pregunta sobre albyhub-admin-mcp
¿Qué es llmops-pro/albyhub-admin-mcp?
+
llmops-pro/albyhub-admin-mcp es mcp servers para el ecosistema de Claude AI. MCP server for node-admin ops on an Alby Hub via its HTTP API: read node info/balances/channels/apps, gated sub-wallet + channel ops, and a generic proxy_request escape hatch. Pairs with nwc-mcp. Tiene 0 estrellas en GitHub y se actualizó por última vez today.
¿Cómo se instala albyhub-admin-mcp?
+
Puedes instalar albyhub-admin-mcp clonando el repositorio (https://github.com/llmops-pro/albyhub-admin-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar llmops-pro/albyhub-admin-mcp?
+
llmops-pro/albyhub-admin-mcp aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.
¿Quién mantiene llmops-pro/albyhub-admin-mcp?
+
llmops-pro/albyhub-admin-mcp es mantenido por llmops-pro. La última actividad registrada en GitHub es de today, con 0 issues abiertos.
¿Hay alternativas a albyhub-admin-mcp?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega albyhub-admin-mcp en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/llmops-pro-albyhub-admin-mcp)<a href="https://claudewave.com/repo/llmops-pro-albyhub-admin-mcp"><img src="https://claudewave.com/api/badge/llmops-pro-albyhub-admin-mcp" alt="Featured on ClaudeWave: llmops-pro/albyhub-admin-mcp" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
The fastest path to AI-powered full stack observability, even for lean teams.
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!
⭐AI-driven public opinion & trend monitor with multi-platform aggregation, RSS, and smart alerts.🎯 告别信息过载,你的 AI 舆情监控助手与热点筛选工具!聚合多平台热点 + RSS 订阅,支持关键词精准筛选。AI 智能筛选新闻 + AI 翻译 + AI 分析简报直推手机,也支持接入 MCP 架构,赋能 AI 自然语言对话分析、情感洞察与趋势预测等。支持 Docker ,数据本地/云端自持。集成微信/飞书/钉钉/Telegram/邮件/ntfy/bark/slack 等渠道智能推送。