getAlby/mcp

**NEW:** also checkout Alby CLI for agents that don't support MCP.
Connect a bitcoin lightning wallet to your LLM using Nostr Wallet Connect (NWC).
This MCP server uses the official MCP TypeScript SDK
This MCP server has knowledge of NWC, LNURL and L402 using Alby SDK and Alby Lightning Tools.
Take a look at **Awesome AI Bitcoin** for places where you can use the Alby MCP.
Quick Start
> In case you get stuck, see troubleshooting section below.
Use the Alby-Hosted MCP Server
If your agent supports remote MCP servers - SSE (e.g. N8N) or HTTP Streamable transports, you can connect to Alby's MCP server.
- SSE: https://mcp.getalby.com/sse
- HTTP Streamable: https://mcp.getalby.com/mcp
Authentication
Both require providing an NWC connection secret as authentication, either as Bearer authentication (preferred) or via the nwc query parameter.
Bearer Auth
Example: Authorization: Bearer nostr+walletconnect://...
> If your agent UI supports bearer auth, just paste the connection secret into the bearer auth field.
Query Parameter
If your agent doesn't support bearer auth, you can pass the NWC connection secret as a query parameter.
Example: https://mcp.getalby.com/sse?nwc=ENCODED_CONNECTION_SECRET or https://mcp.getalby.com/mcp?nwc=ENCODED_CONNECTION_SECRET
_To get ENCODED_CONNECTION_SECRET, open browser devtools (right click -> inspect) and enter this in the console, with your own NWC connection secret set:_
In case there is a message asking for confirmation for pasting, follow the instructions, and then enter the above command again.
Once the command has run, copy the output and replace ENCODED_CONNECTION_SECRET. It will look like this: nostr%2Bwalletconnect%3A%2F%2F...
Add to Claude Web or Claude Desktop
Use the remote Alby MCP server
Currently, at least a Claude Pro subscription is required to be able to connect to remote MCP servers.
1. Go to Settings -> Connectors
2. Click on "Add custom connector"
3. Call it alby
4. What is the endpoint URI: https://mcp.getalby.com/mcp?nwc=ENCODED_NWC_URL (see above for instructions)
Client-side
Add this to your claude_desktop_config.json:
Add to Goose Desktop
1. Open Goose Desktop
2. Go To Settings -> Advanced Settings
3. Click on "Add custom Extension"
4. Call it alby, and change the type to HTTP Streamable
5. What is the SSE endpoint URI: https://mcp.getalby.com/mcp
6. Timeout: 30
7. Description: no
8. environment variables: no
Add to Goose CLI
Use the Alby MCP server
1. Type goose configure
2. Add extension -> Remote Extension (HTTP Streamable)
3. Call it alby
4. What is the HTTP Streamable endpoint URI: https://mcp.getalby.com/mcp
5. Timeout: 30
6. Description: no
7. environment variables: no
8. add custom headers: yes
9. header name: Authorization
10. header value: Bearer nostr+walletconnect://... (replace with your connection secret)
Client-side
1. Type goose configure
2. Add extension -> Command Line Extension
3. Call it alby
4. What command should be run: npx -y @getalby/mcp
5. Timeout: 30
6. Description: no
7. environment variables: yes
8. environment variable name: NWC_CONNECTION_STRING
9. environment variable value: nostr+walletconnect://... (your NWC connection secret here)
Add to Cline
> Copy the below and paste it into a cline prompt. It should prompt you to update the connection string.
Add to Claude Code
Use the Alby MCP server
Add to N8N via SSE
You can use the native N8N MCP Client tool connected to an AI agent. Enter your SSE endpoint, set authentication to "Bearer" and paste your NWC connection secret.