albyhub-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALBYHUB_URL | No | Base URL of your Hub. Default http://localhost:8080. | http://localhost:8080 |
| ALBYHUB_TOKEN | Yes | 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. | |
| ALBYHUB_LOG_PATH | No | Server log. | ./albyhub-admin-mcp.log |
| ALBYHUB_READ_ONLY | No | Refuse all non-GET requests via proxy_request. Strongly recommended for first-time setup. | false |
| ALBYHUB_AUDIT_PATH | No | Append-only JSON-line audit log. | ./albyhub-admin-mcp-audit.log |
| ALBYHUB_REQUIRE_CONFIRM | No | Two-step confirm for non-GET requests. | false |
| ALBYHUB_MAX_REQUESTS_PER_MINUTE | No | Rolling 60s rate limit. | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| albyhub_proxy_requestA | Generic HTTP proxy to your Alby Hub admin API. Use this when no typed convenience tool exists for the endpoint you need. Returns the response status, headers, and (JSON-parsed when possible) body. Non-GET methods are gated by ALBYHUB_READ_ONLY and ALBYHUB_REQUIRE_CONFIRM. Pair with the Hub's own docs to discover endpoints; the typed wrappers (get_node_info, list_apps, get_balances) are layered on top of this and good defaults to start with. |
| albyhub_confirm_requestA | Execute a previously-prepared non-GET request, identified by its one-time token. Only meaningful when ALBYHUB_REQUIRE_CONFIRM=true. The token is consumed (single use) and the safety pipeline (read-only, rate limit) re-runs before the HTTP call. |
| albyhub_get_node_infoA | Fetch Alby Hub node info (identity, network, version) from GET /api/info. Convenience wrapper. If your Hub returns 404 here, the endpoint path differs in your version — use albyhub_proxy_request to probe alternatives like /api/node or /info. |
| albyhub_get_balancesA | Fetch hub balances (on-chain + lightning) from GET /api/balances. Distinct from nwc_get_balance — that one is a single sub-wallet's view via NWC; this one is the hub-wide aggregate including on-chain. If your Hub returns 404, probe with albyhub_proxy_request. |
| albyhub_list_appsA | List NWC connections / sub-wallets ('apps') currently provisioned on the Hub. Each entry typically includes name, pubkey, scope, daily budget, and creation timestamp. Hits GET /api/apps. Use this to inventory what's connected to your Hub and what each connection's budget cap is. |
| albyhub_list_channelsA | List Lightning channels — typically peer pubkey, capacity, local/remote balance, public/private flag, online status. Hits GET /api/channels. The hub-wide view (vs. nwc-mcp which has no channel concept). Useful for spotting offline channels, low inbound, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: generic proxy, confirmation step, and specific typed wrappers for node info, balances, apps, and channels. The proxy_request tool is explicitly a fallback for endpoints without a dedicated wrapper, so there is no confusion about when to use it.
All tools share the consistent 'albyhub_' prefix and follow a verb_noun pattern (proxy_request, confirm_request, get_node_info, get_balances, list_apps, list_channels). The naming is uniform and predictable.
With 6 tools, the set is well-scoped for an admin API wrapper. The generic proxy plus a few convenient typed wrappers cover the domain without redundancy or clutter.
The inclusion of a generic proxy_request tool ensures that any endpoint of the Alby Hub admin API can be accessed, so there are no dead ends. The typed wrappers cover common operations, and the proxy fills any gaps, making the surface complete.