albyhub-admin-mcp
MCP server for node-admin operations on an Alby Hub Lightning node via its HTTP API: node info, balances, channels, and sub-wallet apps, with write operations gated behind safety knobs. A generic proxy_request tool covers any endpoint the typed wrappers don't expose.
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
| 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
npx -y albyhub-admin-mcp
Configure
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:
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:
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.