by docker-hackerxbt68
Alby Bitcoin Payments MCP Server: integrate Lightning wallets with LLMs via Nostr Wallet Connect for LNURL payments, lig
Connects Bitcoin Lightning wallets to AI models via Nostr Wallet Connect, enabling automated lightning payments and LNURL operations. Supports L402 authentication for AI-powered bitcoin transactions.
Alby Bitcoin Payments MCP Server is a community-built MCP server published by docker-hackerxbt68 that provides AI assistants with tools and capabilities via the Model Context Protocol. Alby Bitcoin Payments MCP Server: integrate Lightning wallets with LLMs via Nostr Wallet Connect for LNURL payments, lig It is categorized under finance, developer tools.
You can install Alby Bitcoin Payments MCP Server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
Alby Bitcoin Payments MCP Server is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Alby Bitcoin Payments MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: Alby Bitcoin Payments MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Alby Bitcoin Payments MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Alby Bitcoin Payments MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We evaluated Alby Bitcoin Payments MCP Server against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, Alby Bitcoin Payments MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend Alby Bitcoin Payments MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Alby Bitcoin Payments MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Alby Bitcoin Payments MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Alby Bitcoin Payments MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 42
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.
<a href="https://glama.ai/mcp/servers/@getAlby/mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@getAlby/mcp/badge" /> </a>In case you get stuck, see troubleshooting section below.
If your agent supports remote MCP servers - SSE (e.g. N8N) or HTTP Streamable transports, you can connect to Alby's MCP server.
https://mcp.getalby.com/ssehttps://mcp.getalby.com/mcpBoth require providing an NWC connection secret as authentication, either as Bearer authentication (preferred) or via the nwc query parameter.
Example: Authorization: Bearer nostr+walletconnect://...
If your agent UI supports bearer auth, just paste the connection secret into the bearer auth field.
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:
encodeURIComponent("nostr+walletconnect://...");
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...
Currently, at least a Claude Pro subscription is required to be able to connect to remote MCP servers.
albyhttps://mcp.getalby.com/mcp?nwc=ENCODED_NWC_URL (see above for instructions)Add this to your claude_desktop_config.json:
{
"mcpServers": {
"nwc": {
"command": "npx",
"args": ["-y", "@getalby/mcp"],
"env": {
"NWC_CONNECTION_STRING": "YOUR NWC CONNECTION STRING HERE"
}
}
}
}
alby, and change the type to HTTP Streamablehttps://mcp.getalby.com/mcpgoose configurealbyhttps://mcp.getalby.com/mcpAuthorizationBearer nostr+walletconnect://... (replace with your connection secret)goose configurealbynpx -y @getalby/mcpNWC_CONNECTION_STRINGnostr+walletconnect://... (your NWC connection secret here)Copy the below and paste it into a cline prompt. It should prompt you to update the connection string.
Add the following to my MCP servers list:
"nwc": {
"command": "npx",
"args": ["-y", "@getalby/mcp"],
"env": {
"NWC_CONNECTION_STRING": "nostr+walletconnect://..."
},
"disabled": false,
"autoApprove": []
}
claude mcp add --transport http alby https://mcp.getalby.com/mcp --header "Authorization: Bearer nostr+walletconnect://..."
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.
Tested with OpenRouter + anthropic/claude-3.7-sonnet
See the N8N workflow for a simple example
Currently this MCP server only works via command line (STDIO).
You can install the n8n-nodes-mcp community node and run n8n with tools enabled e.g.
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true npx n8n
Create a blank workflow and add an AI agent node. Configure your LLM model and add a new tool "MCP Client" (which will have a cube next to it showing it's a community node).
Configure the MCP Client by adding a credential with Command Line (STDIO) selected.
command: npx
arguments: -y @getalby/mcp
environments NWC_CONNECTION_STRING=nostr+walletconnect://your_key_here (create the whole line in a text editor and paste it in, since the password field cannot be switched to plaintext)
See the N8N paid chat workflow for a full example
{
"mcpServers": {
"alby": {
"serverUrl": "https://mcp.getalby.com/sse?nwc=ENCODED_NWC_URL"
}
}
}
By default NWC MCP Server runs locally in STDIO mode.
You can set the following environment variable: MODE=HTTP which will enable Streamable HTTP (http://localhost:3000/mcp) and SSE (http://localhost:3000/sse Note: SSE is deprecated).
HTTP requires bearer authorization, where the token is a wallet's NWC connection secret. See the authentication section further above in the README.
yarn install
yarn build
Copy .env.example to .env and update your connection string
yarn inspect
See the tools directory
Make sure you use a decent model (e.g. Claude Sonnet 3.7) otherwise the MCP server will not work.
Make sure you copied the entire NWC connection secret, without spaces
Visit support.getalby.com and we're happy to help you get the MCP server working.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.