The connection secret is the whole authorisation story: whatever spending limits your NWC connection carries are the limits the model has, which is the part worth setting before you paste it anywhere.
An MCP server that connects a lightning wallet to an LLM through Nostr Wallet Connect. Run it locally over stdio with `npx -y @getalby/mcp`, or point a client at Alby's hosted server — `https://mcp.getalby.com/mcp` for Streamable HTTP, `https://mcp.getalby.com/sse` for SSE.
- A wallet reachable from any MCP client, with the NWC connection secret acting as the credential
- Built-in knowledge of NWC, LNURL and L402, through the Alby SDK and Alby Lightning Tools
- Hosted transport with bearer auth — paste `Authorization: Bearer nostr+walletconnect://...`, or pass the secret URL-encoded as an `nwc` query parameter for clients with no bearer field
- A local mode taking `NWC_CONNECTION_STRING` from the environment, and `MODE=HTTP` to expose Streamable HTTP at `http://localhost:3000/mcp`
- Documented setup paths for Claude Desktop, Claude Code, Goose, Cline, Windsurf and n8n
- `yarn inspect` to exercise the tools without an LLM in the loop
A lightning wallet that supports NWC and its connection secret. Building from source needs Node.js 20+ and Yarn. Connecting Claude to the remote server currently requires at least a Claude Pro subscription. The author notes that a capable model matters here — a weak one will not drive it.
One command plus a key — npx -y @getalby/mcp, then supply credentials