
Albyhub Admin Mcp
io.github.llmops-proPublished by GitHub account llmops-prov0.1.2Updated Oct 27, 2026
Admin an Alby Hub Lightning node from an agent: info, balances, channels; safety-gated writes.
Overview
Administer an Alby Hub Lightning node from an AI assistant: read node info, balances, channels and sub-wallets, plus gated raw API requests.
- What you can do
- Read node identity, network and version, and aggregate on-chain plus Lightning balances
- List Lightning channels with status and capacities, and list NWC sub-wallet connections provisioned on the hub
- Send arbitrary HTTP requests to any Alby Hub API path as an escape hatch for endpoints without a typed wrapper
- Run non-GET requests through a two-step confirm dispatcher when confirmation is enabled
- Apply a read-only gate, a rolling per-minute rate limit and an append-only JSON audit log to proxy traffic
- When to use it
- Useful when you run an Alby Hub node and want an assistant to inspect hub-wide balances, channel state and sub-wallet inventory, or to probe admin API paths that differ between Hub versions. It complements wallet-scoped NWC tooling by covering node-level operations.
- Requirements
- Node.js 20 or newer, run locally via npx. A running Alby Hub instance reachable at a base URL set in ALBYHUB_URL (default and an Alby Hub API token from the Hub UI set in ALBYHUB_TOKEN. Optional knobs include ALBYHUB_READ_ONLY, ALBYHUB_REQUIRE_CONFIRM, ALBYHUB_MAX_REQUESTS_PER_MINUTE and log paths.
Installation
In SourceWeft
- Open Albyhub Admin Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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) 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
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
Configure
Required
Optional safety knobs
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).
Safety model
The proxy tool's pipeline:
ALBYHUB_READ_ONLYgate — non-GET requests blocked outright.- Rate limit — rolling 60s window on the
requestsbucket. ALBYHUB_REQUIRE_CONFIRMgate — non-GET requests return a token;albyhub_confirm_requestexecutes.- HTTP request — Bearer auth, 15s timeout (override via
timeout_ms). - 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— wallet ops via NIP-47. Use this for per-sub-wallet spend; usealbyhub-admin-mcpfor hub-wide / node-level operations.nostr-ops-mcp— NOSTR identity + publishing.marketplace-mcp— NIP-15 marketplace storefront.
License
MIT — see LICENSE.
Contact / Issues
Built by LLMOps.Pro.
- NOSTR:
npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw— follow, DM, zap. - Lightning Address:
[email protected]— 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.
Source: README.md at commit 34ae5d7
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts